Privacy Policy

SYNPL is operated by WORKSTORIES, INC. ("SYNPL", "we", "us"). This Policy covers our website, macOS application, iPhone companion, connected services and account infrastructure. It explains processing, not a guarantee of absolute security. The Terms of Use govern use of the beta service.

The essential distinction: your connected workspace and working memory are stored on your Mac, but cloud AI requests pass through our server at api.synpl.com in Germany to OpenAI. We process those requests in transit without retaining their request and response bodies on our application servers. We do store account, subscription, usage and device records. The phone relay is separately end-to-end encrypted. Local storage does not mean that nothing leaves your device or that we process no personal information.

1. Our role and the scope of this Policy

We determine how account administration, billing, service security, support, product analytics and our own website analytics and marketing operate and act as controller for those activities where that legal concept applies. When processing personal information on behalf of a business customer to deliver its instructed assistant functions, we act as processor or subprocessor under the Data Processing Agreement. Processing includes receiving and forwarding information, even without persistent storage. Website marketing does not authorize an advertising use of information processed on a customer's behalf.

A business customer remains responsible for its purposes, lawful authority, notices to correspondents and personnel, and instructions. Using a personal laptop does not remove other people's privacy rights. Information processed solely by your own connected providers remains subject to their arrangements with you.

2. Information and sources

Connected workspace. On your instructions, the application reads selected communications, message metadata, calendars, tasks, documents and other records from enabled sources. These include Gmail and Google Calendar; WhatsApp and Telegram; and, for enabled Microsoft tenants, Exchange/Outlook and Microsoft Teams through Microsoft Graph. Other supported sources include Zendesk, Jira, Notion, Pipedrive, connected databases, selected local folders and tables, and Mac calendars. Availability is limited to integrations actually enabled for your account. Microsoft access is currently restricted to enabled tenants, not generally available to every organization.

WhatsApp access reads its local Mac database and requires the relevant macOS Full Disk Access permission. That broad operating-system permission is not permission for us to use unrelated files. The application limits extraction to the sources and conversations you select. The current release does not provide Slack, generic IMAP/SMTP, iCloud Mail or Yahoo Mail connectors.

Local working records. The Mac stores the selected source index, conversations with the assistant, tasks, working facts, project/person context, local Wiki, credentials and settings used by the application. Information may concern you, your colleagues, customers, suppliers and other correspondents. We do not host or back up that personal workspace as a central repository.

Cloud feature inputs. A cloud task can transmit your prompt, minimized source excerpts, relevant working-memory fragments, instructions and generated output. Web search can send a derived search query to the provider's search function. Text-to-speech sends the text to be spoken; real-time voice sends audio and session information for processing. Voice can identify a speaker and must not be assumed anonymous. Local transcription of supported voice messages is separate from cloud real-time voice. Imported Plaud recordings are supported when connected; SYNPL is not a general call-recording service.

Server records. We store account identifiers, name, login email and sign-in times; subscription status and Stripe identifiers; usage records showing the account, time, model, task purpose, token use and client version; device/relay records such as Mac identifier, device name and Apple push-notification tokens; and technical logs. These records are different from stored mailbox contents or saved AI conversations.

Application analytics and support. Native product analytics consist of interface events and technical attributes, including a device identifier, application version and language, rather than message or document text. We receive the information you deliberately include in a support request. Do not send your full workspace, passwords, payment-card details or API secrets to support.

Website analytics and advertising. Subject to your choices, website tools can process public-site page views and interactions, browser or device identifiers, advertising click identifiers, IP address, browser attributes, language, approximate location, referring pages and campaign parameters. Limited conversion events can include sign-up, trial, download or purchase activity, with plan, value and currency. These events do not include payment-card details, login secrets or connected workspace content. Advertising providers may match the events with their own information and infer interests. Pseudonymous identifiers are not necessarily anonymous. Website hosting and purchase flows also involve the technical information needed for those functions.

3. Where processing happens

An EU intermediary is not an EU-only processing promise. OpenAI processing involves the United States, and other providers may process information internationally. No zero-data-retention arrangement with OpenAI is represented.

