Website Privacy Policy

The Short Version

This page describes what happens when you visit sammyai.app and join the waitlist. The Sammy app has its own privacy policy. We don’t sell your data, we don’t train AI models on it, and we keep what we collect minimal and specific. The list below is literal, not a generic claim.

The site and the waitlist are run by Keep DS Pty Ltd (ABN 91 695 408 756), Suite 193, Level 5, 33 Stewart St, Richmond VIC 3121, Australia, which is the controller of the personal data described here.

What We Save When You Join the Waitlist

When you sign up, the following is stored in our database (Supabase):

• Your email address - so we can send you a welcome email and the occasional update.
• A referral code we generate for you (e.g. a7b9k2pq) - your unique link for inviting others.
• The referral code you signed up with, if any - so the friend who invited you gets credit.
• A count of people who joined via your code - so we can grant early-access tiers based on referrals.
• Timestamps for when you signed up and when your address was confirmed.
• A normalised copy of your email address - so the same address can’t join twice.
• Whether you’ve been approved for early access, and when you created your Sammy app account.
• A record of the waitlist emails we’ve sent you (such as your approval email) - so we don’t send the same one twice.

That is everything we keep about you in our database for the waitlist. We don’t store your IP address, your browser, your device, or anything else.

We process this data on two bases: your consent when you submit the form (so we can email you a welcome note and the occasional progress update), and our legitimate interest in operating a fair waitlist with a working referral mechanic. You can withdraw consent at any time by unsubscribing or by emailing us to delete your row.

We keep your waitlist entry until six months after Sammy’s public launch, then delete it. Unsubscribing stops our emails but doesn’t delete the entry; to remove it sooner, email us (see Your Privacy Rights below).

When the dedicated sign-up flow ships, it will also ask for your first name and which phone you use (iOS or Android), and that will be added to your row. This page will be updated at the same time.

Cookies and Browser Storage

We set one cookie of our own:

• locale - remembers which region’s prices to show you (Australia, US, UK, Canada, NZ, Europe). No personal data, no tracking. Lasts a year. You can clear it any time.

If you arrive through a friend’s invite link, your browser keeps their referral code in session storage (sammy_referral_code) until you close the tab, so they get credit if you join. It only leaves your device if you sign up.

We count visits with Cloudflare Web Analytics. It records the page you viewed, the site that referred you, your browser and device type, your country, and how quickly the page loaded. It sets no cookies, stores nothing on your device, and doesn’t fingerprint you, so it can’t recognise you between visits or follow you to other sites. We only ever see totals. That’s why there’s no cookie banner: there’s nothing to consent to.

We also count a few on-page actions ourselves: which parts of the page were viewed, which button you used to join, which FAQ questions were opened, whether you switched prices to yearly, and how a waitlist signup turned out (for example, joined or already on the list). Each count carries only coarse labels: the page, the site that referred you, campaign tags in the link (such as utm_source), your device type and your country. There are no cookies or identifiers. If you arrived from another site or through a tagged link, your browser keeps that site and those tags in session storage (sammy_first_touch) until you close the tab, so a signup on a later page is counted against where your visit began. It only ever leaves your device as one of those coarse labels, never with your email. Your IP address is used for a moment to stop abuse and is never stored. We only ever look at totals.

When a page is requested, we also count what kind of visitor asked for it, so we can tell people from automated traffic such as search engines, AI crawlers and link previews. We store only the page, your country, whether the page loaded, and the visitor type, worked out from the browser name your device sends (for a person, simply “browser”). We don’t store your IP address or your full browser details.

Until October 2026 this site offered optional Google Analytics cookies. We’ve removed Google Analytics, and if you accepted those cookies on an earlier visit, the site deletes them the next time you visit.

Cloudflare, the platform that hosts this site, may set bot-detection cookies (__cf_bm, cf_clearance) on its own. We don’t read or store these.

To prevent abuse of the signup form, Cloudflare also briefly checks your IP against a short rolling counter (5 signups per minute, then it resets). The counter isn’t persisted, and we don’t log the IP ourselves.

Welcome Emails and Updates

We use Resend to send transactional email. When you join the waitlist, you’ll receive one welcome email with your referral link. From time to time we may send a short update with progress on the launch. One click unsubscribes you from any email.

Resend keeps its own delivery logs (whether the email arrived, whether it was opened). Open tracking works by your email client loading a small image when the message is displayed; you can block this by turning off remote images in your email client. We use these logs to confirm sends, not to profile you.

Where Your Data Lives

Your waitlist data is held with the following processors:

• Supabase (Postgres database, hosted in Sydney, Australia) - holds the waitlist row described above.
• Resend (transactional email and mailing-list, United States) - sends the welcome email and any progress updates, and stores the audience for one-click unsubscribe.
• Cloudflare (edge hosting, rate-limiting and cookieless analytics, global) - serves this site, runs the signup endpoint, and counts page views and on-page actions in aggregate.

