Privacy

Safe AI Labs Pty Ltd (ABN 79 697 222 601) is responsible for the personal information described here. We handle it under the Privacy Act 1988 and the Australian Privacy Principles.

You can browse the site without telling us who you are. An account needs an email address, and buying credits needs a payment method, so neither can be done anonymously.

Account

Your email address, the public keys of any passkeys you add, your workspace name, the members of your workspace and the email addresses you invite. For each signed-in session we keep the browser's user agent so you can recognise the session. Sign-in codes are kept as a hash until they expire.

Billing

Your billing email, and the business name and tax id if you add them. From Stripe we keep the card brand, the last four digits, the expiry date, and a reference to your Stripe customer. We keep your receipts, your credit purchases and your auto top-up settings. Stripe holds the card number. When you create an account we ask for a card, which is not charged, and keep the identifier Stripe gives that card, which tells us when one card is used for more than one account.

API keys

A hash of each key, a masked form for display, its name, its limits and the regions and models it allows. The key itself is shown once and not stored.

Usage record

For every request: time, model, region, token counts, key id and cost. This is what the usage page shows and what you are billed on.

Request logs

For every request: request id, time, model, the node and region that served it, token counts, timings, status code, finish reason, error code, and the key and workspace ids. Nothing in a request log is taken from the prompt or the output.

Chat conversations

If you use the chat in your account, we store each conversation: its title, the messages you send, the replies, and the files you attach. For a PDF or a text file we also store the text read out of it.

Each message is sent to the model with the conversation's earlier messages and its files, as a request from your workspace. It leaves the same usage record and request log as a request made with an API key.

With Search the web on, which it is unless you turn it off in the chat, the model may search the web to answer a message. The search query it writes can repeat words from your conversation. It goes to a search provider in the United States, and the reply can list the pages it used.

If you share a conversation, we keep a record of the link. Anyone who has the link can read the conversation's title and the text of its messages without signing in, until you revoke the link or delete the conversation. Attached files are not shown.

Messages

What you write in the contact form or in a support message, with the email address you send it from.

Page views

For each page of this site you open we keep the page, the site that linked you here, your country and your browser's family, for 30 days, then only daily totals. We count them on our own server, with no cookie or script, and never keep your IP address with them. API requests are not counted this way.

Where you signed up from

If you create an account from a link that names one of our pages for a particular tool, such as /for/openclaw, or carries utm_source or utm_campaign, we keep that page's name and those two values with your account. They travel in the link, with no cookie, and we use them only to count which pages and campaigns bring sign-ups.

IP addresses

Sign-in and contact forms count attempts per IP address to stop abuse. The count is overwritten each window and used for nothing else. Our hosting providers may record IP addresses in their own security logs.

Prompts and outputs of requests made with an API key are not collected. They stay in memory on the node that serves the request for the session, at most 30 minutes after the last request on a key, and are never written to disk or to a log. In us-region, the provider that runs the request keeps nothing, under zero-data-retention terms.

The chat in your account is different: it stores your conversations, as described under What we collect.

Nothing you send is used to train any model, ours or a provider's.

No third-party analytics run on the site or the API, and we do not sell or rent personal information.

• To sign you in, run your workspace and keys, and serve your requests.
• To charge for credits, record usage, issue receipts and keep the financial records the law requires.
• To enforce key limits, rate limits and the terms, and to detect abuse and fraud.
• To answer support and privacy messages and to investigate faults.
• To send email the service needs: sign-in codes, receipts, invites, low balance and security notices. We also email product updates to the address on your account, which you can turn off in Settings or with the unsubscribe link in each one.

We use personal information for another purpose only with your consent or where the law allows it.

• You, and the members of your workspace.
• A chat conversation is shown only to the member who started it, and to anyone that member gives a share link.
• If a member under 18 sends a message the chat's filter treats as a crisis (self-harm, abuse or danger), the workspace's owners are emailed the member's address, the kind of message and the time, never the message. We keep a record of each alert: the member, the kind and the day.
• Safe AI Labs staff who need it to run the service or answer you.
• The service providers listed below, only for the job named, under their own security and privacy terms.
• A court, regulator or law enforcement agency where the law requires it. For requests made with an API key, the usage record and request logs are all there is to give, because prompts and outputs are not kept. A conversation stored by the chat can be required while it exists.
• A buyer of the business, if Safe AI Labs is sold, under this policy.