4. Purposes and legal bases

We use information to supply the features you enable: connect selected sources; search and organize information; generate digests, drafts and answers; preserve local task and working context; and perform specifically approved actions. We also use necessary information to authenticate you, pair devices, deliver notifications, meter tokens, administer payments, prevent abuse, operate and improve the product, resolve support requests and meet legal obligations.

Separately, with the relevant website permission, we measure website traffic and campaigns, analyze conversion funnels, create permitted advertising audiences, retarget previous visitors, personalize and optimize SYNPL advertising, and suppress irrelevant ads. Analytics-only permission does not authorize advertising use or sharing for advertising. Native application events and connected-source content are not automatically repurposed for this website marketing.

Where the GDPR or similar law applies, account and requested service processing relies on performance of a contract when necessary for that purpose; security, troubleshooting and appropriately limited service administration rely on legitimate interests in running a reliable service; and statutory recordkeeping relies on legal obligations. Optional website analytics and marketing are activated only after the relevant consent. Native product analytics may rely on legitimate interests only where applicable device-access and privacy rules permit this; otherwise prior consent is required. A customer's lawful basis governs personal information it instructs us to process under the DPA.

We do not sell workspace information, use it for targeted advertising, or use it to train shared or general-purpose AI models. The same restrictions apply to Google-derived information and its derivatives, including aggregates and pseudonyms. These protections are distinct from consented website advertising described in Sections 9 and 11. Optional marketing communications are separate from necessary service, billing and security notices.

5. Google access and Limited Use

The current Google integration requests Gmail read and send access and read-only Google Calendar access. It reads the selected mail and calendar information for the assistant functions described above, and sends email only after your confirmation, including a schedule you have expressly approved. Google Drive, Docs, Sheets and Contacts access are not enabled as separate Google integrations in this release. We do not request calendar-write access for this integration.

We use the authorization mechanism provided by Google, not your Google password. Granting an OAuth permission is not blanket approval for every technically possible action. Relevant Google-derived context for cloud features follows the Germany-to-OpenAI route described above. The required in-product disclosure and affirmative consent must precede that processing; merely accepting these Terms or reading this Policy is not a substitute.

SYNPL complies with the Google API Services User Data Policy, including its Limited Use requirements, and the applicable Google Workspace user-data policy. Google-derived data is used only for the disclosed, appropriate user-facing functions. Transfers are limited to providing those functions with the user's consent, necessary security purposes, legal requirements, or a qualifying business transfer with the explicit prior consent Google requires. Human access is limited to the exceptions those policies permit, including specific user-authorized support, necessary security or legal access, and permitted aggregated internal operations. Our inability to read the encrypted phone relay remains unchanged.

We do not transfer Google-derived content to Amplitude as product analytics, sell it, use it for advertising or creditworthiness decisions, or use it to train or improve general-purpose models. Aggregation, masking and pseudonymization do not remove Google's restrictions. You can disconnect the integration and revoke access in your Google Account's third-party connections settings. The Mac erase function also revokes Google tokens as described in Section 8.

Google's policies: Google API Services User Data Policy and Google Workspace user data and developer policy.

6. Minimization, AI and local controls

The text-processing pipeline uses pseudonyms for names, email addresses and phone numbers and detects categories such as keys, access codes, card numbers, passwords and identity-document data before indexing. Cloud tasks use reduced, task-relevant context rather than automatically uploading an entire mailbox. These measures reduce exposure; they do not guarantee complete anonymity, detection of every secret or removal of identifying context from every prompt, search query, spoken text or audio session.

The application provides a local record of material sent to the model, activity counters, pause controls, a configurable source-history window, local-mode functionality and a Mac erase function. A local-mode choice limits cloud assistant processing; it is not a promise that account, billing, connected-source synchronization, analytics or device services never use the network. Analytics has its own control. Review the relevant control before relying on it.

OpenAI is the only cloud AI provider used in this release. Its API is used for responses, provider web search, speech output, real-time voice and embeddings for a server-side knowledge-base function. There is no active Anthropic integration. We use the no-training API arrangements and do not opt customer content into general-purpose model training. Setting store=false for applicable requests does not establish zero retention at OpenAI. See AI Providers & Data Use for the distinction between our transit handling and provider retention.

