PRIVACY · VERSION 2026-10-29

Privacy & your data

Jump to a section

Who is responsible

SYNIX AI SOLUTIONS L.L.C-FZ, Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, United Arab Emirates, operates Countercheck. Contact rawad@synixsolutions.io about privacy. We control account, billing, support and service-administration information. Your business controls supplier and review records it submits; we process them on its behalf under the data-processing schedule.

Information and purposes

We store verified email addresses, names, user identifiers, membership roles, supplier contact and bank details, change requests and payment values, evidence references and attachments, review decisions and audit timestamps. Sign-in records include timestamps and a browser/device description. We use this information to provide and secure the service, maintain review history, support users, manage billing and meet applicable legal obligations.

Processing is limited to those service, security, customer-instruction and legal purposes. Where applicable law requires consent for an additional purpose, we request it separately. The customer must provide appropriate notices and have authority to submit information about personnel and suppliers. Avoid unrelated identity documents or sensitive personal records.

Access and providers

Active organization members see records according to their role. Administrators manage access and billing. Authorized operator personnel and contracted providers may access information as needed to administer, secure or support the service. Private storage does not make records inaccessible to the operator.

Cloudflare hosts the application, D1 records, private R2 evidence and encrypted archives. Supabase provides identity. Resend delivers sign-in messages and enabled monitoring warnings. Stripe processes subscription payments and billing details; the application does not receive full card numbers. Optional inbox processing uses Resend and, when enabled, OpenAI for selected email and PDF extraction. Bank ownership verification is excluded from the email-monitor release. See the optional processing notice.

Optional supplier email monitoring

The email monitor uses up to three separately approved read-only Gmail connections, or selected forwards. It does not send, modify or delete mail through the Google connection. Enabled warnings are sent to the mailbox that received the flagged message through Resend, with the relevant sender, subject, signals and public-domain findings. Google grants mailbox read access; the application checks incoming and sent mail, including Spam and Trash, starting with the last seven days. It retains matched supplier and possible payment-change messages (plain text, locally converted HTML text and selected headers), observed addresses from sent business conversations, optional independently confirmed contact records and alert evidence. Observed history is not independent verification. Retained evidence is available to authorized members of the same workspace. Minimal message identifiers and a monthly usage count prevent duplicate counting; historical backfill is excluded. Evidence remains until the workspace deletion process or an agreed retention policy applies. When invoice checking is enabled for a mailbox, supported forwarded email, Excel and text PDF files are processed within Countercheck. Masked identifiers, comparison fingerprints, filenames, beneficiary names and findings are retained with the message. Image-only pages are reported for manual review. Only domain names are sent to Google Public DNS and the relevant registry RDAP service for public research; email bodies and bank information are not sent to those lookup services. Temporary recovery snapshots are deleted after export or at the next cleanup after one hour. Google refresh tokens are encrypted and excluded from workspace exports and backups. Disconnect removes the saved token; retained evidence remains until deletion under the retention policy. Monitoring does not train a general AI model on mailbox content.

Optional monitoring preview

Additional source connections are an internal preview and are disabled until setup and separate administrator consent. Depending on the selected source, these can retain QuickBooks supplier and transaction records, submitted documents and proposed payment details, supported business WhatsApp messages, GLEIF company records or Google Workspace login audit events. A saved plan selection does not grant access. Document extraction uses OpenAI only after source-specific consent. Company identifiers are sent to GLEIF only for requested LEI lookups. No payment is approved or executed. Connection secrets are encrypted and omitted from customer exports; disconnect removes local credentials, while retained evidence follows the deletion process below.

International processing

Our providers operate international systems, so information may be processed outside the UAE. We do not promise exclusive UAE residency. Provider agreements, access controls and applicable transfer safeguards govern that processing. Contact us before submitting records subject to a specific residency or transfer restriction. The processing schedule identifies providers and how changes are handled.

Cookies and email

Necessary cookies maintain sign-in and protect authentication. Session-cookie and invitation-token values are hashed in storage; stored identity-provider tokens are encrypted. The application does not use advertising cookies or advertising tracking. Sign-in emails deliver requested codes. Account creation does not subscribe you to marketing.

Retention and deletion

Workspace records remain available while the workspace is open, including read/export access after an evaluation or subscription ends. Cancellation alone does not erase records. An authorized administrator may request closure, export or deletion. We verify authority and scope, identify any lawful hold, and aim to complete an approved deletion within 30 days. This is an operator-managed process, not a self-service destructive reset.

New scheduled encrypted backups expire after 30 days. Deleted data can remain in those protected copies until expiry and must not return to use without reapplying the deletion. Prelaunch verification archives contain only operator or fictional test records and are retained separately. Billing, security and legal records may be retained as necessary for their purposes or legal obligations; supplier evidence is not kept solely for billing. Membership removal blocks future access but preserves historical actions with the workspace. Exported copies are controlled by the recipient.

Your requests

Contact us for access, correction, deletion, restriction or other rights available under applicable law. We verify identity before disclosure or deletion. For records controlled by a customer, we direct the request to that customer and assist with lawful instructions. Rights may be subject to legal exceptions. You may also raise concerns with the competent data-protection authority.

Changes

We update the version above and notify affected customers of material changes. We do not sell supplier or case data or use it to train AI models.

Support · Service terms · Data processing · Security