Privacy Policy
What Sarga collects, why, who else handles it, how long it is kept, and how to have it removed.
Last updated: 18 November 2026
Who we are
Sarga is a marketing operating system made by Sarga Inc., a Delaware corporation ("Sarga", "we"). This policy covers the Sarga web app at app.sarga.ai, its API, and the pages on sarga.ai. Questions: support@sarga.ai.
Organisations use Sarga to plan, write, review, approve and publish their marketing. For the content and records an organisation puts into Sarga, that organisation decides what happens to them and Sarga processes them on its behalf, under its agreement with us.
For your account details, product events and the security of the service, Sarga decides how they are used, as described here.
What we collect
Your account
Your name, email address, role, the organisation you belong to, a hash of your password (never the password itself), and, if you turn it on, a two-factor authentication secret, stored encrypted. If your organisation uses single sign-on, the sign-in details your identity provider sends: email, name and group claims.
What your organisation puts into Sarga
Campaigns and their content, images and videos, brand guidelines, rules, claims and their evidence, review results, approvals and comments, and the signed audit record of who did what and when.
Accounts you connect
When an admin connects a website, social media, email, analytics or tag-management account (for example WordPress, Shopify, HubSpot, Facebook, Instagram, Threads, LinkedIn, X, TikTok, Pinterest, YouTube, Google Business Profile, Mailchimp, Klaviyo, Google Analytics, Search Console or Google Tag Manager), Sarga stores:
- the access tokens or keys that let Sarga act for you, encrypted, and never shown again once saved;
- the name and id of the account and of what you chose it should point at (a Page, board, location, property, container or audience);
- a record of each item Sarga published there: which approved version, where, its address and id, who clicked Publish, and when;
- the numbers Sarga reads back about those items, as the platform reports them (for example views, reactions, clicks, opens), and for Google Analytics and Search Console, numbers for those pages or your site;
- for Google Tag Manager, the list of tags in your live container, so a change can be noticed.
Sarga reads only what those features need: the accounts or places you can choose from, what it published, and their numbers. It does not read your followers, messages or other content in those accounts. Two exceptions you control: with Shopify connected, an admin can copy the store's products into your organisation's offers; with Mailchimp connected, a connection test lists your audiences' names and sizes.
Outside MCP servers
An admin can connect an outside MCP server (a vendor's tool server) and allow some of its read-only tools. When an AI client your organisation authorised asks Sarga to call one, Sarga calls it and passes the answer back to that client. Sarga records that the call happened, which server and which tool, but does not store the answer. What such a tool returns depends on the tool the admin allowed.
How you use Sarga
Product events (which page or feature was used, how long it took, whether it worked), with your browser's user agent and IP address. Kept for up to 400 days.
Cookies and browser storage
Sarga does not use advertising or third-party tracking cookies. The web app keeps your signed-in session and a few settings (such as a chosen image engine) in your browser's local storage.
How we use it
- To provide Sarga: generate and review content, route approvals, publish what you approve to the accounts you connect, read back results, and keep the audit record.
- To keep it secure: authentication, rate limits, abuse prevention and investigating incidents.
- To support you and send service email: invitations, password resets, digests and notices.
- To understand how Sarga is used and improve it, from product events.
Improving Sarga's reviews
Sarga trains no foundation models. One defined exception, stated plainly: governance review records (the content reviewed, the model's verdict, and the reviewer's eventual decision) are retained to train a future Sarga-owned reviewer model. No record can reach a training snapshot until 45 days after it was made, and snapshots are de-identified. Each review may also go to a second, open-weight model on Sarga's own account, only to measure how often the two agree (listed on the sub-processors page). An organisation whose agreement with Sarga excludes its data from training produces no such records and no second review. Data from connected platforms is never part of these records.
We do not sell personal information and do not use it for advertising.
Data from Google, Meta and other connected platforms
Data Sarga receives from a connected platform is used only to provide the feature you connected it for: publishing what you approved, showing what was published and its results, and noticing tag changes. It is not used for advertising, not sold, not transferred to anyone else except as needed to provide those features or required by law, not read by people at Sarga except with your permission for support, security or the law, and not used to train AI models.
Sarga's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Sarga's YouTube connection uses YouTube API Services. By connecting YouTube you agree to the YouTube Terms of Service, and Google's handling of your data is covered by the Google Privacy Policy. You can remove Sarga's access to your Google account at any time at myaccount.google.com/permissions.
To remove Sarga's access to any connected account, see Data deletion.
Who else handles it
Sarga uses service providers to run the product: hosting and the database, web delivery, email, single sign-on if you turn it on, file storage, and one AI provider for a measurement lane. Each is listed, with what it receives and where, on the sub-processors page.
When you use your own AI provider keys, content goes to that provider under your account with it. When your organisation has not added its own key for a provider, Sarga uses its own account with that provider (Anthropic, OpenAI or Google) to generate and review content, and its OpenAI account to index content for search, and those providers then process that content for Sarga.
Publishing sends the approved content, and any approved image or video, to the account you chose, at the moment a person clicks Publish. Sarga gives the platform a link to the image or video that expires after an hour.
We may disclose information if the law requires it, or to protect the rights and safety of people and of Sarga. If Sarga is reorganised or sold, this information may pass to the successor under this policy.
How long we keep it
- Account and organisation data: while the organisation uses Sarga, then until it is deleted on request.
- The audit record: kept with the organisation's data, because it is the evidence of who reviewed and approved what.
- Product events: up to 400 days.
- Connection tokens: until the connection is disconnected or the organisation is deleted. Sign-in hand-offs to a platform expire after 15 minutes.
Deleted data may remain in database backups until those backups expire.
Your choices and rights
You can disconnect any connected account in Settings, and your organisation's admin can remove you. You can ask us for a copy of your personal data, to correct it, or to delete it, by emailing support@sarga.ai from your account's address. Where your organisation decides what happens to its data, we will pass your request to it.
When we delete a person's data, their name and email are removed and the records they authored are anonymised. Signed audit entries that prove a governance decision (for example who approved a release) keep a pseudonymous reference to that person, because they are the evidence the record exists for.
If you are in the European Economic Area or the United Kingdom
Sarga relies on these legal bases: performing its contract with your organisation (providing the service); its legitimate interests in securing and improving the service; meeting legal obligations; and your consent where it asks for it, which you can withdraw. You can ask for access, correction, deletion, restriction, a portable copy, or object to processing, and you can complain to your data protection authority. Sarga stores data in the United States; transfers from the EEA and the UK rely on the European Commission's Standard Contractual Clauses and the UK addendum where they are required.
If you are in California
You can ask what personal information Sarga holds about you, and for it to be corrected or deleted. Sarga does not sell or share personal information for cross-context behavioural advertising, and will not treat you differently for using these rights.
We answer requests within the time the law sets.
Security
Data travels encrypted. Connection tokens, keys and two-factor secrets are encrypted at rest. The server scopes every request to your organisation, and the database also enforces row-level security on customer requests. More on the Trust Center.
Children
Sarga is a business product and is not meant for anyone under 16.
Changes
We will post changes here and change the date at the top. If a change materially affects how we use personal data, we will tell organisation admins by email.
Contact
Sarga Inc. Email support@sarga.ai.