Local workload/pressure indicators and a local dictionary of self-referential crisis markers operate on the Mac. They are organizational aids, not medical diagnoses, emergency monitoring or judgments about other people's health or character. These local indicators are not sent as product-analytics content or used by us for significant automated decisions about people. Underlying source excerpts can still be included in a separately authorized cloud task.

7. Recipients and international processing

Our current service recipients include Hetzner for German server hosting; OpenAI for cloud AI; Amplitude for limited native interface-event analytics; Stripe for payments; Apple for push notifications; and Webflow for the website hosted on that platform. Account-email delivery and support providers receive information needed for those functions, not a general copy of the local workspace.

For the website, we may enable Google Analytics, Amplitude Analytics, Meta Pixel for Facebook/Instagram advertising, and TikTok Pixel, subject to the choices in Section 9. Advertising features, linked Google advertising services and other new recipients require the relevant disclosure and permission before activation. These providers receive the permitted website identifiers and events, not access to your connected mailbox. Depending on the function and applicable arrangements, recipients may act as processors, independent controllers or joint controllers. We remain responsible for our own collection, choices and disclosures. The Cookie Policy identifies purposes, provider references and choice controls.

Connected services you choose receive authorized requests and actions under their own account arrangements. OpenAI may use its own service providers for enabled functions such as search. We may disclose information we actually hold to authorized advisers or authorities where necessary for legal compliance, security or legal claims. A business transfer remains subject to this Policy and, for Google data, Google's additional consent restrictions.

Where cross-border transfer safeguards are required, the relevant processing must use a legally valid mechanism, such as an applicable adequacy decision or appropriate contractual safeguards with necessary supplementary measures. Hosting in Germany, acceptance of the beta Terms, or masking alone does not establish such a mechanism. Contact us for information about the safeguards applicable to your processing; the DPA addresses business-customer transfers. We do not claim an unverified certification or universal regional residence for provider processing.

8. Retention and deletion

Mac data. By default, the source-history window covers seven days and can be narrowed; older source material outside the selected window is removed from that rolling source history. Any shorter retention limit required by law or a connected provider prevails. This is not a seven-day expiry for all records. Tasks, facts, local Wiki, saved assistant conversations and other working memory can remain until removed through the relevant controls or by erasing the local workspace. Your source providers and your backups retain their own copies separately.

Erase this Mac. The application's "Erase everything from this Mac" function signs out connected accounts, revokes Google tokens, and removes the local index and application secrets. Use the available local removal controls for the workspace and check your own backups and paired devices separately. Local erasure does not delete original messages at their source, recall sent communications, cancel a subscription or automatically delete our account records.

Server data. We do not retain cloud AI request/response bodies as stored application records. Ordinary technical logs are retained for up to 30 days. Account, subscription, metering and device records remain as needed to operate the account, manage billing and resolve relevant issues; they are not all covered by the technical-log limit. Email support@synpl.com to request server-record deletion. We complete verified deletion requests within 30 days, or any shorter applicable legal deadline, except information lawfully required for tax, accounting, security incidents or legal claims. Such exceptions are limited to their necessary purposes and retention periods.

Providers and support. OpenAI's standard abuse-monitoring retention can include content for up to 30 days, with legal, safety and feature-specific exceptions; deletion on your Mac does not erase those copies. Support correspondence and native analytics records are kept only as needed for the stated support or product-analysis purpose, applicable provider configuration and legal obligations. You may request deletion or information about the applicable period. Disabling native analytics stops future optional application-event collection; it does not itself erase earlier events. We transmit appropriate deletion instructions to our processors where required and within our control.

Website tracking. Cookie and storage lifetimes are disclosed in the active Cookie settings inventory. Website-event records and audience membership have separate retention based on their disclosed purpose, configured period and applicable withdrawal, deletion and legal-record duties. Cookie expiry does not itself erase provider records. A website marketing withdrawal stops future consent-based collection and advertising uses under our control, including future audience updates; required instructions are passed to the relevant recipients. These records are not governed by the AI-content or ordinary application-server log retention limit.

