OrgTidePricingGuideLearnSign inGet started

Privacy Policy

Last updated: September 28, 2026

This policy describes what data OrgTide - operated by Appiotech, Inc. (“Appiotech”, “we”, “us”) - collects, why, who processes it, and how long it is kept. The short version: we store your account, your org connections, and the work you do in OrgTide; we send what each AI action needs to our AI provider; and we never read, store, or transmit your Salesforce record data.

What we collect

  • Account data - your email address and sign-in details, managed by our sign-in provider (Clerk). OrgTide keeps an internal account ID and looks your email up from Clerk when it is needed, for example for billing.
  • Org connections - for each Salesforce org you connect: its name, its address, the Salesforce username you connected with, and OAuth tokens, which are stored encrypted and used only for actions you start.
  • Your conversations - the messages you send in Work, OrgTide’s replies, and what you attach to them: screenshots, PDFs, text files, and components from your org.
  • Your saved corrections - the facts you save on Account for every answer to read first: for your whole account (every org), up to 30, kept until you delete them.
  • Your work product - the changes OrgTide builds (with the request that produced them), releases and their notes, packages, deploy history, the snapshot taken before each deploy and the files it sent, version history, org health reports, AI reviews, your org brief, drift scans, and the results of compile checks.
  • Support cases - the messages and attachments you send through the Support page, with the org and page they were sent from.
  • Connector data - if you connect Jira, the key, summary, description, and link of each ticket sent to your OrgTide inbox.
  • Billing data - if you subscribe, your Stripe customer and subscription IDs and your subscription status. Card details are handled by Stripe and never reach OrgTide.
  • Usage records - which AI actions you ran and when, the components involved, the model used, and the underlying cost, used to apply fair-use allowances and to run the service. Cost accounting is internal and never shown to other users.

What we never collect

  • Salesforce record data. OrgTide reads your org’s metadata - code, flows, components, and the descriptions of objects and fields - plus the few setup records it needs: your org’s name and type, your own user’s permissions, and the object and field permissions of the profiles and permission sets you ask it to change, and - only when Salesforce’s answer to starting one of your deploys was lost - the org’s list of recent deploys, to find out whether it started. It never reads your Accounts, Contacts, Opportunities, or any other business records.
  • Production browsing. Production orgs can only be connected as deploy targets. OrgTide reads from them only to verify identity at connect time, to capture a rollback snapshot before a deploy you approved, to run a drift comparison you explicitly request, and - when a release you promote changes existing fields - to check that production’s copy of those fields is still the one the change was made from - metadata only, in every case.
  • Payment card details. Checkout and the billing portal are hosted by Stripe.

How AI processing works

When you ask a question, request a review or a build, or run an org health check, OrgTide sends Anthropic’s API what that task needs: your message and the earlier messages in the conversation, your saved corrections, the attachments you added, and the relevant metadata - for example the source of components you attach or ask about, descriptions of the objects your request names, your org brief, or class bodies for a health check. When a question needs current information, OrgTide can use Anthropic’s web search, with a search query based on your question. Per Anthropic’s API terms, API inputs and outputs are not used to train their models. OrgTide does not train AI models on your data either.

Who processes your data

  • Clerk - sign-in, account management, and bot protection at sign-up.
  • Render - application hosting and the Postgres database where your data is stored.
  • Anthropic - AI processing, as described above, including web search.
  • Stripe - payments, subscriptions, invoices, and sales tax.
  • Salesforce - the orgs you connect; OrgTide talks to them with the OAuth access you grant.
  • Sentry - error monitoring (error details and request context; no org metadata by design).
  • Cloudflare Web Analytics - privacy-first, cookieless page-view counts on our website and in the app (aggregate visits and referrers; no individual visitor tracking, no cross-site profiles).

Cookies and browser storage

OrgTide uses the session cookies required for sign-in (set by Clerk) and a short-lived cookie that protects the step where you connect a Salesforce org. Your browser also keeps a few things on your device only: preferences such as your theme and preferred model, and work in progress such as text you have not sent yet. No advertising or cross-site tracking cookies. Our analytics is cookieless and does not identify individual visitors.

How long we keep it

Your data is kept while your account is active, with these limits:

  • Conversations - the newest 200 per org; older ones are deleted automatically.
  • Deploy snapshots and the files each deploy sent - the newest 50 deploys per org. A deploy that fails changed nothing, so its copies are deleted right away.
  • Version history - the newest 20 versions of each component.
  • Health reports, drift scans, AI reviews, and your org brief - the latest one; a new one replaces it.
  • Org sign-in tokens - deleted after 30 days without use; reconnect the org to continue.
  • Everything else (saved changes, releases, deploy history, usage records, support cases) - until you delete it or your account.

Disconnecting an org and deleting your account

Disconnecting an org deletes its stored connection and tokens. The work you did in that org stays in your account - reconnecting the same org brings it back - until you delete your account. You can also revoke OrgTide’s access from Salesforce Setup at any time (Connected Apps OAuth Usage).

Deleting your account from the Account page cancels any subscription immediately, then deletes your org connections, conversations and attachments, work product, deploy history, usage records, support cases, connector data, and billing records, and finally your sign-in account at Clerk. What remains: Stripe keeps its invoices and payment records for accounting and legal reasons; we keep a log of administrative actions taken on your account (such as a plan change); and copies in our hosting provider’s encrypted database backups expire within 7 days.

Security

  • Data is encrypted in transit (TLS). Our database and its backups are encrypted at rest (AES-256) by our hosting provider.
  • Salesforce tokens are additionally encrypted by OrgTide (AES-256-GCM) and are never sent to your browser.
  • Everything you store is separated by account and by org.
  • Production orgs get extra guardrails: deploy-target-only access, check-only validation, typed confirmations, and a rollback snapshot before every deploy.
  • Our admin tools show account emails, plans, connected org names and usernames, usage and deploy records, and support cases - not your conversations or code. We access other stored data only to run the service, to fix a problem you report, or when the law requires it. Administrative actions are logged.
  • The rules every change follows - your approval before anything is saved to your org, Apex tests, the safety scan, inactive flows, rollback - are in the Guide’s safety model.

Your choices

You can download any change or release as a standard Metadata API zip, export your org’s metadata, and delete your account at any time. Depending on where you live, you may have rights to access, correct, delete, or receive a copy of your personal data - email us and we will help.

Children

OrgTide is a tool for Salesforce professionals and is not directed at children.

Changes

We may update this policy. Material changes are announced in the app before they take effect, and the “Last updated” date above always shows the current version.

Contact

Privacy questions? Email support@orgtide.com, or use the Support page inside the app.