Privacy Policy

1. Who we are

ARIA OS is a product of CeraNova AI, an Australian company. This policy covers aria-os.studio and the ARIA OS application served from it. Our company website at ceranovaai.com has its own policy.

For anything in this policy, contact hello@ceranovaai.com.

2. What we collect on this website

These marketing pages set no cookies and run no analytics tag. See the cookies policy, where that is measured rather than asserted. Our hosting provider records aggregate, cookieless page-view and page-speed measurements that do not identify you.

If you join the beta waitlist, we store what you type into that form:

• your email address (required, so we can reply)
• your name, organisation, how many brands you run, and what you would use ARIA OS for (all optional)

We deliberately do not record your IP address or user agent with a waitlist submission. We use the address to contact you about beta access and for nothing else: no newsletter, no marketing list, no sale or transfer to anyone. Ask us and we will delete your entry.

Joining the waitlist does not create an account. Registration is closed: accounts are created only through an invitation, and the waitlist form touches our authentication system not at all.

3. What we collect when you use ARIA OS

• Account details: your email address, your role, and the teamspace and brands you have access to.
• Authentication events: sign-ins, failed sign-ins, and the address they came from. This is a security record: it is how account takeover is detected, and it is why it is kept even though it is more than we need to run the product.
• Audit events: what was created, changed, published or deleted, and by whom. Written to an append-only, hash-chained log.
• Content you create: pages, media, configuration and anything else you put into the platform. It is yours; we process it to provide the service.
• Product analytics (PostHog): which screens are used and where errors occur, so we can fix what is broken. Attached to your account only where you are identified; it is never sold or shared.

4. Legal basis and retention

• Contract: account, content and configuration data, for as long as your account exists.
• Legitimate interests: security and audit records, and product analytics.
• Consent: the waitlist, which you can withdraw by asking us to delete your entry.

Content and configuration are deleted when your account is closed.

Audit and authentication records are kept for the life of your account and are never deleted. The audit log is append-only and hash-chained: each record is sealed against the one before it, so removing a row would break the chain that makes the rest of it evidence. A security log you can delete on request is a security log an attacker can ask you to delete. What does expire is the identifying detail on those records — a daily job erases the IP address and user agent from every audit record older than 12 months, and the record itself remains.

Product analytics held by PostHog are retained for up to 12 monthsunder that project’s retention setting. Waitlist entries are deleted once the beta closes, or sooner if you ask.

5. Google data: what we request and what we do with it

ARIA OS can connect to your Google Search Console and Google Analytics so it can show you how your own websites are performing. This connection is optional, you initiate it, and nothing about Google is touched until you do.

What we request

Two read-only scopes, and no others:

• https://www.googleapis.com/auth/webmasters.readonly, Search Console: your own site’s impressions, clicks, average position and indexed pages.
• https://www.googleapis.com/auth/analytics.readonly, Google Analytics: your own property’s aggregate traffic reports.

Both are read-only. ARIA OS cannot change your Search Console or Analytics settings, cannot add or remove users, and cannot delete anything. We request no scope for Gmail, Drive, Contacts, Calendar or any other Google service, and we never will for this product.

Why we request it

So that the search and traffic figures shown inside ARIA OS are measurements of your own properties rather than a third-party vendor’s estimate of them. Everything the platform reports about search performance comes from the property that owns the data.

Whether it is stored

Google Analytics is read live, at the moment you look at it. Analytics reports are fetched when a page in ARIA OS needs them and rendered to you. No Analytics figures are written to our database and none are cached between one look and the next.

Search Console is different: we keep a copy of it, deliberately. Google’s Search Console API serves only the last 16 months, so a chart of your search performance over a longer period cannot be drawn from a live request — it has to have been kept. When you connect Search Console we store the daily figures it returns: clicks, impressions, click-through rate and average position, per day, broken down by query, page, country and device. That includes the search terms your site was found for, the pages they led to, and how those positions moved over time, together with the sitemap submissions we make on your behalf.

That copy is stored against your brand alone. It is shown to you and to the people you have given access to in your teamspace, it is not pooled with any other customer’s data, and it is deleted when your account is closed.

Alongside it we store, and nothing beyond this:

• the identifiers that tell us which property to query — your GA4 property ID, measurement ID, Search Console site and verification token;
• the authorisation credential itself, held encrypted in a secrets vault and readable only by our servers, never by a browser, and never written to a log;
• the health of the connection — which scopes Google told us you granted, when it was last checked, whether it is working, and Google’s own message when it is not;
• how many URL inspections we have made against your property today, which is how we stay inside Google’s daily ceiling for it rather than driving your property past it.

Who it is shared with

Nobody.Google data obtained through your connection is shown to you and to the people you have given access to in your own teamspace. It is not sold, not transferred to a third party, not used for advertising, and not pooled with any other customer’s data. The Search Console copy described above lives in our database, which is operated by Supabase (section 7); no other sub-processor receives your Google data, and none of it is ever sent to an AI provider.

Model training, explicitly

Google user data obtained through these scopes is never used to develop, improve or train any generalised or standalone artificial-intelligence or machine-learning model. Not ours, and not a third party’s. It is not sent to any AI provider. Where ARIA OS generates content with a language model, the material sent to that model is the content and brand context you have put into the platform, never your Search Console or Analytics data.

ARIA OS’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How to revoke it

Disconnect the integration inside ARIA OS, which deletes the stored credential immediately, or revoke access from your own Google Account at myaccount.google.com/permissions. Either ends our access at once. Revoking does not delete the ARIA OS content you created; deleting your account does.

6. How your data is protected

• Separation is enforced in the database.Access to a brand’s data is decided by row-level policy in Postgres, not by a check in application code that a future change could skip.
• Credentials are never in the browser. API keys and OAuth tokens live in a server-side vault. No secret value is written to a log, an error message, or a page.
• ARIA OS’s own Google identity is federated rather than a downloadable service-account key. There is no permanent credential file that could be copied, because none is ever created. That statement is about our identity — when you connect your Google account, the authorisation we hold is your refresh token, kept encrypted in the vault described in section 5 and revocable by you at any time.
• Emergency developer access is time-boxed and audited. It needs a consent code issued by an administrator, expires on a hard maximum, and every access it performs is recorded.
• Registration is closed. Nobody can create an account on our systems without an invitation.

7. Who processes data for us

• Supabase: database, authentication and file storage.
• Vercel: application hosting and cookieless traffic measurement.
• PostHog: in-application product analytics.
• Resend: transactional email, including the notification when you join the waitlist.
• AI providers: where you use content generation, the content and brand context you supply are sent to the model provider to produce the draft you asked for. Google Search Console and Analytics data are never included.

Some of these operate outside Australia, so your data may be processed overseas. Each is bound by its own data-processing terms.

8. Your rights

You can ask us for a copy of the personal information we hold about you, ask us to correct it, or ask us to delete it. Email hello@ceranovaai.com and we will respond within 30 days. If you are not satisfied with how we handle a privacy matter, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

9. Children

ARIA OS is a business product and is not directed at anyone under 16. We do not knowingly collect information from children.

10. Changes to this policy

Material changes are published here and, if you have an account, notified to you. The effective date at the top of this page is the date of the version you are reading.