Privacy Policy
Last updated: October 20, 2026
wrka is operated by Kasino Inc., based in California, United States. You can reach us at support@wrka.ai.
The short version
wrka is a business tool for independent operators: barbers, producers, photographers, food trucks and anyone else running a business on their own. You use wrka to keep track of your own customers and leads. That means two kinds of people appear in this policy:
- You, the operator. You created a wrka account. This policy says what we collect about you.
- Your contacts. People you add to wrka, who message you, or who book you. They never signed up for wrka. Most of what wrka stores is about them, and you decided to put it there.
We do not sell anyone's data. We do not run ads. We do not track you across other apps or websites.
1. Information you give us about yourself
- Account details: your name, email address and password. Passwords are handled by our sign-in provider and we never see them in readable form.
- Your business profile: your trade, city, how long you have been in business, and your answers to our setup questions. Those answers include financial information about your business: recent revenue, average sale price, monthly and yearly income, and your largest sale.
- Your goals: what you want to fix, what is getting in your way, and how you feel about your business right now. Answering is up to you.
- Your Stripe connection: if you set up Stripe, the ID of your Stripe account and whether it can take payments. Your bank and identity details go to Stripe directly, never to wrka.
- Your Square connection: if you connect Square, your Square merchant ID and the ID of its main location, your business name as Square has it, whether it can take card payments, whether you picked it for card payments, and the OAuth access tokens Square gives wrka to take payments on your account, stored encrypted. Your bank and identity details go to Square directly, never to wrka.
- Your wrka plan: if you subscribe to wrka, your Stripe customer ID and your plan's status and dates (trial end, renewal, cancellation, a failed payment). Your card goes to Stripe directly, never to wrka.
- Your writing style: sample messages and phrases you use or avoid, so wrka can draft messages that sound like you.
- Your services and availability: what you offer, your prices and your working hours. Your booking page shows your services, your hours and any social links or website you add to it, to anyone who opens it.
- Your payment handles: the Zelle, Venmo, Cash App or PayPal details you choose to add. They are shown on the invoices you send, to anyone who has an unpaid invoice link.
2. Information about your contacts and customers
This is most of what wrka holds. It is here because you put it here, or because it arrived through an account you connected.
- Contact details: names, nicknames, email addresses, phone numbers, businesses and the city or area you record.
- Social handles and links: Instagram, TikTok, X, YouTube, Facebook, Yelp and websites.
- Messages: the full text of messages exchanged through accounts you connect, with subject lines and times.
- Messages from people you have not added yet: when someone new messages an account you connected, wrka holds the message in a pending list until you add or block them, and keeps a list of the senders you blocked. When the message comes from Instagram, wrka looks up the sender's Instagram handle so you can see who it is, and remembers the answer.
- Your notes: anything you write about a contact, plus deal stage, deal value and follow-up reminders.
- To-dos: the to-dos you write, their due dates, whether you starred them, the contact they are for and when you ticked them off.
- Quotes and invoices: the lines, prices, deposit and note on quotes and invoices you send, the name a client types when they accept a quote, and when and how an invoice was paid.
- Photos in Live chat: a photo you or your client sends in a Live chat is stored so you both can see it in the conversation. The device resizes it and saves it again as a JPEG before it is sent, which removes camera details such as location. Photos are kept in private storage, never at a public link, and are shown only through links that expire after 30 minutes.
- Your logo: if you upload a logo, we store it so it can appear on your booking, Live chat and contact pages, in link previews and on Home Screen shortcuts your clients save. Logos are public by design: anyone with the link can see them, and apps like Messages fetch them without signing in. The logo's web address does not contain your account ID. Your device crops and resizes the image before upload, which removes photo details such as location. Removing your logo, or deleting your account, deletes the stored file.
- Booking details: when someone books you through your wrka booking page, we collect the name, phone number, email address and any note they leave, the options and add-ons they pick, and the time zone their browser is set to, so emails can show a remote meeting's time on their clock.
- Payment records: amounts, payment method and dates for work you log or invoices you mark paid. When a client pays an invoice online, Stripe or Square (whichever you use) takes the payment in its own secure form and wrka records that it was paid; wrka never receives card or bank numbers.
- AI-generated notes about contacts: summaries, suggested next steps and read-outs of tone, generated from the above.
Your responsibility as the operator
You are responsible for having a lawful basis to store your contacts' information in wrka and for telling them how you handle it where the law requires. If a contact asks you to remove their information, you can delete it in the app. If they contact us directly, we will refer them to you and help you act on it.
3. Information collected automatically
- Error data: when something breaks, our error monitoring records what went wrong, the page it happened on, and basic details about the browser or device, and may record an IP address. We switch off its collection of personal details and strip cookies, sign-in tokens and IP headers before anything is sent.
- Abuse protection on public pages: to stop automated spam on booking, lead, quote and invoice pages, we count requests by IP address and email address. Those records are deleted automatically after two days.
- Notifications: if you turn on notifications, your device gives us a delivery address for it. A message notification carries the sender's name and a short preview of the message; the morning to-do notification carries the titles of the to-dos due that day. Each one is encrypted before it leaves our servers and travels through your device maker's push service (Apple, Google or Mozilla), which cannot read it.
Our public pages (the wrka.ai homepage, sign-up, privacy and support pages) use Google Analytics to count visits and see which pages and links bring people to wrka. On those pages only, it sets first-party cookies and records the page you viewed (without any personal details from the web address), the site that sent you, your device and browser type, and an approximate location Google works out from your IP address. Google Analytics does not run inside the wrka app, on any booking, lead, quote or chat page, or in the wrka iOS app. We have Google's advertising features and Google signals turned off, and we honour the Global Privacy Control signal: if your browser sends it, analytics never loads. You can also opt out with Google's browser add-on at tools.google.com/dlpage/gaoptout.
Our fonts are served from our own site, not from a third party.
4. What wrka does not collect
- No location from your device. Cities and areas in wrka are typed in by hand.
- No access to your device's contacts, camera or microphone.
- Contact imports are your pick. If you import contacts from a file you choose (a CSV or a contacts file), it is read in your browser and only the contacts you select are saved to your account.
- No photo library access. You can pick an image to upload with your device's standard file picker, but wrka cannot browse your photos.
- No advertising identifiers, no cross-app or cross-site tracking, no third-party cookies.
- No full card numbers or bank details. For a card saved at booking, wrka keeps only its brand and last four digits (section 6).
- No imported screenshots kept. A screenshot you upload to import a conversation is read and discarded. Only the text taken from it is saved. Photos sent in a Live chat and your logo are the only files wrka keeps (section 2).
5. AI features
wrka uses AI to draft messages, summarise conversations and analyse your business. To do that, we send information to Anthropic, the company that makes Claude. What we send can include:
- The text of your recent messages with a contact, up to the last twelve, word for word.
- That contact's details: name, business, city, email address, phone number, Instagram handle, website, deal stage, deal value and your notes about them.
- Your business profile and writing samples, so the draft sounds like you.
- Images you choose to upload, such as a screenshot of a conversation.
- Your business details, your services and prices, and how many contacts you have, when you use the business analysis features. If you saved business answers earlier, including financial figures, those are sent too.
Anthropic processes this to generate a response and handles it under its terms as our service provider. It does not use it to train its models.
AI features run only when you use them. wrka does not send your data to Anthropic in the background.
6. Who else receives information
Each service gets only what it needs to do its job. We never sell personal information and never share it for advertising.
Supabase
For: Database, sign-in, private storage for Live chat photos, and public storage for your logo
Receives: Everything in sections 1 and 2
Vercel
For: Hosting
Receives: Web requests and IP addresses
Anthropic
For: AI features
Receives: See section 5
Unipile
For: Connecting your email and Instagram
Receives: Messages sent and received, recipient addresses, and Instagram sender lookups. Unipile holds your mailbox and Instagram sign-in; wrka never stores it.
Stripe
For: Online invoice payments, if you set up Stripe, and billing for your wrka plan
Receives: Your email address and business name when you set up, then each invoice's number, amount and your name when a client pays. Clients enter their payment details into Stripe's secure form, on the invoice page or on Stripe's own page; wrka never receives them. On invoice pages Stripe's form may collect device and browser information to prevent fraud. If you subscribe to wrka, your name and email address; you enter your card on Stripe's page, and Stripe bills it.
Square
For: Online card payments, if you connect Square and pick it for them: invoice payments, cards saved at booking, and subscriptions you sell to clients
Receives: Each invoice's number and amount and your name when a client pays, and the email address a client types for it. Clients enter their card details into Square's secure card form (Square's Web Payments SDK), on the invoice, booking or subscription page, or on Square's own page; wrka never receives or sees card numbers. When a client saves a card at booking or subscribes, their name and email address, so Square can keep the card on file in your Square account, and for a subscription its number, price and how often it charges. Square processes those card payments, stores the saved cards and runs those subscriptions in your Square account; wrka stores Square's IDs for them, and for a card saved at booking its brand and last four digits (for example, Visa ending 1111) so you can see which card is on file. Square's privacy notice covers what Square does with it.
Resend
For: Booking emails, Live chat emails, and account emails (confirming your sign-up, resetting your password, and telling you that you already have a wrka account)
Receives: Your customer's name, email address and booking details. The new-booking email we send you also carries your customer's phone number. For Live chat, your client's name and email address, your name, the chat link and, in a reply notice, the first line of your reply. For account emails, your email address.
Twilio
For: Reminder texts the day before a booking, only if you turn text reminders on and your wrka plan includes them. Texts come from wrka's own number, not yours.
Receives: For each reminder, your client's mobile number and the text itself: the service, your business name, when the booking is, a link to your booking page and, if you use Live chat, your client's Live chat link. A reminder goes only to a client who ticked "Text me a reminder the day before" when they booked on your booking page. Replies to wrka's number come back through Twilio (section 7).
Apple, Google, Mozilla push services
For: Delivering notifications you turned on
Receives: An encrypted notification they cannot read
Google Analytics (Google LLC)
For: Counting visits to our public pages: the homepage, sign-up, privacy and support pages
Receives: See section 3
Sentry
For: Error monitoring
Receives: See section 3
Slack
For: Our internal alerts
Receives: Error alerts, and your email address when you sign up
We may also disclose information if the law requires it, or to protect our rights, our users or the public.
7. Text messages
The only texts wrka sends are appointment reminders the day before a booking. A reminder goes to a client only when the business has text reminders turned on and the client ticked "Text me a reminder the day before" when they booked on its wrka booking page. Ticking it is optional, and booking works the same without it. Texts come from wrka's own number, one per booking, and never carry marketing.
- What a reminder says: what you booked, with whom and when, a link to the business's booking page, and, if the business uses Live chat, your link to chat with them.
- To stop: reply STOP to any reminder. You get one text confirming it and no more texts from wrka's number, for any business. Reply START to get them again.
- For help: reply HELP, or contact us (section 14).
- Cost: Message and data rates may apply.
- What wrka keeps: the time you ticked the box, on your booking. If you reply STOP, your number goes on wrka's do-not-text list so no reminder is sent to it again, even if a business later deletes its account; replying START takes it off. Twilio passes your replies to wrka, which reads them only for STOP and START and does not store them or forward them to the business.
We do not share or sell mobile phone numbers or text message opt-in data and consent with third parties or affiliates for marketing or promotional purposes. For reminder texts, the only outside service that receives your mobile number to send them is Twilio.
8. How long we keep information
We keep your information for as long as your account is open.
When you delete your account in Settings, we delete your data from our database immediately: your account, contacts, messages, bookings, payments, business profile and everything else, including the photos sent in your Live chats. This is permanent. Photos are deleted when you delete your account. While your account is open, a photo is usually removed within a day of its message being deleted (deleting a contact deletes its messages), and a photo that was uploaded but never sent is usually removed within two days.
A few things can outlast that, and we would rather say so:
- Connected email or Instagram accounts at Unipile. We ask Unipile to remove them. If that request fails we do not hold up your deletion; email us and we will remove them by hand.
- Your wrka plan. Deleting your account cancels it straight away, so you are never billed again. Stripe keeps its own record of your past payments.
- Your Stripe account. It belongs to you, not to wrka, so it stays open with its payment history. Close it from your Stripe Dashboard if you want it gone.
- Your Square account. It belongs to you, not to wrka. We ask Square to end wrka's access to it; if that request fails we do not hold up your deletion, and you can remove wrka in your Square Dashboard. The account stays open with its payment history and saved cards, and any client subscriptions running there keep billing until you cancel them in your Square Dashboard.
- The do-not-text list. A number that replied STOP to a reminder stays on it (section 7), so it is never texted again.
- Error reports already recorded by Sentry, kept for its retention period.
- Internal alerts already delivered to our Slack.
- AI request records held by Anthropic under its retention terms.
9. Your rights
You can view and edit almost everything in the app, and delete your account at any time from Settings.
Depending on where you live, you may also have the right to request a copy of your information, ask us to correct or delete it, or object to how we use it. If you live in California, the CCPA gives you rights including access, deletion and correction, and the right not to be treated differently for using them. We do not sell or share personal information as the CCPA defines those terms.
To make a request, email support@wrka.ai. We will confirm it is you before we act.
10. Security
Your data is protected by row-level security, so one operator's records cannot be read by another. Sign-in is handled by our sign-in provider, and connections to wrka are encrypted. No system is perfectly secure. If a breach affects your information, we will tell you as the law requires.
11. Children
wrka is a business tool and is not directed at children. We do not knowingly collect information from anyone under 13. If we learn that we have, we will delete it.
12. Where wrka operates
wrka is offered to businesses in the United States, and your information is stored there. If you use wrka from outside the US, your information is sent to the US, where privacy laws may differ from your own.
13. Changes
If we change this policy we will update the date at the top. Significant changes will be announced in the app.
14. Contact
Kasino Inc., California, United States. Email support@wrka.ai or call (559) 813-5313.