Privacy policy
Last updated
We collect as little information as we can. This policy lists all of it.
About us
Yak Shaving LLC971 S Centerville Rd, #2009
Sturgis, Michigan 49091
United States
Send questions, corrections and deletion requests to hello@yaks.app.
Information we collect
- Your email address. We use it to sign you in, to send your code, and to let other people invite you to their apps. We don't show it to other people: an app shows a name, never an address.
- Your name. When you first sign in, we ask what you'd like to be called. If you skip the question, we use the part of your address before the @. That name appears beside what you write in an app other people can see.
- A session cookie. We set this cookie for everyone. It ties anything written without signing in (guest entries) to the browser that wrote it, and keeps you signed in. Signing in puts your name on that browser's guest entries across apps. Visitor counts never use this cookie. The cookies page has the details.
- Which campaign and home page brought you. If the link you followed to yaks.app carries campaign tags or an ad's click id, we keep them, and when you arrived, in a second cookie for ninety days, with the name of the home page you last opened (such as the one for churches), so a sign-up can be counted against the campaign and the page that brought it. Our own counts of each step from the home page to signing up keep the campaign's and the page's names, never who took the step. The cookies page has the details.
- Your sign-in codes, briefly. A code lasts ten minutes and allows five guesses. We never store the digits, only a one-way hash of them, so nobody reading our records can sign in as you.
- The content of your apps. Everything you and the people you invited write (text, lists, photos and any other uploaded file), along with who wrote it and when.
- The apps themselves. The files your assistant writes to build them.
- Email your apps send and receive. An app can have its own email address, like yourspace.yourapp@yaks.app. We keep anything sent to that address in the app, including the sender's address, the message and any attachments. Anything the app sends goes out under that address.
- Your mobile number, if you give one. You can sign in or sign up with a US mobile number instead of an email address, or give one on your space's Operator page. We text it the sign-in codes you ask for and, once you've agreed, your Operator's answers and its alerts about your space and the apps you build. We keep the number, the words you agreed to, and when you agreed, and never use them for marketing. Replying STOP, or stopping texts on that page, ends texts; the number stays with your account as a way to sign in until you ask us to remove it.
- Error reports. If a page or a request fails, we record the error message, where in the code it came from, the address being visited, and which version of the app was running. We send that report to your assistant so it can fix the problem. It isn't a record of what you were doing.
- Page counts for your app. So you can see whether anyone is reading your app, we count each page it serves: 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. We keep only the counts. They contain no address, name, cookie or user agent string, so they can't identify or track a visitor. We keep them for about three months, and only the app's own members can see them.
- What you say to our builder. If you have us build an app for you instead of using your own assistant, what you type goes to a model that reads and answers it. We keep the conversation with your space so you can continue it later.
- Feedback you send us. If you ask your assistant to report a problem or send us a request or comment, your words are emailed to us at hello@yaks.app and added to the list where we track them. Your name, your email address, the space and app you were in, and the version that was running are included, so we can look into it and reply. We keep those reports.
Information we don't collect
We don't keep an advertising profile, a history of where else you've been, your location, or your contacts. We don't keep your card number either: Stripe sells and charges for the paid plan, your card goes to Stripe and never through us, and Stripe tells us only your plan and whether it's active. We don't sell anything to anyone, ever.
Where information is stored
All of it is on Cloudflare, which hosts yaks.app. Cloudflare's workers run the code, its storage holds each app's data and files, its network carries every request, its model answers you in the builder, and its containers are the sandboxes where your agent runs commands. Cloudflare handles this information on our behalf and keeps its own operational records of requests, as any host does. That network is worldwide, so your information may be stored in a different country from someone else's.
Who we share information with
Besides Cloudflare, we share information with four other companies. Stripe sells the paid plan: we give Stripe your email address so it can bill you, and Stripe tells us whether the plan is active. Telnyx carries our text messages: when we text you, Telnyx receives your number and the message so it can deliver it, and nothing else. Meta runs our ads on Facebook and Instagram. If you came to yaks.app by clicking one of them, we tell Meta, from our servers, when you open a page of this site and when you sign up: the page's address, the time, the click id Meta put on the link, and your browser's IP address and user agent, which Meta needs to match the event to its ad. We tell Meta nothing about visits its ads didn't bring, and never your name, your email address or anything in your apps.
OpenAI answers your Operator when the Operator runs on OpenAI's models. OpenAI receives the conversation and anything you ask the Operator to draw, so its model can answer, and keeps each answer for 30 days, so the next turn of the conversation sends OpenAI only what is new.
We don't share your mobile number or your agreement to receive texts with anyone else, and nobody uses them for marketing, including us.
Apart from telling Meta about the visits its own ads brought, we don't share information with advertisers, data brokers or analytics companies. Feedback you send us reaches us by email, so it passes through the email providers between you and our inbox, as any email does.
Buyers
Some yaks apps sell things. When one does, the seller is the merchant, not us (see the terms). Your card details go to Stripe on Stripe's own page and never touch this platform or the app. Neither we nor the seller ever see your card number.
We do see the order, and it goes to two places. The seller receives what you bought, what it cost, and the email address you gave at checkout, stored in the seller's app so the seller can send you what you bought. Stripe takes the payment and holds the record of it under the seller's account. We keep our copy of the order for as long as the seller keeps the app. Deleting the app deletes it, and the seller can delete a single order.
We use your email address only for the receipt the app sends you. We don't add you to a list, and we never sell your address.
Sellers
When you connect a Stripe account, we send Stripe your email address and the name of your space. Stripe then asks you directly for your business details, your identity documents and your bank account. Those never come to us. Stripe tells us three things, and we keep only those: the account's id, whether Stripe says you may take payments, and whether you finished Stripe's form.
We send sign-in codes and invitations through Cloudflare Email Sending. Those are the only emails we send you without your asking, and each one results from something you or another person did.
Email from your apps and feedback you send us go through the same service.
Analytics
No advertising or analytics code runs on our pages. We count the steps people take from the home page to signing up, with the site and campaign that sent them but not who took them, and Cloudflare gives us the ordinary request counts any host sees. What Meta is told about visits its ads brought is above.
Who can see your content
You set this for each app. Private means you and the members you invited. Public means anyone with the link can read it. Open means anyone with the link can also write in it. Anyone 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. We look at the content of your apps only when you ask us for help, or when we have to in order to keep the service running or to comply with the law.
Data retention
We keep your information for as long as you have an account.
When you delete an app, it goes to the trash. It stops responding at its address immediately, and we keep its data and files for 30 days so you can restore it. After 30 days we erase its data, its files and everything else belonging to it, and this can't be undone. If you ask us to erase it immediately instead, we erase it right away and keep nothing.
You can close a space by asking your assistant to delete it and confirming the link we email you, or by deleting it yourself while signed in. The same 30 days apply to the whole space. It stops responding at all of its addresses immediately, and we keep its apps, their saved data and files, and your conversation with our builder for 30 days so you can restore it. We also hold the space's address for you during those 30 days. After that, we erase everything and the address becomes available to others. If you ask for the space to be erased immediately instead, your assistant emails you a link for that too, and we erase it right away.
If you ask us to close your account, we remove everything else, including our record of you. Backups and server records expire on their own in the following weeks.