Privacy policy

Who holds it

Questions, corrections, or a request to delete something all go to hello@yaks.app.

What we keep

• Your email address. It's how you sign in, how we send your code, and how a friend invites you to their app. We don't show it to other people — an app shows a name, never an address.
• The name you chose. When you first sign in we ask what you'd like to be called. Skip the question and we use the front of your address. That name is what appears beside things you write in an app other people can see.
• A session cookie. One, so you stay signed in. The cookies page has the details.
• Your sign-in codes, briefly. A code lasts ten minutes and five guesses. We never store the digits themselves, only a one-way scramble of them, so nobody reading our records can sign in as you.
• What's in your apps. Everything you and the people you invited write — text, lists, photos and any other file uploaded — along with who wrote it and when.
• The apps themselves. The files your assistant writes to build them.
• Letters your apps send and receive. An app can have an address of its own, like yourspace.yourapp@yaks.app. Anything written to it is kept in that app — the sender's address, what they wrote, and whatever they attached — and anything the app sends goes out under that address.
• Reports when something breaks. If a page or a request fails, we record what happened: the message, where in the code it came from, the address being visited, and which version of the app was running. That report goes to your assistant so it can fix the thing. It isn't a record of what you were up to.
• A count of the pages your app served. So you can see whether anyone is reading it, we tally each page an app answered — which page, which country the request came from, which site linked to it, and whether the visitor was a person's browser, a search crawler or an AI assistant. Counts only: no address, no name, no cookie, and not the browser's own identifying string, so there is nothing here to pick one visitor out of and nothing to follow anyone with. We keep those tallies about three months, and only the app's own people can see them.
• What you say to our builder. If you have us build an app for you rather than bringing your own assistant, what you type goes to a model to be read and answered, and we keep the conversation with your space so you can pick it back up.
• Feedback you send us. Ask your assistant to report a problem — or pass on a wish, a rough edge or a kind word — and your words are mailed to the people who run this place, at hello@yaks.app and the work list where we track them. Your name, your email address, the space and the app you were in, and the version that was running ride along, so we can look into it and write back. We keep those reports.

What we don't keep

No advertising profile, no history of where else you've been, no location, and no contact list. No card number either: the paid plan is sold and charged by Stripe, your card goes to them and never through us, and what comes back to us is your plan and whether it's on. We don't sell anything to anyone, ever.

Where it lives

All of it sits on Cloudflare, who host this whole platform: their workers run the code, their storage holds each app's data and files, their network carries every request, their model is the one that answers you in the builder, and their sandbox is where a build compiles anything a browser can't. They handle it on our behalf and keep their own operational records of requests, the way any host does. That network is worldwide, so the nearest copy to you may sit in a different country than the nearest copy to somebody else.

Who else touches it

Two other companies, and that's the end of the list. Stripe sells the paid plan: we hand them your email address so they can bill you, and they hand back whether the plan is on. Google serves the typeface these pages are set in, so your browser asks them for a font file and they see that request the way any web server would.

Nobody else — no advertiser, no data broker, no analytics company of our choosing. And when you send us feedback, it reaches us by mail, which means it passes through whichever mail providers stand between here and our inbox, the way every letter does.

If you buy something here

Some apps here sell things, and when one does the seller is the merchant — not us (terms). Your card details go to Stripe on Stripe's own page and never touch this platform or the app; we never see a card number, and neither does the seller.

What we do see is the order, and it goes two places. To the seller: what you bought, what it cost, and the email address you gave at checkout, written into their app's own store, where they read it to send you your things. And to Stripe, who take the payment and hold the record of it under the seller's account. We keep our copy of the order for as long as the seller keeps their app; deleting the app deletes it, and the seller can delete a single order like any other row.

We use your address for the receipt the app sends you and for nothing else. We do not add you to a list, and we never sell it.

If you sell something here

Connecting a Stripe account sends Stripe your email address and the name of your space, and Stripe then asks you directly for your business details, your identity documents and your bank account. Those never come to us. We are told three things back and hold only those: the account's id, whether Stripe says you may take payments, and whether you finished their form.

Email

Sign-in codes and invitations go out through Cloudflare Email Sending. Those are the only letters we send you unasked, and each one is something you or a friend set in motion.

Your apps' own letters travel the same road, and so does the feedback you send us — that one goes to us rather than to you.

Counting visits

We run no analytics of our own and no advertising trackers. Cloudflare gives us the ordinary request counts any host sees.

One honest note: Cloudflare currently attaches its own Web Analytics script to pages served from here. It counts page views, sets no cookie, and doesn't follow you elsewhere. We didn't add it, and we're switching it off.

Who can see your things

That's yours to set, one app at a time. Private means you and the members you invited. Public means anyone who has the link can read it. Open means anyone who has the link can write in it as well. Whoever you invite can see what's in that app.

Your assistant sees the apps you connected it to, and acts as you when it does. On our side, we look at what's in your apps only when you ask us for help with something, or when we have to in order to keep the place running or to answer the law.

How long we keep it

For as long as you have an account here. Delete an app and it goes to the trash: it stops answering at its address straight away, and its data and files are kept for 30 days so you can restore it if you deleted it by mistake. After 30 days we erase it — its data, its files, everything — and that is final. Ask for it gone at once instead and we erase it then and there, with nothing kept. Close a space — ask your assistant to delete it and confirm the link we email you, or do it yourself while signed in — and the same 30 days apply to the whole of it: it stops answering at every address it has straight away, and its apps, everything they saved, their files and the conversation you had with our builder are all kept for 30 days so you can restore it. Its address is held for you for those 30 days too. After them we erase all of it and the address goes back into circulation. Ask for the space gone at once instead — your assistant emails you that link too — and we erase it then and there. Ask us to close your account and we remove the rest, the record of you included; ordinary backups and server records age out on their own in the weeks after.

What you can ask for

Write to hello@yaks.app and ask for a copy of what we hold, a correction, or deletion, and we'll do it. Depending on where you live the law may give you those rights formally — in the UK and the EU, in California, and elsewhere. We'd rather just do it than argue about which rule applies.

Children

This isn't built for children, and it isn't for anyone under 13. If a child's information has ended up here, tell us and we'll remove it.

Changes

If this policy changes, the page and the date at the top change with it, and we'll email you when the change is one that matters.