> For the complete documentation index, see [llms.txt](https://help.auray.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.auray.ai/privacy-and-your-data.md).

# Privacy and your data

Two documents bind, and this is neither of them. The [Privacy Policy](https://app.auray.ai/privacy) lists what is stored, where it goes and how long it stays. The [Terms](https://app.auray.ai/terms) cover billing, what you may do with what you make, and what is forbidden. Both pages are Indonesian first, then the same text in English.

This page answers the four things people actually write in about.

## What sits on our servers, and what only sits in your browser

On the servers: your account details, everything you generate — including drafts you never ran — the photographs you upload for 3D and Video, your Messages conversations, and the contents of your Code projects. Payment goes to Stripe; a customer id and a subscription status come back, and card numbers never reach us. Stripe is in test mode on this deployment, so only test cards are accepted and nothing is charged.

There is no third-party analytics. No Google Analytics, no advertising trackers, no pixels.

Not on the servers at all: Notes, Calendar, the files in Finder, the Trash, your wallpaper and your window positions. Those live in this browser and nowhere else.

{% hint style="warning" %}
Because they are only in the browser, they are not in your data export, they are not touched when you delete your account, and clearing this browser's site data destroys them with no copy anywhere. Keep anything that matters somewhere else too.
{% endhint %}

## One kind of upload is not private

A reference image or dialogue track you upload in Video is stored where anyone holding the exact address can read it. The renderer runs on rented GPUs that fetch the file over the internet, and that service refuses private addresses. The address is long and unguessable, but it is not a secret.

Source photographs for 3D are the opposite: private, never fetched from outside, downloaded by us and passed to the renderer. That difference is deliberate — an image-to-3D source is very often a photograph of a person.

## What the training tick-box agreed to

Creating an account takes one tick-box, and it covers three things at once: the Terms, the Privacy Policy, and permission to use work made in Auray to train and improve models. There is no way to create an account with that third part switched off.

A permission you cannot decline without also declining the account is a weak permission, and the thing that makes it real is that you can withdraw it — completely, in seconds, at **Settings → Privacy**. It takes effect the moment you flip the switch.

Four switches, not one, because the categories are not alike:

* **Generated results** — images, songs, videos and 3D models Auray made for you, and the model's replies in Messages.
* **Prompts and lyrics** — the words you write, including what you type in Messages.
* **Photos you upload** — source photographs for 3D and Video. Only ever your own face. Do not switch this on to hand over pictures of other people.
* **Quality signals** — what failed, what you remade, how long it took. No content of any kind.

Whatever those switches say, none of this is ever included:

* **Work made before you agreed.** Each piece of work is marked once, when it is created, against the permission in force at that moment. Older work carries no mark and is never picked up later.
* **Anything you deleted.** A deleted result drops out of training data from the moment you delete it.
* **Anything from Code.** Project files, project instructions and the agent's history carry no training mark at all.
* **Consent given under an older policy.** The Privacy Policy carries a version date — 2026-08-24 today. Your decision is recorded against that date, and when the meaning of the policy changes the date changes with it. Your switches then read off until you choose again, and the Privacy pane says so rather than pretending nothing happened.
* **Accounts made before the tick-box existed.** Those were never included, and training stays off for them until somebody switches it on.

{% stepper %}
{% step %}

### Open Settings → Privacy

Under "Training our models" there are the four switches.
{% endstep %}

{% step %}

### Switch off whatever you want off

Every flip is stored as a new decision. Nothing is edited and nothing is erased, so the record of what you agreed to, and when, stays intact.
{% endstep %}

{% step %}

### Check "Your record"

It shows the date of your last decision and the policy version it was made under. If it says something you did not expect, that is the thing to quote when you write in.
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
Switching a category off stops new work being used. It cannot pull work already in a training set back out of a model that has been trained on it. That is the one consequence turning it off does not undo.
{% endhint %}

## How long results are kept

There is no expiry. Nothing is deleted on a schedule — work stays in your library until you delete it, or until you delete your account.

Deleting one result takes it out of the library at once. Every link to a generated file is signed and lasts fifteen minutes, so any link already handed out stops working inside the quarter hour.

**The file itself is usually still there.** Auray holds a read-only credential for the storage that generated files live in, so deleting a result cuts every route to the file without deleting its bytes. Photos are the exception: the image service that made them holds the write credential, and it is asked to erase them — best effort, and it does not hold up the delete. Songs, videos and 3D models are not erased. The Privacy Policy says this in the same words, and it will keep saying it until deletion reaches that storage.

Deleting your account removes your profile and every row that points at it. The files you uploaded — your avatar, Video reference images and dialogue tracks, 3D source photographs — are deleted from their buckets first, and a failure there does not stop the account going. Generated results in the other storage are not deleted, for the reason above.

{% hint style="info" %}
The Terms say it plainly and it is worth repeating: Auray is not a backup service. Keep your own copies of anything you would mind losing.
{% endhint %}

## Getting a copy, or leaving

**Settings → Account → Your data → Download** gives you one JSON file holding every row we have about you. Rows you deleted are in it too, deliberately: what is held that you can no longer see is part of an honest answer.

Four things are not in that file, and the file says so itself:

* The generated files. Their storage keys are listed, so you can point at any one of them and ask.
* Tokens for services you connected in Code. They are encrypted, and an export is not a place to put credentials. Disconnect them in Code to revoke them.
* The secret half of any API key. Only a one-way hash is stored, so nobody can recover a lost key — us included.
* Abuse reports, because a report names somebody other than the reporter as often as not.

{% hint style="info" %}
The Privacy Policy still says a button for this "is being built". It is built. That sentence is out of date, not the feature.
{% endhint %}

**Settings → Account → Danger Zone → Delete…** removes the account. You type your email to confirm. There is no undo and no grace period.

To correct rather than delete: name, email and profile photo are all editable in **Settings → Account**.

## Asking us something

Data requests, objections, corrections and complaints go to <privacy@auray.ai>. If your question is about a specific piece of work, the date and the app it was made in are enough to find it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.auray.ai/privacy-and-your-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.