9. Analytics, cookies and website advertising

The current application's product-analytics setting is an opt-out toggle in "About". When enabled, interface events with device identifier, application version and language are relayed to Amplitude, without workspace text. You can switch it off. This describes the current control, not a claim that opt-out is legally sufficient everywhere: where prior consent is required, collection must wait for that consent or remain disabled. A device identifier is not necessarily anonymous.

Website choices. The website may use Meta Pixel, TikTok Pixel, Google Analytics and Amplitude for the measurement and advertising purposes described above. Optional website analytics and marketing stay off until the relevant permission is accepted. Use Cookie settings to accept or reject them separately, or withdraw a choice. Analytics-only events are not sent to advertising platforms or reused for retargeting. Marketing consent covers only the disclosed website purposes and recipients; it does not authorize any advertising use of connected-source content, its derivatives or native application data.

Website audiences may support retargeting, similar audiences, campaign attribution, advertising personalization or ad suppression. Enhanced matching with contact details and customer-list uploads require a separate clear disclosure and the required permission before activation; this notice does not enable them automatically. We do not send names, email addresses or telephone numbers as ordinary Google Analytics event data. Advertising integrations must exclude private workspace content, support text, authentication secrets, full payment details and sensitive pressure or crisis indicators.

The Cookie Policy explains website technologies, recipients, retention information and controls. Cookie choices are generally browser-specific and do not automatically synchronize with the application's analytics setting. Consent to website tracking, cloud AI, connected accounts and recurring charges are separate choices; none is inferred from another. Refusing optional tracking does not prevent access to the core website or paid service.

10. Security, your device and beta limitations

We maintain safeguards proportionate to the processing, including encrypted network transport, the encrypted phone relay, local minimization and permission controls, and restricted handling of server information. We are responsible for safeguards applicable to our own processing and service providers. We do not promise that every byte is protected against every threat, that content can never be identified, or that the beta has no vulnerabilities.

You manage your Mac and iPhone: device encryption, passwords, operating-system updates, physical access, malware protection, approved applications, screen/notification exposure, provider credentials, backups and sync settings. Do not expose sensitive information to other people through a shared or unlocked device. SYNPL is not a managed-device security, archival, disaster-recovery or emergency-response service. Your responsibilities do not excuse our own breach, unauthorized transmission or mandatory data-protection duties.

11. Rights, contact and changes

Depending on applicable law and our role, you may request access, correction, deletion, restriction, portability, withdrawal of consent, objection to processing, and an appeal against a rights decision. We do not make solely automated decisions producing legal or similarly significant effects about you through these assistant functions.

Website advertising opt-outs. Sharing website identifiers, public-site activity and limited conversion information with advertising or analytics providers may qualify as a sale, sharing for cross-context behavioral advertising, or targeted advertising under applicable US state laws, even without payment for the information. This is not a sale or advertising use of connected workspace data. Use Do Not Sell or Share My Personal Information in the website privacy controls to stop covered website advertising disclosures and targeted advertising, including associated server-side uses under our control. We honor Global Privacy Control and other legally required opt-out signals for covered processing. These opt-outs do not require an account or identity documents. We do not knowingly use information about people under 18 for targeted advertising. Additional controls are described in the Cookie Policy.

Send requests to support@synpl.com. We may verify identity proportionately, and respond within the applicable legal deadline, explaining any permitted extension or refusal. You may complain to your competent data-protection authority without first contacting us. For data held only on your device or processed for a business customer, we explain the relevant local control or direct the request to that customer and provide required assistance. We do not require a full workspace upload to exercise rights.

SYNPL is for adults aged 18 or over, not a child-directed service. Notify us if an underage person has created an account. We update this Policy when processing changes, give material-change notice and obtain fresh consent before new processing where required. A policy update does not retroactively authorize an undisclosed use. Beta status does not waive privacy rights.

Contact: WORKSTORIES, INC., 2093 Philadelphia Pike #2517, Claymont, DE 19703, United States. Email: support@synpl.com.