Privacy Policy

Your Avyn account keeps your email address, the name and picture you add, your theme and display preferences, your notification choices and the personal instructions you give the AI builder.

Kept: Until your account is deleted. Stored: Avyn's control plane (Supabase, Sydney).

For each organisation Avyn keeps its name, the address used in its links, its logo, plan and default region, the instructions it gives the AI builder for every app, its credit and Cloud credits balances, whether its apps show the Avyn badge, whether its profile is public, whether single sign-on is required, and its Stripe customer id.

Kept: While the organisation exists; purged 7 days after the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Avyn keeps who belongs to each organisation and their role, each invitation (the invited email address, the role, who sent it and a one-way hash of the invitation link), which apps each teammate can open, the apps they mark as favourites and when they last had an app open.

Kept: While the organisation exists; a teammate's membership and app access go when they are removed. Stored: Avyn's control plane (Supabase, Sydney).

For each app Avyn keeps its name, address, region and the prompt it was built from, its thumbnail, every build with its versions, the app's code at each version, checkpoints and reverts, the roadmap's initiatives and milestones, the agent's requests for approval, audit and search-engine review results, and each publish and deployment with the provider identifiers and short-lived tokens it uses; when an app was made by remixing or duplicating another, Avyn keeps which app and organisation it came from and who made the copy.

Kept: Until the app is deleted. Stored: Avyn's control plane and file storage (Supabase, Sydney).

Each app's settings are kept for it: its branding and sharing image, its sign-in options and redirect addresses, the outside addresses it may reach, which agent tools need approval, its scheduled jobs and their queued runs, and its backup schedule.

Kept: Until the app is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Avyn keeps each app's avyn.cloud address, any custom domain connected to it with its DNS records and verification state, and an organisation's or app's previous address after a rename so visitors are redirected.

Kept: Until the app is deleted; a previous address stops redirecting and is removed after 30 days. Stored: Avyn's control plane (Supabase, Sydney).

Avyn keeps each organisation's subscription (its plan, billing period, status and Stripe's subscription id), its credit grants and add-ons, an append-only ledger of credits granted, reserved and used, and the ids of the Stripe events it has processed; card details are entered on Stripe's pages and stay with Stripe.

Kept: While the organisation exists; purged 7 days after the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

An agent's name, description, tags, folder, instructions, settings and published versions are kept for the organisation in Avyn's control plane (Sydney), and every member of the organisation can see, edit and run its agents. A personal skill a member attaches to an agent is used in every member's runs of that agent while it stays attached.

Kept: Until the agent or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

When a member connects a service to an agent, Avyn keeps that service's sign-in sealed with encryption on its own server, and the agent uses it in its runs, whichever member starts them; members of the organisation see which services are connected, who connected each one and when, never the sign-in itself. Files the agent writes to its workspace are stored privately on Avyn's server, and only that agent's runs can read them.

Kept: Connected services: until the service is disconnected, or the agent or the organisation is deleted. Workspace files: until the agent or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Files added to an agent (images, PDFs, text, CSV and Markdown) are stored privately for the organisation, read when the agent runs, and every member of the organisation can open them.

Kept: Until the file, the agent or the organisation is deleted. Stored: Avyn's file storage (Supabase Storage, Sydney).

