PactMeter

InfinityOre · version 2026-09-26

Privacy policy

Status of this text. It describes how the product actually behaves during its pilot stage. It has not yet been reviewed by a lawyer, and the operator details below may be incomplete. Nothing here is legal advice. The operator’s registered legal name and address have not been set on this deployment.

This explains what InfinityOre (“we”) collects when you use PactMeter, why, who sees it, and what control you have. The short version: your documents are used to give you results, are not used to train anything, are not shared with a language-model provider unless you consent, and can be exported or deleted.

  1. 1. What we collect

    • Account: your name, work email, a salted hash of your password (never the password itself) or, if you sign in with Google, Google’s identifier for you; your time zone and language; the workspace name and the optional business details you enter; and which version of the terms and privacy policy you accepted, and when.
    • Sign-in records: for each signed-in device, a truncated browser description and the network address it came from, and a short log of security events (sign-ins, password changes, resets, linking Google). They are shown to you under Settings → Security and are kept to protect your account.
    • Email we send you: the text and delivery status of the account, security and workflow emails about your account.
    • Workspace content: the agreements and records you upload (which may contain names, contact details and commercial terms of your suppliers), what is extracted from them, and what you and the system do with it: findings, approvals, claims you record, replies, outcomes, and an audit trail of who did what and when.
    • Website use, only if you allow analytics cookies: an anonymous visit identifier and the names of steps reached (for example “visited”, “ran a scan”, “signed up”) to see where people drop off. It contains no document content. If you do not allow it, none of this is recorded.
    • Technical: server logs with request details needed to run and secure the service.
  2. 2. Cookies

    We set at most three first-party cookies and no third-party cookies. Necessary: a session cookie that keeps you signed in, and a cookie that remembers your cookie choice. Analytics (only with your permission): an anonymous random identifier (df_fs, up to 30 days) so we can count how far visitors get through the site. It contains no personal data and is not shared. We run no advertising or marketing cookies. You can change your choice at any time with “Cookie settings” in the page footer or in Settings. The full list is in the cookie policy.

  3. 3. Why we use it

    To provide the service you asked for: reading your agreements, comparing them with your records, showing and explaining findings, tracking claims you record, and keeping the workspace secure. To operate and improve reliability, and to meet legal obligations. We do not sell personal data.

  4. 4. The free scan and the demo

    Files given to the free scan are read in memory for that scan and the temporary workspace is deleted when it ends. Demo workspaces contain only fictional data and are removed after 24 hours.

  5. 5. Language-model providers

    By default agreements are read by deterministic software on our own server. If a language-model provider is configured, an agreement is sent to it only after your workspace owner has given consent, and only to help read the text; the model never decides an amount, date or approval. Each call is recorded (provider, duration, tokens reported). You can withdraw consent at any time under Data sources. The provider’s own terms govern its handling of the text, and we name it in your workspace when it is enabled.

  6. 6. Who else sees it

    Only people in your workspace, in the roles you give them; the people who operate this deployment, for support and security; and the service providers listed on the subprocessors page, under their terms. If you create a share link for a proof pack, anyone with the link can read that pack until it expires or you revoke it. We do not use your content to train models.

  7. 7. How long we keep it

    Workspace content is kept until you delete the workspace. Deleting a workspace is done by an owner, needs a fresh password confirmation and the workspace name, and removes the workspace’s data, including its append-only records, from the live database at once. Deleting your account removes your profile, sign-in methods, devices, security events and queued emails, and the workspaces only you belong to. Copies in backups, if the operator keeps any, are not edited and disappear as backups roll off; how long backups are kept is set by the operator and is not yet fixed in this text. Where the law requires us to keep specific records (for example billing records), we keep only those, for the period required.

  8. 8. Your choices and rights

    You can download your own account data, and (as an owner) all workspace data, as JSON (Settings → Privacy and data; a confirmed email address is needed), correct your details, withdraw model consent, sign devices out, and delete your account or workspace, all from Settings. The account deletion page also explains how to request deletion without the app. Depending on where you live you may have further rights, including access, correction, erasure, objection and complaint to a regulator. Write to us and we will respond within the time the law requires.

  9. 9. Security

    Workspaces are isolated from one another at the database level; passwords are stored as salted hashes; production sessions use secure cookies; connections should be served over TLS; and every automated action is recorded with the reason it was allowed. No system is perfectly secure; tell us at once if you find a problem.

  10. 10. Children, transfers and changes

    The service is for businesses and is not directed at children. Data may be processed where our infrastructure providers operate; we will describe the locations here once they are fixed. We will update the version above when this policy changes.

  11. 11. Contact

    Operator: InfinityOre. The contact address for privacy requests has not yet been set on this deployment.

Related: Terms of service · Privacy policy · Fees and refunds · Cookies · Security · Acceptable use · Subprocessors · Contact

There are no marketing or third-party cookies, so there is nothing to switch on for them.