Privacy & Terms
Last updated: 8 October 2026
Privacy Policy
Pazator builds local-first software. This website is a static site; it does not set advertising or analytics cookies and does not run third-party trackers.
What we collect
When you submit the demo-request form we collect the information you enter: your first and last name, business email address, company or institution, job title, phone number, country, and any project details you choose to share.
Why we collect it
Only to respond to your request and arrange a demo. We do not sell your information and do not use it for advertising.
Where it goes
Form submissions are sent to our own endpoint and delivered to a private channel we control. They are not shared with third parties except the infrastructure provider that relays the message on our behalf.
Retention
We keep your request for as long as needed to handle it. You can ask us to delete it at any time via the contact link below.
Contact
Questions or deletion requests: reach us on Discord.
Terms of Service
MADAR: TERMS OF SERVICE
Please read these terms carefully. By using MADAR you agree to all of the following.
Neural disclaimer, please read first
Zor and the other Neural features (risk assessment, report narratives, scoring) produce predictions and suggestions, not verified facts. They can be wrong, incomplete, or misleading. Never trust Neural output 100%; treat it as a lead and verify it yourself before acting on it. Pazator is not responsible for incorrect, incomplete, or false information produced by Neural features, nor for any decisions you make based on them.
1. Authorized use
You confirm that you are authorized to store, process and analyze the data you put into this system, including data about other people or organizations, and that doing so is lawful in your jurisdiction. You are responsible for complying with all applicable laws, including data-protection and privacy regulations.
2. No guarantee of accuracy
MADAR aggregates, connects and analyzes data from many sources. Entity information may be incomplete, out of date, or wrong, and relationships or casework may be mistaken. All decisions made on the basis of MADAR output are your responsibility.
3. Neural and data sharing
Neural features send the data they process to the Neural provider configured on this server. With cloud providers that data may leave your network and be processed by a third party. If your data must never leave your premises, configure a local on-premises provider. You are responsible for choosing an appropriate provider.
4. Classification and access
Every record in MADAR carries a classification, and every account can see everything up to that account's clearance. You are responsible for granting the right roles and clearances, and for keeping passwords strong and secret. We are not liable for misuse of accounts you create or passwords you choose.
5. Data loss and backups
MADAR stores data in a database on your server. We do not back it up for you; you are responsible for regular backups. We are not liable for any loss, corruption, or deletion of your data, including data lost or damaged during imports, merges, or transfers.
6. Imports, exports, and edits
Imports create fresh copies and nothing is overwritten, but a mistaken import or merge can still duplicate or misplace data. Review what you import and what you merge. Exports can contain classified data; store and share them accordingly.
7. No warranty
MADAR is provided "as is" and "as available", without warranty of any kind, express or implied, including fitness for a particular purpose. It is not a substitute for professional judgement and does not constitute legal, financial, or operational advice.
8. Limitation of liability
To the fullest extent permitted by law, Pazator and any contributors are not liable for any damages arising from your use of MADAR, including but not limited to: decisions made on the basis of its output, errors or omissions in data, downtime or unavailability, data loss, and the actions or outputs of Neural features.
9. Acceptable use
You agree not to use MADAR to store or process unlawful content, and to use the system lawfully at all times. You are responsible for how your organization uses it.
10. Security is yours
You are responsible for securing your installation: TLS, strong administrator passwords, session lifetimes, and physical access to the server. Report any suspected breach to your own organization.
11. Changes to these terms
These terms may be updated from time to time. Continued use of MADAR after a change means you accept the updated terms.
Support and Warranty Addendum
This Support and Warranty Addendum forms part of the agreement between Pazator and the Buyer. It defines the guarantees, defect response timelines, and support obligations provided during the active license term. By purchasing a license and activating the system, the Buyer accepts these terms.
1. Scope of warranty
Pazator warrants that the unmodified MADAR software, as delivered and installed, substantially conforms to its functional documentation and passes the standard acceptance test suite (npm run check:*) provided with the distribution. Pazator further warrants that it will use commercially reasonable efforts to correct reproducible technical defects in the software that materially affect its operation.
2. Defect classification and response timelines
For the purposes of this warranty, technical defects are classified by their impact on operations. The Buyer must assign an initial severity level when submitting a support request. Pazator reserves the right to reclassify a defect based on objective criteria.
Critical Defect (Severity 1): The software is wholly unusable, persistent data corruption occurs during routine operations, the entity resolution engine fails entirely, or the system refuses to start or authenticate. Pazator will dedicate continuous engineering effort until the defect is resolved or a functional workaround is provided. A permanent fix shall be delivered within five (5) business days of confirmation of the defect.
Non-Critical Defect (Severity 2 or 3): A specific feature fails to operate as documented (e.g., report export, map rendering, search facets), the user interface contains a functional error, or a non-security performance degradation occurs. Pazator will deliver a fix or workaround within the next scheduled maintenance release, but in no event later than thirty (30) calendar days from the date the defect is reported and confirmed.
3. Support term and license validity
The warranty and support obligations described herein remain in full force and effect for the duration of the Buyer's active software license. Support terminates automatically upon license expiration, non-renewal, or revocation for breach of the Terms of Service. Support may be renewed separately at Pazator's then-current maintenance rates.
4. Update delivery mechanism
All software patches, fixes, and version updates provided under this warranty shall be delivered as a self-contained, digitally signed update bundle (.madar-update or similar) via physical media (USB drive, hard disk) or secure file transfer, at the Buyer's election. The Buyer is solely responsible for transferring the update file into the air-gapped environment and uploading it via the MADAR Settings panel. Pazator does not maintain remote network access to the Buyer's infrastructure and shall not be held liable for delays caused by the Buyer's internal security review, transport logistics, or deployment procedures.
5. Warranty exclusions
Pazator's obligation to correct defects does not apply to any issue arising from:
- Hardware failure, network outages, operating system misconfiguration, or PostgreSQL database corruption not caused by the MADAR application code;
- Data errors, duplicate records, or analytical inaccuracies resulting from the Buyer importing malformed source documents, misusing the merge/unmerge tools, or entering incorrect metadata manually;
- Modifications, reverse engineering, or custom integrations performed by the Buyer or any third party without Pazator's written authorization;
- Failure or unavailability of third-party cloud Neural providers (e.g., OpenAI, Gemini) if the Buyer has explicitly configured the system to use a cloud endpoint instead of an on-premise local model;
- Any defect that was corrected in a prior update but persists because the Buyer delayed or failed to apply the available patch.
6. Sole remedy and liability cap
The Buyer's sole remedy for any breach of this warranty shall be, at Pazator's option: (i) correction of the defect in accordance with the timelines above; (ii) provision of a functional workaround; or (iii) a pro-rata refund of the unused portion of the license fee, limited to the total amount actually paid by the Buyer for the affected license term. To the fullest extent permitted by applicable law, Pazator disclaims all other warranties, express or implied, and shall not be liable for indirect, incidental, or consequential damages, including lost profits, lost intelligence, or mission failure, arising from the use or inability to use the software.
7. Acceptance period and initial testing
Upon initial delivery, the Buyer shall have fourteen (14) calendar days (the "Acceptance Period") to install and test MADAR against its operational environment. The system shall be deemed accepted at the end of this period unless the Buyer provides Pazator with a written list of Critical Defects that prevent normal operation. Defects discovered after the Acceptance Period are subject to the standard support timelines defined in Clause 2.
8. Governing law and arbitration
Any dispute arising out of or relating to this Addendum shall be settled by binding arbitration administered under the UNCITRAL Arbitration Rules, conducted in a neutral venue mutually agreed by the parties (e.g., Sultanate of Oman or Swiss Confederation). This clause survives termination of the license agreement.