Privacy Policy

Togetherward is an independently operated service. It is run by a single operator rather than a registered company, and there is no parent organisation, investor, or agency behind it.

This policy applies to accounts created at togetherward.app, the case workspaces you share with a partner, and the public pages on this site.

• Account information. Email address, display name, and the authentication material our identity provider issues for your session.
• Case content. Everything you and your partner record in a case: tasks, timeline events, appointments, travel plans, notes, decisions, and uploaded documents.
• Billing metadata. If and when you subscribe, our payment processor holds card details and transaction history. We retain only plan, status, and identifiers.
• Product telemetry. Coarse, anonymous events such as “onboarding step completed” — only after you opt in, and never containing case content. See Cookies and Local Storage.
• Diagnostic logs. Server error traces, stripped of document names, note bodies, contact details, invitation tokens, and signed URLs.
• Request metadata. IP address, user agent, and requested URL, recorded by our edge network for delivery, abuse prevention, and debugging.

Once a case has encryption enabled, protected content is encrypted on your device before it reaches our servers. We do not hold the keys, so the stored ciphertext is unreadable to us and our storage provider. If you choose optional evidence checklist suggestions, the values in fields you choose are handled by our application server and sent to the providers listed below after consent; uploaded file bytes are not sent.

• File bytes of document and evidence uploads
• User-entered details for new document and evidence uploads, including filenames, exact file types, categories, dates, labels, statuses, and notes
• Shared note bodies
• Case memory bodies
• Attorney-question drafts and their answers

For encrypted document revisions, servers still see opaque document IDs and storage paths, ciphertext sizes and hashes, upload times, and a coarse file family. Other structured fields you enter, such as task titles and due dates, remain server-readable.

If you explicitly create a shared task from an official update, its public revision reference is also server-readable. Local applicability inputs and match reasons are not copied into that task.

The technical detail — key derivation, per-member key wrapping, and the recovery consequences — is on the security page.

Encryption protects content, not the existence of records. Our servers can read the metadata needed to operate the workspace:

• Who the members of a case are, and when they joined
• That a record exists, its kind, and when it was created or changed
• Dates you attach to tasks, appointments, reminders, and travel
• Unencrypted fields you deliberately record as structured data, such as a task title
• Object sizes and storage paths for encrypted uploads

We state this plainly because a privacy claim that hides its own limits is not a privacy claim.

When you choose to connect Togetherward to ChatGPT, you authorize ChatGPT to call Togetherward tools for you. Public tools return only public information. Member tools require you to sign in and can return only the server-readable structural information needed for your request.

• Your case display name and opaque case, stage, milestone, and task identifiers
• Current stage or milestone labels, task status, assignee, due date, and last-updated time
• A short task title you ask ChatGPT to create
• Receipts that record an assistant-initiated change

Protected encrypted content — including document and evidence files, shared notes, case memories, and attorney-question drafts — cannot be returned through these tools. The tools also do not provide government identification numbers, billing or payment details, or legal strategy.

OpenAI processes the conversation and tool results under its own terms and privacy policy. You can disconnect Togetherward or revoke access to stop future calls. Disconnecting does not delete information OpenAI has already kept in an existing conversation; use OpenAI’s controls for that.

Google Ads receives public page addresses, browser and network information, advertising cookie identifiers and beta form confirmations for measurement and campaign optimization. We do not send names, emails, form answers or private case content. Customer matching and advertising personalization are disabled.

Tracking stays blocked in the EEA, UK, Switzerland, Canada and unknown locations until you accept. Canada requires consent here because country-level location cannot identify Quebec. Elsewhere measurement is enabled unless you refuse or your browser sends DNT/GPC. Cookie settings changes your advertising choice independently of analytics. Blocked events are not replayed.

Your device stores the choice, time, region and notice, preserving prior acceptance evidence after withdrawal. Withdrawal stops future reporting but does not delete information already received by Google. See Google’s business data privacy information.

• Lovable Cloud

  Provides the managed database, authentication, and object storage.

  Account identifiers, case metadata, and stored objects. Protected case content is stored encrypted; selected evidence values also pass through the application server when you request optional checklist suggestions.

• Cloudflare

  Serves the site and runs the server-side application code at the network edge.

  Request metadata such as IP address, user agent, and requested URL.

• Stripe

  Processes payments if and when a paid plan is offered.

  Card details and transaction history, held by Stripe. Togetherward retains only plan, status, and identifiers.

• Lovable transactional email service

  Sends sign-in, invitation, reminder, and receipt email.

  Email address, message subject and body, and delivery status.

• Lovable AI Gateway and OpenAI

  Processes optional evidence checklist suggestion requests after a member chooses to share selected fields.

  Prompt content includes selected evidence fields and checklist instructions, not uploaded file bytes. Provider retention and use follow applicable service terms.

Providers process data for the services described above. We update this list when a provider changes, and record the change in the revision history below.

• Account and case records: for as long as the account or case exists.
• Deleted cases and accounts: removed from the live database and object storage at the time of deletion.
• Encrypted database backups: rolled off on our provider’s standard schedule after deletion.
• Billing and email delivery records: retained by those providers for the period their own legal obligations require.
• Diagnostic logs: short-lived and rotated automatically.

Depending on where you live, you may have the right to access, correct, export, delete, or object to the processing of personal data we hold about you, and to withdraw analytics consent at any time. Most of these are available directly in the product.

For anything that is not, write to support@togetherward.app. We answer data requests ourselves and will confirm receipt.

Togetherward is not intended for children, and we do not knowingly create accounts for them.