CMS
For developersFor clients
How it worksPricingFAQDocs
Log inStart free
For developersFor clientsHow it worksPricingFAQDocsLog inStart free

Privacy

What we keep, and why.

Last updated 10 September 2026. Tusk CMS is operated by Emile de la Rey trading as Napkin Group (ABN 38 586 173 074), Queensland, Australia. We handle personal information in line with the Australian Privacy Act 1988 and the Australian Privacy Principles. Questions: admin@oryxbga.com.

Who this covers

This policy covers studio owners and their staff, the client users a studio invites, and anyone who emails us. For content that clients put into a site, the studio decides what is collected and why; we store and process it on the studio’s instructions. Studios should give their own clients a privacy notice that covers Tusk.

What we collect

  • Account details. Your name, email address and a hashed password. If you sign in with Google or Microsoft, the account identifier they give us. If you turn on two-factor sign-in, the secret needed to check your codes. For studios, the studio name and plan.
  • Website content. The words, photos and files you and your clients put into a site, and the pages and fields you define. Photos are re-encoded on upload and any embedded metadata, such as location and camera details, is removed.
  • Activity. Who published, invited, signed in or changed a setting, and when. Studios see this for their own sites.
  • Billing. Handled by Stripe. We keep the customer and subscription identifiers Stripe gives us. Card details never touch Tusk.
  • Technical data. Your IP address, kept for 15 to 60 minutes to rate-limit sign-in and other requests. Our hosting provider keeps request logs for a short period to keep the service running.
  • Support. The emails you send us, and our replies.

How we collect it

Mostly from you, when you sign up, edit content or email us. When a studio invites a client, we get the client’s name and email from the studio. When you sign in with Google or Microsoft, we get your identifier and email from them. When you subscribe, Stripe tells us the outcome of payments, not your card.

Why we use it

  • To run Tusk: sign you in, store your content, hand it to your build, and show studios their activity.
  • To bill studios and keep accounts.
  • To send service emails: invitations, sign-in links, receipts, failed-payment notices, and notices about changes to Tusk or these terms.
  • To keep the service secure: rate limiting, detecting abuse, and investigating incidents.
  • To answer support requests and meet legal obligations.

We do not use your information for advertising, we do not sell it, and we do not send marketing email unless you have asked for it. If we ever start, you will be able to opt out from each message.

What we do not do

  • We do not sell or share personal information with advertisers or data brokers.
  • We do not read your clients’ content except to provide support you ask for or to investigate abuse.
  • We do not put personal information in links. Invitations carry a random token that expires.
  • We do not run analytics or advertising trackers on Tusk.

Who can see what

A client sees only the sites they have been given access to. A studio sees only its own sites and clients. Tusk staff can access accounts to provide support or keep the service secure, and every such access is logged.

Who we share it with, and where it is stored

We use a small number of providers to run Tusk. They process data on our behalf under their own terms and security commitments, and only to provide their service to us.

  • Vercel hosts the application and stores uploaded files in Vercel Blob. Our hosting region is Sydney, Australia. Vercel is a United States company and some of its systems, such as logs and its network edge, run outside Australia.
  • Neon runs the Postgres database that holds accounts, content and activity. Neon is a United States company.
  • Stripe handles payments and holds card details. Stripe operates in the United States and other countries.
  • Resend sends our email. Resend is a United States company.
  • Google or Microsoft, only if you choose to sign in with them. They tell us who you are; we do not send them your content.

Because of this, personal information may be stored or accessed outside Australia, including in the United States. Before we use a provider we check it has reasonable security and privacy commitments. We may also disclose information where the law requires it, or to a business that takes over Tusk, in which case this policy continues to apply and we will tell you.

How long we keep it

  • Account details, content and activity: while the studio is open.
  • Closed studios: we keep the data for 30 days so it can be exported, then delete it.
  • Backups: taken nightly and kept in Vercel Blob for a limited period, then overwritten. Deleted data drops out of backups as they roll over.
  • Rate-limit counters: 15 to 60 minutes.
  • Billing records: as long as Australian tax law requires, which is generally five years.
  • Support email: as long as it is useful for helping you.

Security

Connections to Tusk are encrypted. Passwords are stored as hashes, never in plain text. Session cookies are signed so they cannot be forged. Two-factor sign-in is available. Uploaded photos are re-encoded and stripped of metadata. Staff access to accounts is logged. Data is backed up nightly. No system is perfectly secure, so keep your password private and use two-factor sign-in. If a breach is likely to cause serious harm to people whose information we hold, we will tell them and the Office of the Australian Information Commissioner as the law requires.

Access and correction

You can see and change your name and email in your account settings. You can ask for a copy of the personal information we hold about you, ask us to correct it, or ask us to delete your account. Studios can export everything in their studio as a zip file at any time, and can close the studio from the dashboard, which deletes its sites, pages, media, clients’ seats and activity after 30 days. Email admin@oryxbga.com for anything else and we respond within 30 days. We may need to confirm who you are first. If we cannot do what you ask, we will explain why.

If you are a client user, your studio controls the content in its sites. Ask the studio first about content; ask us about your own account.

Complaints

If you think we have handled your information badly, email admin@oryxbga.com with the details. We will acknowledge it, look into it, and reply within 30 days. If you are not happy with our answer, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

Cookies

One cookie, oryx_session, keeps you signed in for up to 30 days. It is signed, holds no personal details, and is needed for Tusk to work. There are no tracking or advertising cookies. If we add analytics later, we will update this page first.

Children

Tusk is a business tool and is not aimed at children. You must be at least 18 to open a studio. If you believe a child has given us personal information, email us and we will remove it.

If you are outside Australia

Tusk is sold worldwide. If you are in the United Kingdom, the European Union or another place with its own privacy law, this section adds to the rest of the policy.

  • We process your information to perform our contract with you, and for our legitimate interests in keeping Tusk secure, supporting you and improving it. We rely on consent only where we ask for it, such as optional sign-in with Google or Microsoft.
  • You have the right to access, correct, delete and export your information, to object to or restrict some processing, and to complain to your local privacy regulator. Use the contact below.
  • We are based in Australia and not established in the UK or EU. We have not appointed a representative there yet. Your information is stored in Australia and the United States by the providers named above.
  • For content that a studio puts into its sites, the studio is the controller and we act on its instructions. Contact us if your studio needs a written data processing agreement.

Changes

If this policy changes in a way that matters, we tell studio owners by email before it takes effect. Smaller changes are posted here with a new date at the top.

Contact

Emile de la Rey trading as Napkin Group, ABN 38 586 173 074, Queensland, Australia. admin@oryxbga.com.

CMS
For developersFor clientsPricingDocsFAQLog inContact
Tusk CMS · an ORYX productPrivacyTerms