Privacy Policy

1. Overview

SynOI Inc., a Delaware corporation (“SynOI,” “we,” “us,” or “our”), operates synoi.systems and all associated products and services (“Services”). This Privacy Policy explains what information we collect, how we use it, and the choices you have with respect to your data. We are committed to handling your information in compliance with the EU General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and Canada's Personal Information Protection and Electronic Documents Act (PIPEDA).

By using the Services, you agree to the collection and use of information as described in this policy. If you do not agree, do not use the Services.

2. Information We Collect

2.1 Account information

When you create an account, we collect your name, email address, and company name. Billing information is collected and processed by Paddle (our Merchant of Record). We do not store raw payment card numbers.

2.2 Customer Data

“Customer Data” refers to any data you submit to a SynOI-hosted service for processing, including the information you choose to send from Pour when you opt in (see 2.3). Customer Data is processed on your behalf and is not used for any purpose other than providing and improving the Services to you. We process Customer Data only as a data processor acting on your instructions. You remain the data controller for any personal data contained within Customer Data. Data that you check with Pour on your own infrastructure is not Customer Data, because it never reaches us.

2.3 Pour (software you run yourself)

Pour runs on your own infrastructure. SynOI does not receive your rows, your cell values, or your column names. Pour reads your files and databases where they already are, and by default it makes no network call to us to run a comparison. We never receive your database or cloud-storage credentials, connection strings, or directory paths.

If you opt in to submitting a receipt (with the --submit option), what SynOI receives is:

• Content IDs: one-way hashes of a compared table, computed on your machine.
• Row counts.
• Salted commitments: for a manifest run, hashes of the schema, the query, the control totals, and the rules, inventory, ties, drift, and residual files, each combined with a random salt that stays in your local run report. We cannot open a commitment without that report.
• File names (base names only, without directory paths) and the profile name.
• CI details: repository, commit, ref, and run ID, and the CI provider where the software detects one. Where the CI provider issues an identity token, a limited set of claims from it: repository or project, ref, commit, workflow reference, run ID and attempt, the username of the account that triggered the run, and the runner environment. We do not store the token itself.
• The Pour version, the outcome for each table (compared, refused, or not checked), and counts of accepted differences and rules.

Table names are hidden unless you choose to send them (the --share-table-names option). Our service rejects any other field. A content ID cannot be reversed into the data, but like any hash it can confirm a guess about a very small, predictable table, so treat it as a fingerprint and not as encryption.

Pour also involves the following, which are not part of a comparison:

• License checks. Pour verifies a signed license token on your machine. To obtain or refresh that token, it sends your license key to our servers. The token names your organization and license, the product, the entitlements, and the dates, and it carries no email address or other personal identifier. Verifying a receipt without supplying our public keys yourself fetches those keys from us.
• Account records. Your organization's name, its members' email addresses and roles, and its license records (identifiers, entitlements, paid-through date, and status), plus an audit log of organization events in which email addresses are stored as keyed hashes.
• Alerts, if you set them up. The watches you define (repository and table name), the email addresses of alert recipients, and webhook URLs. A recipient may be someone other than the account holder, and we confirm a recipient by a verification email before we send alerts to it.
• Partner invitations. When a partner invites a client organization, we store the invited contact's email address and record whether it was accepted. The partner sees only the status (pending or active), never the client's data, and never the client's license key.

Pour is in early access, so some of these server-side features may not yet be available to all customers.

2.4 Trial abuse controls

To enforce one trial per organization and to prevent abuse of the trial, when a trial is requested we compute keyed hashes (HMAC-SHA256, using a secret key held in our secrets manager) of three values: your email address, after normalizing common alias forms; your email domain, except for webmail domains such as gmail.com; and the IP address of the request, where our portal supplies it. The records that enforce the one-trial rule and the IP rate limit store these hashes, not the raw values, so we do not hold a browsable list of who has taken a trial. Short-lived rate-limit counters are keyed by the normalized email address and by the domain themselves, and they expire automatically.

The purpose is fraud and abuse prevention. The legal basis is our legitimate interests (Section 4). We treat these hashes as personal data. Your email address is also held in your account and organization records, as described above.

2.5 Technical and log data

We automatically collect standard infrastructure logs including IP addresses, browser user agent strings, request timestamps, and error traces via AWS CloudFront. This data is used for security, debugging, and abuse prevention.

2.6 Usage data

We collect data about how you use the Services, including API call counts, feature interactions, and derived usage metrics. This data powers your dashboard, enforces plan limits, and informs billing.

2.7 Contact form submissions

Messages submitted via our contact form are collected and used solely to respond to your inquiry.

2.8 Cookies

Our marketing website (synoi.systems) currently uses no cookies and no client-side tracking scripts. Authenticated product surfaces may use strictly necessary session cookies to maintain your login state. We do not use advertising or behavioral tracking cookies. We will update this policy before deploying any non-essential cookies.

3. How We Use Your Information

We use the information we collect to:

• Provide, operate, and maintain the Services.
• Create and manage your account and process transactions via Paddle.
• Respond to your inquiries and provide customer support.
• Send transactional communications: receipts, security notices, service updates.
• Detect, investigate, and prevent security incidents and abuse, including abuse of trials.
• Verify licenses and operate the receipt, dashboard, and alert features you choose to use.
• Improve and develop the Services using aggregated, de-identified data where possible.
• Comply with legal obligations.

We do not use your data for advertising and do not sell your data to any third party.

4. Legal Bases for Processing (GDPR)

For individuals in the European Economic Area (EEA) and United Kingdom, we process personal data under the following legal bases:

• Contract performance: to provide and manage the Services you have subscribed to, including licenses and any receipt features you turn on.
• Legitimate interests: for security, fraud prevention (including trial abuse controls), and service improvement, where our interests are not overridden by your rights.
• Legal obligation: where processing is required to comply with applicable law.
• Consent: where we have asked for and received your consent (e.g., marketing emails). You may withdraw consent at any time.

5. Data Sharing

We do not sell, rent, or trade your personal data. We share data only in the following limited circumstances:

• Paddle: as our Merchant of Record, Paddle processes payment and billing data. Paddle's privacy policy governs their handling of payment information.
• Amazon Web Services (AWS): our cloud infrastructure provider processes technical log and infrastructure data, and hosts our Pour license and receipt service, under a data processing agreement.
• Partners: if a partner invites you to Pour, it can see the status of that invitation (pending or active). It does not see your data or your license key.
• Legal requirements: we may disclose information if required by law, court order, or to protect the rights, property, or safety of SynOI, our users, or the public.
• Business transfers: in the event of a merger, acquisition, or sale of assets, your information may be transferred. We will notify you before your data is subject to a materially different privacy policy.

6. Data Retention

We retain personal data for as long as necessary to fulfill the purposes described in this policy:

We do not hold the data you compare with Pour, so no retention period applies to it.

7. Data Security

We implement industry-standard technical and organizational measures to protect your personal data, including encryption in transit (TLS 1.2+), access controls, and our own signed governance infrastructure. No method of transmission over the Internet is 100% secure. If you discover a security vulnerability, please report it via our contact form - select “Security” as the inquiry type.

8. International Data Transfers

SynOI is based in the United States. If you access our Services from the EEA, UK, or Canada, your data may be transferred to and processed in the United States. We rely on the EU Standard Contractual Clauses (SCCs) and equivalent mechanisms where required to legitimize such transfers.

Enterprise customers requiring a Data Processing Agreement (DPA) or specific data residency arrangements should contact us via our contact form.

9. Your Rights

All users

• Access a copy of the personal data we hold about you.
• Correct inaccurate or incomplete data.
• Request deletion of your personal data (subject to legal retention requirements).

EEA / UK users (GDPR)

• Restrict or object to certain processing activities.
• Data portability: receive your data in a structured, machine-readable format.
• Withdraw consent at any time without affecting prior lawful processing.
• Lodge a complaint with your local supervisory authority.

California residents (CCPA / CPRA)

• Know what personal information we collect, use, disclose, or sell.
• Delete personal information we hold about you (subject to exceptions).
• Correct inaccurate personal information.
• Opt out of the sale or sharing of personal information. We do not sell or share personal information for cross-context behavioral advertising.
• Non-discrimination: we will not discriminate against you for exercising your CCPA rights.

Canadian residents (PIPEDA)

You have the right to access personal information we hold about you and to challenge its accuracy.

To exercise any of these rights, please use our contact form - select “Legal” as the inquiry type. We will respond within 30 days.

10. Children's Privacy

The Services are intended for users who are at least 18 years old. We do not knowingly collect personal data from persons under 18. If you believe we have inadvertently collected such data, please contact us immediately via our contact form and we will promptly delete it.

11. Third-Party Links

Our Services may contain links to third-party websites or services. This Privacy Policy does not apply to those third parties. We encourage you to review the privacy policies of any third-party services you visit.

12. Browser Extensions (SynOI AI Receipt)

This section describes the extension only. Pour, which you run on your own infrastructure, is described in Section 2.3.

The SynOI AI Receipt browser extension processes your AI conversations entirely on your device. It reads the conversation you choose to sign, computes a signed receipt with a key generated and stored locally in your browser, and saves the receipt to your machine.

The extension makes no network requests. It does not collect, transmit, sell, or share any data. It contains no analytics, no telemetry, and no account system. Nothing you sign, and nothing about you, leaves your device. Data the extension stores (your local signing key and saved receipts) lives in your browser profile and is removed when you uninstall the extension or clear its storage.

Verifying a receipt with the separate open-source tools (such as the @synoi/verify package) is likewise an offline operation and requires no SynOI account or service.

13. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the revised policy on this page and updating the effective date. Your continued use of the Services after changes are posted constitutes acceptance of the updated policy.

14. Contact

For privacy-related requests, questions, or complaints, please use our contact form - select “Legal” as the inquiry type. We will acknowledge your request within 5 business days and respond fully within 30 days.

You also have the right to lodge a complaint with your local data protection authority if you believe your rights have been violated.

Our full Terms of Service govern your use of the Services and are incorporated by reference into this policy.