Keep DS and our database are in Australia, which isn’t covered by an EU adequacy decision, and some of our processors are in the United States. Where data crosses borders (for example from the EU or UK to Australia or the United States), we rely on each processor’s Standard Contractual Clauses (with the UK Addendum for UK data) or the EU-US Data Privacy Framework and its UK Extension, whichever applies, to provide an adequate level of protection. You can ask us for details.

What We Never Do

• We never sell your personal data.
• We never share your email with third parties for advertising.
• We never fingerprint you, build user profiles, or sync identifiers across sites. Our page-view analytics are cookieless and aggregate; see Cookies and Browser Storage above.
• We never use your conversations in the Sammy app to train AI models.

Your Privacy Rights

Wherever you live, you can email us at hello@sammyai.app to:

• See what we hold about you.
• Correct anything that’s wrong.
• Delete your row entirely.
• Stop receiving updates (or use the one-click unsubscribe link in any email).
• Object to how we process your data, or ask us to restrict it.

We aim to respond within 30 days, usually much sooner. The notes below explain how this maps to the specific laws that may apply where you live.

If you live in the EU, UK, or Switzerland (GDPR / UK GDPR)

You have rights under Articles 15-22 of the GDPR and the UK GDPR: access, rectification, erasure, restriction, data portability, and objection. The lawful bases for our processing are your consent (the welcome email and mailing-list updates) and our legitimate interests in operating a fair waitlist with a working referral mechanic, in protecting the signup form from abuse, and in counting visits and on-page actions with cookieless, aggregate analytics. You can object to processing based on legitimate interests at any time. You can withdraw consent at any time, without affecting what we did before. We’ll respond within one month, or tell you within that month if a complex request needs up to two more months.

You also have the right to lodge a complaint with a supervisory authority at any time: in the EU, the data protection authority where you live or work, or where you think the problem happened (the European Data Protection Board lists them at edpb.europa.eu); in the UK, the Information Commissioner’s Office (ico.org.uk).

If you live in California (CCPA / CPRA)

You have the right to know what we hold, to delete it, to correct it, and to opt out of the selling or sharing of your personal information. We will not discriminate against you for exercising any of these rights. We don’t sell or share personal information for cross-context behavioural advertising, so there is nothing to opt out of, but the right exists and we honour it.

If you live in Australia (Privacy Act 1988)

You can access or request correction of your personal information under Australian Privacy Principles 12 and 13. If you believe we’ve mishandled your data, you can raise it with us first, and then with the Office of the Australian Information Commissioner if you’re not satisfied with our response.

The Sammy App

The Sammy app has its own privacy controls and a dedicated app privacy policy. The sections below summarise how Sammy is built; the app privacy policy has the full detail.

Where Sammy Cloud Runs

The Sammy app asks for your permission before anything first goes to Sammy Cloud. Whenever it uses Sammy Cloud (on every plan, including the free plan’s limited Sammy Cloud usage), general chat runs on a decentralised AI compute marketplace called AkashML. Your conversations run across a network of independent GPU operators rather than a single tech giant’s data centre.

AkashML does not store prompts or responses, apart from short-lived error logs, and only allows limited human review, for safety. We do not log, retain, sell, or train on your conversations. Because compute runs on third-party operators, the upside is no central honeypot to leak, sell, or be hacked. The trade-off is that compute is run by independent operators rather than a single audited vendor, which is part of why on-device mode is always there as the fully private option.

If AkashML itself is unavailable, the same Qwen model answers from DeepInfra, based in the United States. DeepInfra receives the same anonymous account code AkashML does (a one-way code, not your account ID), doesn’t train on what it receives, doesn’t store it to disk and doesn’t log what your messages say.

A few features use other providers: Ask a Specialist and Word, Excel and PowerPoint files use Anthropic’s Claude, which gets as little personal detail as possible and deletes what it receives within 30 days by default, and image generation uses FLUX.2 image models from Black Forest Labs, run by DeepInfra, which receives your image request and any reference images you choose, doesn’t train on them and deletes them once the image is made. The app privacy policy lists every provider and what each one receives.

Your Data, Your Control (in the App)

The Sammy app is built so that conversations live on your device by default. In on-device mode, the model (Google’s open-source Gemma) runs entirely offline and your conversations don’t leave your phone. The free plan includes limited Sammy Cloud usage, and you can keep any chat on-device instead. When Sammy Cloud is used, conversations are sent only for the duration of the request, and neither we nor AkashML keep them, apart from AkashML’s short-lived error logs.

The app also reports, once a day, anonymous counts of finished items (such as to-dos completed), with no account or device identifier and no content, so we can see whether Sammy is genuinely helping people finish things.

The full app privacy policy details backup, export, and deletion controls.

Contact

Questions about privacy? Email us at hello@sammyai.app.