Know what you submit
Job specs, environment variables, dataset links and log tails can be stored. Keep secrets out of them.
Privacy notice
Your data.
In plain view.
What Symbioza receives, why it is used, who it reaches and how to make a request.
Policy dated 29 September 2026.
Expiry is not deletion
Download links expire. Stored artifacts have no automatic deletion schedule in the current notice.
Your choices and requests
Browser analytics choices and account event recording are different. You can ask about, correct or delete data.
A reading guide. The full clauses below contain the detail and exceptions.
Who holds it
Moshe Edri, HaLilach 73, Hodaya, Israel, is responsible for the personal data described here. Write to access@symbioza.dev with any question or request.
1
What we collect
Your email address and an account identifier, from the sign-in provider you choose. We do not ask you to create a profile. Separately, the Contact form lets you provide a name, and you may provide billing details at checkout.
Messages you send through the Contact form: your email address, topic and message, plus your name and job or payment reference if you provide them. We also store a receipt time and identifiers used to recognise retries of the same submission. We use this information to respond, investigate your request and maintain the support record. An email address or reference supplied through the form does not verify ownership of an account or job.
Your jobs: what you submitted — including the image, the command, any environment variables you set and the dataset links you point us at, signed links included — all of which we store as you gave them to us and keep in our backups — what it cost, when it ran, whether it finished, and the hashes of what it produced. Do not put secrets in a job's environment variables, and give a signed dataset link the shortest expiry that covers staging.
Your run's own output: the tail of what your command printed, so we can tell you — and ourselves — why a run ended the way it did.
Your payments: the amount, the date, and the reference the payment arrived with.
A log of calls to the service from your account, so we can tell you when we last heard from it and investigate problems.
How the site and your account pages are used: which pages load and which controls are clicked, the referring site, and the browser and device type, through PostHog, which we run on their servers in the EU. If you accept the cookie banner, one cookie ties your visits together and, once you sign in, to your account. If you reject it, the visit is still counted, but without a cookie and without your account attached to it. The banner governs your browser. Signing in, submitting a job and paying are recorded against your account whichever you choose, and reach PostHog too; for a job that record carries the image name, any GPU requirement you set, your spending limit and, once it runs, the kind of machine it ran on, how long it took and its charge. So is connecting an AI client: the name and version it reports, and whether it came through our Claude Code plugin.
2
What we do not collect
We never see or store card numbers. Payment details are entered on the payment page, not here.
No advertising and no ad-network pixels. The one analytics tool is PostHog, described above, and nothing is sold or shared with anyone for marketing.
We do not use your data, your code or your artifacts to train models.
3
Why we hold it
To run the jobs you ask for, to bill you correctly and show you a statement, to answer you when you write, and to keep the tax and accounting records the law requires us to keep.
4
Who else it reaches
Running a job means it reaches the parties that make it work: the sign-in provider you chose, the provider that processes your payment, the operator of the machine your job runs on, the storage where your artifacts are kept (Cloudflare R2 — the download link you receive is a signed link to it, and names it), and an AI model provider, which receives the image and command your job runs and, when a run ends in a way we cannot explain, a tail of what your command printed. They each get only what their part needs, and none of them get it for their own purposes. The model provider does not train on what we send it. The machine your job runs on is someone else's hardware while it runs. Your job runs on it in its own container, and the machine runs only your jobs — one after another, or two of yours at once when that is arranged with you — never another customer's. It is torn down when your work on it is done, or when the bounded time it is kept for your next job runs out.
Two more services each receive a small part: the identity service that hosts our sign-in (WorkOS), which receives your email address and the account identifier from Google, GitHub or the email you sign in with; and a push-notification service (ntfy) that receives the first 200 characters of a message you send from your account page, so a person is alerted.
Using the site and signing in also reaches PostHog, described in section 1, which processes that on their servers in the EU.
Contact messages are stored in our operator support inbox on the infrastructure that hosts Symbioza. Copies are included in backups stored with Cloudflare R2. The operator may use email to reply to the address you provide.
5
How long we keep it
Job records — the spec as you submitted it, environment variables and dataset links included — and payment records are kept as long as the law requires us to keep accounting records, because they are the evidence behind an invoice; nothing prunes a signed link or a variable out of a stored spec, and our backups carry them too. Artifacts are kept after you collect them; nothing deletes them on a schedule. The download link expires after 24 hours — that is the link, not the file. Ask us and a person removes them. Your account exists until you ask us to close it.
For requests sent through our Contact form, we delete closed requests from our active support records within 90 days after closure. Backup copies expire within a further 30 days. If we need part of a request for an unresolved dispute or a legal obligation, we retain only the relevant material for that purpose and review that need separately. Restoring a backup does not restart these periods.
6
Your rights
You can ask for a copy of what we hold about you, ask us to correct it, ask us to delete it, or object to what we do with it. Write to access@symbioza.dev and a person will answer. If you think we have handled your data badly you can complain to your national data-protection authority.
Deleting an account does not delete the accounting records behind invoices already issued — we are required to keep those.
7
Cookies
Two cookies that stay. One keeps you signed in. The other, only if you accept the banner, lets PostHog recognise your browser between visits; reject it and PostHog sets nothing. Two more exist only while you are signing in — one carries that one sign-in attempt, the other records where you came from if you arrived by a link that said so — and both expire within half an hour. Your banner choice itself is kept in your browser's local storage so we do not ask again. If you arrive from another site or by a tagged link, where you came from — the tags, that site's name and the page you landed on — is kept in this browser's local storage for up to 30 days, holds no identifier, and is sent only with your sign-in.
Questions or requests
A person can help.
Write to access@symbioza.dev to ask about your data or make a privacy request.