Each run of an agent is kept for the organisation in Avyn's control plane (Sydney): when and how it started, the version it ran, its status, the credits it spent, and each step's kind, name, outcome and a short note of what it did (never a connected service's full reply), readable by every member of the organisation.

Kept: Until the agent, the conversation the run belongs to, or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

AI gateway calls record the model, units, cost and latency of each request, and prompts and responses are never stored.

Kept: 400 days. Stored: Avyn's control plane (Supabase, Sydney).

Analytics keeps each visit's coarse region and city beside its country, taken from the hosting platform's location headers, never the visitor's address; the visitor hash is salted daily.

Kept: 400 days. Stored: Avyn's control plane (Supabase, Sydney).

Published-app analytics count visitors by a hash made with a daily salt and record the country, page path and referrer of each view.

Kept: Salts deleted after 2 days; events kept 400 days. Stored: Avyn's control plane (Supabase, Sydney).

Android package names and signing-certificate fingerprints you add are published at /.well-known/assetlinks.json on your app's address; they are public by design.

Kept: Until removed or the app is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Secrets an app uses are sealed with encryption: the values an owner adds in Secrets, its sign-in provider and runtime keys, the client secret of its sign-in service, and an organisation's app store credentials. Each runtime key is also recorded as a one-way hash, which every request to Avyn's runtime is checked against, and a one-time sign-in code is kept only as a one-way hash, with its sign-in details sealed.

Kept: Until removed or the app is deleted; app store credentials until removed or 7 days after the organisation is deleted; a one-time sign-in code until it is used, or after it expires, at the app's next sign-in. Stored: Avyn's control plane (Supabase, Sydney).

When an app moves between organisations, Avyn keeps the transfer record with the steps that ran and both organisation ids.

Kept: 12 months. Stored: Avyn's control plane (Supabase, Sydney).

Sign-in events in an app record the IP address, city and country of each attempt.

Kept: Until the app is deleted. Stored: The owner's app database (Neon, Sydney).

Credit auto-reload settings and the last reload error are stored for the organisation.

Kept: Until the organisation turns auto-reload off or is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Backups of an app's database, with its files when chosen, export archives, the record of each restore, and the records and reports of data and user imports are kept for the app; before a restore, a copy of the database as it was is kept in the app's own database project.

Kept: Daily and manual backups 7 days and weekly backups 14 days; export archives 24 hours; the copy made before a restore 7 days; restore and import records until the app is deleted. Stored: Avyn's control plane and file storage (Supabase, Sydney); the copy made before a restore in the app's database project (Neon, Sydney).

Recipient lists for a broadcast email are stored encrypted while the broadcast sends.

Kept: 30 days, then purged. Stored: Avyn's control plane (Supabase, Sydney).

Build transcripts keep the agent's messages and steps for each build, including short, secret-redacted excerpts and diffs of the app's own code, the prompts of generated images and the files a person attaches to a prompt.

Kept: Until the app is deleted. Stored: Avyn's control plane and file storage (Supabase, Sydney).

When an agent is connected to a team chat, code host, issue tracker or messaging app, the messages that mention it, the thread they sit in and the agent's replies are stored as a conversation of the organisation, and the app's sign-in or bot token is sealed on Avyn's server and never shown again.

Kept: Conversations: until the conversation, the agent or the organisation is deleted (disconnecting a channel keeps them). Thread links: until the conversation is deleted or the channel is disconnected. Sealed sign-ins: until the channel is disconnected. Event ids used to drop repeated deliveries: at least seven days, removed as later deliveries arrive. Stored: Avyn's control plane (Supabase, Sydney).

When you turn on a chat integration, Avyn keeps your sign-in for that service sealed with encryption, with the service's client details, its list of tools and which of its tools you have allowed, set to ask, or blocked, and only you can see it. The service's replies are not stored: the build's record keeps only which tool ran and how much it returned, though the agent may quote a reply in the build chat, which teammates who can open the app see.

Kept: While the integration is turned on; deleted when you turn it off, when you leave the organisation, or with your account or the organisation. Stored: Avyn's control plane (Supabase, Sydney).

Payment events from Stripe are stored with their identifiers only, never card data, customer details or secrets.

Kept: Until decided. Stored: Avyn's control plane (Supabase, Sydney).

Product photos you add to a product are stored in Files and, up to eight images, sent to Stripe in the United States as the product's images; videos stay in Avyn's storage in Sydney.

Kept: Until the product or the app is deleted; when a file in use is purged from Files, its row goes at once, while the product's saved image address and its Stripe images stay until the product is saved again. Stored: Stripe (United States) for the images; Avyn's control plane (Supabase, Sydney) for the rows.

For commerce in an app, Avyn keeps the products, prices, features and coupons the owner creates, the app's commerce settings, the organisation's Stripe account details (its id, business name, country, currency, mode, whether it can take payments and payouts, and what Stripe still asks of the account before it can) and the delivery record of each payment event passed to the app.

Kept: Until the app is deleted; the Stripe account details until 7 days after the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Tokens for connected software such as Xero, Google and Microsoft 365 are sealed with encryption and are never readable by members.

Kept: Until the connection is removed. Stored: Avyn's control plane (Supabase, Sydney).

When an app calls a connector, Avyn's server logs record which connector and operation it called, the reply status and how long it took, never the key or what was sent and received.

Kept: Up to 30 days, depending on the hosting platform's log retention. Stored: Avyn's platform logs (Vercel).

API keys an owner adds for an app's connectors are sealed with encryption, shown again only as their last four characters and never readable by members.

Kept: Deleted when the connector is turned off or the app is deleted; a key added for the whole organisation is deleted when it is turned off for the organisation or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Files attached to a chat conversation are stored privately for that conversation: only people who can read the conversation can open them, and a public link opens them through short-lived signed links issued by Avyn's server.

Kept: Until the conversation is deleted; files of a conversation removed with its author's account stay private, unreadable by anyone, until the organisation's files are deleted. Stored: Avyn's file storage (Supabase Storage, Sydney).

A conversation shared by public link can be read by anyone who holds the link, without signing in, until the conversation is made private or team-only again, its organisation is deleted, or its author leaves the organisation or deletes their account: it shows every message, the assistant's replies, what connected services returned and the attached files, but no names, avatars or organisation details. Avyn keeps only a one-way fingerprint of the link, never the link itself.

Kept: Until the conversation is made private or team-only or is deleted, its organisation is deleted, or its author leaves the organisation (the link stays off if they rejoin). Stored: Avyn's control plane (Supabase, Sydney).

Chat conversations keep each message, the assistant's replies, the steps it took and the replies of any connected services it used; a general conversation belongs to the person who started it, and teammates can read it only when that person shares it with the team. What a step waiting for your confirmation would send is kept where no member can read it, and deleted once you answer.

Kept: Until the conversation or the organisation is deleted; a person's own general conversations also go when their account is deleted. Stored: Avyn's control plane (Supabase, Sydney).

When you answer "Was this helpful?" on a help page, Avyn keeps the page, your yes or no and the time, with your account if you are signed in; nothing you type is kept.

Kept: Until Avyn deletes it; your account is removed from the answer when the account is deleted. Stored: Avyn's control plane (Supabase, Sydney).

When an owner buys a domain, Avyn keeps the order (the domain, its price and GST, its state, the registrar's reference and the Stripe payment ids) and the registrant's name, business name, address, phone, email and, for a .au domain, the ABN or ACN and eligibility type; the registrant details go to the domain registrar, which publishes them as the domain's registry requires. An order never paid has its registrant details cleared a day after it was started.

Kept: Until the app or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Email that an app sends is delivered through Resend, which processes the recipient address and message.

Kept: Resend's own retention for delivery records. Stored: Resend (United States).

Email history keeps each message's subject and shows its recipients masked, and suppressions and unsubscribes are stored as keyed hashes with a masked address.

Kept: Until the app is deleted. Stored: Avyn's control plane (Supabase, Sydney).

For email your apps send, Avyn keeps each sending domain with its DNS records and verification state, the sender names and addresses, the delivery events Resend reports for each message (the event type and any bounce reason), and the organisation's bounce and complaint rates.

Kept: Sending domains and the organisation's bounce and complaint rates until 7 days after the organisation is deleted; an app's sender addresses and the delivery events of its messages until the app is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Search embeddings are numbers derived from an app's own data so it can search by meaning; they live in the app's own database and are deleted with the app. The text they are made from passes through Avyn's AI gateway to the embedding provider and is not kept.

Kept: Until the app is deleted. Stored: The app's database, in its region.

A grader's wording, its history, and every evaluation's questions, replies and grades, plus grades given to live runs, are kept for members of the organisation. Evaluation replies are generated for the test alone and are not conversations.

Kept: Until a member deletes the grader or the evaluation, or the run, the agent or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

When a guardrail warns or blocks, Avyn keeps a short excerpt of the message, tool call or reply that tripped it, with secret-shaped values removed, so the team can see what was stopped and why.

Kept: Until the run, the agent or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Cloud credits auto-reload settings (threshold, amount, monthly maximum), the last reload error and who last saved them are stored for the organisation.

Kept: Until 7 days after the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Avyn keeps a record of every Cloud credits top-up, auto-reload, daily hosting usage charge and correction, in Australian cents, for each organisation.

Kept: While the organisation exists; purged 7 days after the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

An agent's improvement goal, priorities, notes and schedule, and each analysis's report of what it reviewed, found, changed and spent, are kept with the agent for the organisation. The analysis reads the agent's recent runs and the team's ratings and writes its findings as issues.

Kept: Until the agent or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

An issue found in an agent, by a member, by an analysis or by the agent itself, with its evidence, proposed fixes and the team's comments, is kept with the agent for the organisation. Evidence names runs and never copies their content, and email addresses and phone numbers in titles and summaries an analysis or the agent writes are masked.

Kept: Until a member deletes the issue, or the agent or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

When you start, Avyn keeps the description of the app you typed, your answers to the onboarding questions, including how you heard about Avyn, the plan it suggested and the plan you chose; for each AI call made while helping, it records the model and the cost, not the text.

Kept: Until 7 days after the organisation is deleted; the answers tied to your account until your account is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Avyn keeps a log of changes to an organisation, such as invitations, role and ownership changes, app access, single sign-on, app store credentials, deletion and restore, with who made each change and when.

Kept: Until 7 days after the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

For each passkey you add to your Avyn account, Avyn keeps its public key, the name you give it, when it was added and last used, whether your device syncs it, the authenticator's model identifier and a sign-in counter; the private key never leaves your device.

Kept: Until you remove the passkey or delete your account. Stored: Avyn's control plane (Supabase, Sydney).

Avyn keeps a record of each app's build workspace and version previews (the workspace's id, its state and when it was last used) and the short-lived, sealed links that open a preview.

Kept: Until the app is deleted; preview links expire. Stored: Avyn's control plane (Supabase, Sydney).

Private files in an app's Files & Media library are stored for that app and served only through short-lived signed links.

Kept: Until they are deleted. Stored: Avyn's file storage (Supabase Storage, Sydney).

Each push notification an app sends is logged with its title, message, audience, who sent it and how many devices it reached or failed to reach.

Kept: Until the app is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Push notification subscriptions store the browser endpoint, its keys, the user agent and the visitor ID of the opt-in.

Kept: Until the subscriber opts out or the app is deleted. Stored: The owner's app database (Neon, Sydney).

Each person who shares a referral link has a referral code kept for them, and referral attributions record that an organisation signed up through that link, when, and whether it qualified; no name or email is kept in the link or the cookie.

Kept: Attributions 24 months; a person's referral code until their account is deleted. Stored: Avyn's control plane (Supabase, Sydney).

When a member edits a row in the Database section, Avyn keeps a masked, size-limited snapshot of the row before and after the edit.

Kept: Until the app is deleted. Stored: Avyn's control plane (Supabase, Sydney).

A member's thumbs up or down on an agent's run, with an optional note, is kept with the run and shown to the whole team.

Kept: Until the member clears it, or the run, the member's account or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

A published app's runtime log lines are kept so the owner can read them in the Backend section.

Kept: 7 days. Stored: Avyn's control plane (Supabase, Sydney).

An app listed in the showcase publishes its title, description, screenshots and the organisation's name and logo.

Kept: Until the owner unlists the app. Stored: Avyn's control plane (Supabase, Sydney).

When an organisation is created, Avyn records how its owner arrived: the landing page and tab, the referring site's host name, any campaign tags in the link, and the example prompt they started from and whether they edited it, and an anonymous id of the landing visit.

Kept: Until 7 days after the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Skills that members write are stored with secrets redacted, and a personal skill is visible only to its author.

Kept: Until the author deletes it. Stored: Avyn's control plane (Supabase, Sydney).

When an app sends a sign-in code by text message, Avyn keeps a record of the send (a keyed one-way hash of the phone number, the time, the status and the provider's reference) to apply the monthly limit and show usage; it never keeps the number or the code. The SMS provider receives the number and the message to deliver it.

Kept: 90 days. Stored: Avyn's control plane (Supabase, Sydney).

A deleted organisation stays offline but intact for 7 days so its owner can restore it; after that every app, database, file and row is purged.

Kept: 7 days, then purged. Stored: Avyn's control plane (Supabase, Sydney).

Single sign-on keeps each identity provider's name, protocol, metadata or issuer address and client ID, the email domains you claim and verify, and the client secret encrypted; the identity provider and its vendor receive your teammates' sign-ins.

Kept: Until the provider is removed or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Messages you send through Help and feedback are kept with the kind of request, the page you were on, your latest build, any attachments and the error report reference, so Avyn can answer without asking again.

Kept: Until 7 days after the organisation is deleted; your account is removed from a message when the account is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Two test accounts exist only in an app's preview so browser tests can sign in and check that one user cannot see another's records; they hold no real person's data and are deleted with the app.

Kept: Until the app is deleted. Stored: The owner's app database (Neon, Sydney), preview branch only.

A test case holds a question a member wrote, imported or took from an agent's run, with an optional expected answer, tags and notes. Imported files may carry personal details, which the team controls and deletes with the case or the dataset.

Kept: Until a member deletes the case or its dataset, or the agent or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Browser test runs keep their screenshots, recordings and step transcripts for members of the organisation.

Kept: Until the test or the app is deleted. Stored: Avyn's control plane (Supabase, Sydney).

A published app whose theme uses a Google font loads the font files from Google Fonts, so each visitor's browser sends its IP address and browser details to Google when a page needs the font; no cookies are set and Avyn receives nothing from it.

Kept: Google's own retention for font requests. Stored: Google Fonts (Google's global network).

What a service or a caller posts to an agent's web address, or the event that started a run, is stored with the run after secret-shaped values are removed, bounded to 64 KB, so the team can read what the agent received.

Kept: Until the run's agent, the conversation the run belongs to, or the organisation is deleted; an event's own record also goes when the trigger that received it is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Avyn keeps usage figures for each build and app (the AI work of each build turn, daily and monthly storage, bandwidth and email counts, and search-by-meaning counts) and each usage alert it has sent, with how many people received it.

Kept: Until the app or the organisation is deleted. Stored: Avyn's control plane (Supabase, Sydney).

Avyn keeps one daily usage figure per resource for each organisation and app (storage, bandwidth, function calls, compute, egress and AI credits) to show the Usage table and run the hosting-cost audit.

Kept: 24 months. Stored: Avyn's control plane (Supabase, Sydney).