How Parallax handles personal information

This policy applies to visitors to Parallax websites, users of the Parallax desktop app, users of Parallax Command, customer administrators, trial users, prospects, suppliers, and people who contact us for support or sales.

For customer meeting, coaching, and sales-call data, the customer is generally the controller and Parallax acts as processor. For Parallax account administration, billing, licensing, support, website, security, and operational telemetry, Parallax acts as controller. Where required, Parallax makes a Data Processing Agreement available to customers.

We may collect account and contact details, organisation details, billing and subscription information, support messages, sales and customer relationship records, website usage information, product telemetry where enabled, security logs, and information needed to administer licences or provide support.

During live operation, the Parallax desktop app may process meeting audio, transcript text snippets, speaker labels, coaching suggestions, suggestion categories, confidence scores, outcome signals, session metadata, hashed deal identifiers, and related product usage information. The way this data is stored and synced depends on the product area described below.

Parallax is built so that sensitive meeting data is stored locally on the user's device wherever possible. The Parallax desktop app stores meeting transcripts, coaching suggestion text, speaker labels, hint outcome signals, local database statistics, knowledge base files, and local customer context in a local SQLite database.

Parallax does not currently apply separate application-level encryption to the local SQLite database. Local data is protected by the customer's or user's device and operating-system security controls, such as account permissions and disk encryption where enabled.

Parallax does not persist raw meeting audio to local disk and does not sync raw meeting audio, transcript text, coaching suggestion text, full meeting content, plaintext deal names, or raw meeting recordings to Parallax Command. Plaintext deal names are handled as SHA-256 hashes before Command sync.

To provide the service, limited data may be sent to subprocessors or to Parallax Command. Deepgram receives live audio streams during active meetings and training calls for transcription. MiniMax receives transcript snippets and relevant context needed to generate real-time coaching suggestions and summaries.

Parallax Command receives limited metadata only, such as session metadata, suggestion categories, confidence scores, outcome signals, aggregate statistics, and hashed deal identifiers. Command is used for adoption reporting, rep-level coaching signals, metadata analytics, suggestion outcome analytics, and management reporting. It is not used as a repository for raw meeting content.

We use personal information to:

• provide, maintain, secure, and improve Parallax;
• administer accounts, workspaces, licences, trials, and billing;
• deliver live transcription and real-time coaching suggestions;
• provide customer support and respond to enquiries;
• measure product adoption, performance, reliability, and usage;
• send operational, security, product, and commercial communications;
• enforce our agreements and protect Parallax, customers, and users;
• comply with legal, tax, accounting, and regulatory obligations.

Where GDPR or UK GDPR applies, our legal bases may include performance of a contract, legitimate interests, consent, legal obligation, and, where applicable, processing on documented customer instructions as processor.

Parallax uses optional product telemetry through PostHog EU Cloud. Telemetry is limited to anonymous event counts, durations, and product usage metadata. We do not send transcript text, coaching suggestion text, raw audio, or meeting content to PostHog. Telemetry opt-out is supported.

Our website uses a cookie preference system. Optional analytics and marketing trackers are not intended to run unless enabled through the cookie banner or settings control. More detail is available in our Cookie Notice.

We use subprocessors and service providers to operate Parallax. We may update this list if material subprocessors change.

Parallax is operated from Australia. Parallax Command application hosting is provided by Vercel, and the Command database is hosted by Neon in London, United Kingdom.

Where EU/EEA or UK personal data is accessed or processed from Australia or another jurisdiction that requires a transfer safeguard, Parallax will use appropriate contractual safeguards, such as EU Standard Contractual Clauses and the UK Addendum or an equivalent UK transfer mechanism, as applicable.

Parallax uses a combination of product architecture, technical controls, and operational policies to protect customer data. Command data is encrypted in transit and at rest. Support access to customer production data is logged, and company policy requires customer approval before support or developer access to customer production data except where access is legally required or necessary to protect the service.

No internet-connected service can be guaranteed completely secure. Customers are responsible for managing their users, devices, endpoint security, access controls, retention settings, and internal policies.

Local device data is stored on the customer's or user's own device. By default, local device retention may be unlimited unless the user or customer deletes it using available in-product controls, such as date-range deletion, session-level deletion, or full local data deletion where available.

Command metadata is handled separately. Deletion may be handled through customer administrator controls where available, support request, or contract termination workflows. On contract termination, Parallax deletes or returns customer personal data within the shorter of the period legally required in the applicable jurisdiction or 90 days. Command backup retention is 30 days unless a longer period is legally required.

Depending on where you are located, you may have rights to access, correct, delete, object to, restrict, or receive a copy of personal information. You may contact us at privacy@tryparallax.app.

Where Parallax acts as processor, customers are responsible for responding to data subject requests, and Parallax will reasonably assist with requests relating to personal data that Parallax processes on the customer's behalf. Because Parallax is local-first, some meeting data remains on the relevant user device and is not accessible to Parallax.

Customers remain responsible for their own use of Parallax, including establishing a lawful basis for processing meeting participant data, giving any required notices to employees, representatives, prospects, customers, and meeting participants, and complying with call recording, transcription, employee monitoring, workplace privacy, and similar laws.

Parallax does not join meetings as a bot and does not persist raw meeting audio. Customers remain responsible for notices and consents required by applicable law.

We may update this Privacy Policy from time to time. If we make a material change, we will take reasonable steps to notify customers or users, such as by updating this page, sending an email, or providing an in-product notice.