SyntoniseReturn home

PRIVACY / PRODUCT FOUNDATION

Your private conversations
deserve restraint.

What happens during analysis

Your messaging export is parsed in the browser. The original ZIP, JSON, or text file is not uploaded. Syntonise creates aggregate statistics, chronological periods, and a bounded normalized transcript. Common email addresses, phone numbers, and links are removed, and both participant names are replaced with anonymous labels before the transcript is sent to OpenAI.

AI processing

The pseudonymized transcript, notes, and statistical context are sent to OpenAI to generate the report. Analysis uses background processing with API response storage disabled. OpenAI temporarily retains background response state for polling and may retain abuse-monitoring logs under its API data controls. Only continue if you have the right to provide and process the conversation.

Advisor questions

Questions submitted to the contextual advisor are sent with the report context needed to answer them. Do not include sensitive information that is unnecessary for the question.

Payments

Subscription checkout is embedded in Syntonise using a secure payment component operated by Stripe. Card details go directly to Stripe and are not received or stored by Syntonise. Stripe sends signed events so membership access can be provisioned, renewed, restricted, or cancelled for the correct account.

Advertising measurement

Syntonise uses the Meta Pixel and Meta Conversions API to measure page visits and the main subscription-funnel events. Depending on what is available, these events can include Meta browser and click identifiers, IP address, browser user agent, page URL, account identifier, email, and first name. Email, first name, and account identifiers are normalized and cryptographically hashed before server-side transmission. Browser and server events use a shared event identifier to prevent duplicate conversion counting. Meta processes this information under its own privacy terms.

Account data

When account storage is enabled, the completed report, import metadata, additional notes, and advisor history are stored under your authenticated account. Row-level access rules isolate each account. The original export and normalized transcript are not stored in the account database.

Data on this device

The completed report and notes may also be cached in this browser so the dashboard survives a restart and can recover from a temporary connection problem. The original export and normalized transcript are not saved there. Clearing this site's browser data removes the local copy but does not delete account data.

Before public launch

Final retention rules, a support contact, account export procedures, and disclosures required in each country still need to be finalized. This foundation page is product copy, not a substitute for review by qualified privacy counsel.

Your choices

Do not analyze a conversation you are not permitted to process. Do not add sensitive information that is unnecessary. Once accounts are enabled, controls for account export, retention, and deletion should be available in account settings.