A request is processed in the region you chose. A prompt sent to us-region is processed by an inference provider we contract with, in or headquartered in the United States, on zero-data-retention terms. A request is never moved to a region you did not choose: a request sent to gbl runs only in a region your key and workspace allow.

A prompt sent to us-region passes through our systems in Australia and a routing service in the United States on its way to the provider. The routing service keeps no prompt or output, only the request's metadata, such as token counts and timing.

Chat conversations are stored in the account database, in Australia. Each message is processed in the first live region your workspace allows.

A web search from the chat is not held to your region: its query goes to the search provider in the United States.

• Prompts and outputs of requests made with an API key: in memory for the session, at most 30 minutes after the last request on a key. In us-region, the provider that runs the request keeps nothing, under zero-data-retention terms.
• Chat conversations, their attached files and share links: until you delete the conversation, or your account or workspace is deleted. A file you attach and do not send is removed by an hourly job once it is 24 hours old. If you are removed from a workspace, your conversations in it, their share links and any file you had not sent are deleted at once, and their files are removed from storage by the same hourly job.
• Request logs: 30 days, then deleted automatically.
• Per-request usage record: 30 days. Hourly totals per key and model are kept with your financial records.
• Page views: 30 days, then daily totals per page, referring site and country.
• Receipts, credit purchases and hourly usage totals: 7 years, because Australian law requires financial records to be kept that long.
• Account, keys and billing details: while your workspace is open, and after that until you ask us to delete them.
• Messages to support: as long as needed to deal with them and any follow-up.

Deleting a conversation in the chat removes its messages, replies and share link at once. Its attached files are removed from storage by a job that runs every hour, and database backups hold the conversation for up to 7 days.

Deleting a workspace in Settings revokes its keys, signs every member out, and deletes its chat conversations and their files. It does not erase your other personal information. To have it deleted, email hello@safeailabs.ai. We delete everything the law does not require us to keep within 30 days and tell you what we kept and why.

• Traffic to the site and the API is encrypted in transit with TLS.
• API keys and sign-in codes are stored as hashes. There are no passwords to leak.
• Access to production systems is limited to Safe AI Labs staff who need it.
• Card numbers never reach our systems.
• Chat conversations and attached files are encrypted at rest.

If a data breach is likely to cause you serious harm, we tell you and the Office of the Australian Information Commissioner as the Notifiable Data Breaches scheme requires. The security page has the detail.

You can ask for a copy of the personal information we hold about you, and ask us to correct it or delete it. Email hello@safeailabs.ai from the address on your account. We reply within 30 days and there is no charge. If we refuse, we say why in writing.

You can change your email address, passkeys, members and billing details in Settings, and download your usage as CSV from the usage page.

If you are in the European Economic Area or the United Kingdom, you also have the right to restrict or object to how we use your information, to receive it in a portable format, and to complain to your local data protection authority. We rely on our contract with you for account, billing, usage and chat information, and on our legitimate interest in running a secure service for request logs and abuse counters.

Email hello@safeailabs.ai with what happened. We reply within 30 days. If you are not satisfied with the answer, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

The site sets one cookie, sail_session, when you sign in. It keeps you signed in and is deleted when you sign out or it expires. Your theme and region choices are kept in your browser's local storage and are never sent to us. There are no advertising or analytics cookies.

An account holder must be 18 or over. An account holder can add a person under 18 as a member and gives their year of birth, which we use to set an age band and do not store. A member under 18 can use only the chat, with replies suited to their age, and cannot see keys or billing. We collect from them only their email address and what the chat stores, as described above. The account holder can remove them, which deletes their conversations.

We post changes on this page with the date they take effect. If a change affects how we use information we already hold, we email workspace owners at least 14 days before it applies.

Safe AI Labs Pty Ltd
Brisbane, Australia
hello@safeailabs.ai