Privacy Policy

Who we are

“Rook”, “we” and “us” mean the people who run Rook, the AI you text at +1 (628) 998-8199 and use at heyrook.xyz. This policy covers the Rook text service, the website and your account page. It doesn’t cover the stores, apps and websites Rook works with for you; they have their own policies.

What we collect

Only what Rook needs to work for you:

Your phone number. It’s how you sign up, sign in (Rook texts you a 6-digit code) and talk to Rook.
Your messages. What you text Rook and what it texts back, including photos, screenshots, voice notes, files, links and contact cards you send. Voice notes and video are turned into text so Rook can read them.
What Rook remembers. Facts you tell it or that come up in your chats (your name, your timezone, people and plans you mention), the decisions you make and the reasons you give, the people you mention with their role and any email or number you give for them, what you’re waiting on or promised, what you’re building, a running summary of your conversation, and your preferences, like how often Rook may text you first, the people or companies whose emails you asked it to tell you about, and whether you’ve told it to be quiet for now. Rook never keeps passwords, codes, card or account numbers in its memory.
Connections with other people’s Rooks, if you make one: who you’re connected with, what each of you lets the other ask, the questions and messages you approve sending, the answers that come back, and a log of each step. The other person’s Rook only ever gets the words you approved; it never sees your memory, email, calendar, money or conversations.
Reminders, habits and watches you set up, like a morning brief or a price you want watched.
Your location, only if you share it, to help with things nearby. Rook keeps your latest shared location.
Data from apps you connect. When you connect Gmail, Google Calendar, Notion, Slack, Stripe, GitHub or any other app, Rook reads from it and acts in it when a request needs it: for example reading new email so it can tell you what needs you, finding receipts to spot subscriptions, checking your calendar for free time, or reading a Notion page. Rook keeps what it needs to do the job (for example a found subscription’s merchant, amount and dates, or the summary it texted you), not a copy of your inbox or workspace.
Purchase details. When you ask Rook to buy something: the item, store, price, total, order number, receipt and status, plus the screenshots of the store page Rook sends you. For guest checkouts, your name, email, phone number and shipping address, which Rook saves so it doesn’t have to ask again.
Bank data, if you connect a bank. You pick your bank and sign in on Stripe’s own secure sheet (Stripe Financial Connections); Rook never sees your bank login. Rook gets read-only access to balances and transactions, and keeps only Stripe’s reference IDs for your accounts, the bank’s name, the last four digits and whether the link is active. Balances and transactions are read from Stripe when a request needs them and are not stored.
Shop Pay checkouts. Where Rook offers Shop Pay checkout: the stores and items it found for you, the checkout it opened with that store (kept encrypted, for a few hours), and the order’s store, item, total and order number. If you connect your Shop account, Rook keeps an encrypted sign-in token for it (never your password or card number) so it can use your saved addresses and Shop Pay after your yes and show your order status.
Card details, without the card. You add your card on our payment partner AgentCard’s own secure page. Rook only keeps the card’s brand and last four digits so it can say which card it used.
Billing. Your plan, billing period, payment status and the subscription record from our checkout provider. Rook doesn’t see or store your card number for subscriptions either.
Your users’ check-ins, if you ask Rook to talk to your users: the signup email addresses and names you send Rook (or that come from your connected Stripe customers or your signup webhook), when each one was emailed, who asked not to be emailed again, and the replies they send back. Rook emails each signup once, from rook@heyrook.xyz, only after you approve the exact email, and stops for anyone who replies “stop”. You confirm you have the right to contact the people you add.
Events from your tools, if you point them at Rook (Stripe, Railway, GitHub, CI or Claude Code): the event type and the few details Rook needs to text you about it (for example the amount and customer email of a failed payment, or the service and commit message of a crashed deploy), kept as a short recent list. If you link Railway so Rook can roll back a deploy, your Railway token is stored encrypted and used only for a rollback you approve.
Bookings, if you use them (restaurants, hotels, flights, appointments and the like): the place, dates and times, party size, the price and terms you approved, and any confirmation.
Technical data. Basic logs of requests and errors, a sign-in cookie for the account page, a cookie that remembers your answer on a plan link, and your light or dark theme choice stored in your browser. Logs are scrubbed of keys, passwords, codes and card numbers. We don’t use advertising or analytics trackers.

How we use it

To do what you ask: answer, look things up, remember, remind, draft, make images, schedule, buy, book and keep watch.
Now and then, to tell you about something new Rook can do. Text Rook “no more updates” and it stops; it never affects replies, reminders or alerts.
To text you first about things you set up or that clearly need you (a reply you owe, a meeting moving, a payment failing). By default Rook sends at most 4 of these a day and stays quiet from 10pm to 8am your time, except for urgent alerts. You can change both by texting Rook.
To run your plan, take payments and stop abuse, like spam or attempts to get around limits.
To keep Rook working and fix problems. The person who runs Rook may look at a specific conversation only to fix a problem you reported, to investigate abuse or security issues, or when the law requires it.

Rook asks before it does anything that sends, spends or can’t be undone. It shows you the email before it sends it, and the total before it pays.

What we never do

We don’t sell or rent your personal data.
We don’t use your data for advertising, and we don’t share it with advertisers or data brokers.
Rook doesn’t train AI models on your messages, memory or connected-app data. Our AI provider, Anthropic, doesn’t train its models on data sent through its commercial API either.
Rook never asks for your store or app passwords. You sign in on the app or store itself.

Google data (Gmail and Calendar)

If you connect Gmail or Google Calendar, Rook can read, search and summarize your email, write drafts, and send an email or reply only after you say yes to the exact text. On Calendar it can read your events and free time, and add, move or remove events, again after your yes.

While Gmail is connected, Rook checks each inbox you connected for new mail every few minutes. If you asked it to watch for someone (“tell me when Nolan emails”), it texts you when their email arrives. It also texts you about a new email that clearly needs you soon, like a security alert, a failed payment, a plan expiring or a deadline today, a few times a day at most and never for newsletters or promotions. For this it keeps only the email’s ID (so it never texts twice about the same one) and the short text it sent you. Text “stfu” or “be quiet” and it stops texting you first until you text again.

Packages. When you ask Rook where your orders are, it reads the shipping and delivery emails in your connected Gmail (the last few weeks) and keeps a short list of the orders it found: the store, a few words naming the item, the carrier, tracking and order numbers, the status and the expected delivery date, and which updates it already texted you about. From then on it checks every couple of hours and texts you when an order is out for delivery, delivered or delayed, at most three times a day and never in your quiet hours. Text “stop the package texts” and it stops. The list keeps at most 40 orders and is deleted with the rest of your data.

Photos you send. When you text a photo of a flyer, ticket, appointment, bill or receipt, Rook reads the text in it to offer one thing it can do (like a reminder or a calendar event) and keeps only what it sets up after your yes.

Rook’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain terms:

Google data is used only to provide the features you use in Rook.
It is shared with others only to provide those features (for example, the AI provider that writes Rook’s replies), to comply with the law, or as part of a merger or sale with the same protections.
It is never used for advertising, never sold, and never used to train or improve general AI or machine-learning models.
No person reads it unless you agree to it for a specific message, it’s needed for security or to investigate abuse, or the law requires it.

You can disconnect Google any time from your account page or by texting Rook, and you can also remove Rook’s access in your Google Account settings.

Rook's own email address

You can claim an address for Rook, like yourname.mail@heyrook.xyz, so Rook can sign up for things and receive codes, confirmations and receipts without using your own inbox. Mail sent to that address is received through Cloudflare and kept in your Rook account for 30 days, then deleted: who sent it, the subject, the text (up to 20,000 characters), any one-time codes or confirmation links in it, and whether it passed sender authentication (a DKIM signature from the sender's own domain). Attachments are not kept. Rook only uses codes and links on its own from mail that passed that check; other mail is kept but flagged as unverified. Rook reads it to finish what you asked (for example entering a sign-up code) and may text you about it. It never pays for, approves or replies to anything because an email asks it to. When you ask, Rook can send an email from this address to one person you name, only after showing you the exact text and getting your yes; the recipient’s address, the subject and the text go to our email provider (Resend) to deliver it, and replies come back to this address. When a store asks for an account to check out, Rook may create one at that store under your Rook address, with a long random password that is stored encrypted and never shown to anyone, including Rook’s model. Store codes sent to that address are entered by Rook for you. You can choose whether store receipts go to your Rook address or to your own email. You can have one address at a time and change it once every 30 days. An address you give up is never given to anyone else: mail sent to it still reaches you, so stores you used it with keep working. Deleting your data deletes this mail and these store logins, and retires the address permanently: mail to it is refused and nobody can claim it.

Health tracking and plans with friends

Health. If you ask Rook to track something (sleep, meals, workouts, water, weight, mood, meds, symptoms, caffeine), it keeps what you tell it: the kind, the number or a short note, and when. It uses that only to answer you (“how have I been sleeping?”). Rook only logs what you ask it to track, it isn’t medical advice, and it’s never shared or sold. Say “stop tracking” any time, and deleting your data deletes it.

Plans with friends. When you ask Rook to organize something, it makes a link you share. Friends who open it see the plan’s title, the times and places, and how many people answered. They enter a first name and tap what works. A small cookie in their browser ties the answer to that browser, so they can change it later and nobody else can change it by typing their name. Rook keeps those answers with the plan to tell you the best time and place. Rook never texts your friends, and plans expire after 14 days.

Rook in group chats, and feedback

Group chats. When you add Rook to a group, that group gets its own Rook. It keeps the group’s messages (with who sent each one) so it can follow the conversation, and it only replies when someone says “rook” or replies to it. A group’s Rook has no access to anyone’s personal email, calendar, card, bank or memory, and it never shares anything from your one-on-one chats. If someone in a group asks Rook to buy something, the exact total goes to that person in their own one-on-one chat with Rook, and only their typed yes there completes it.

Feedback. If you ask Rook to pass feedback to the team, it sends your words (with any card or Social Security number masked), your first name, the last four digits of your number and your plan to the team’s Rook inbox, and nothing else. Ask to stay anonymous and only your words and plan go.

Rook relies on these companies. Each gets only what its part of the job needs:

Anthropic · the AI models that read your messages and write Rook’s replies.
Photon · delivers texts between you and Rook over iMessage (Apple carries the messages themselves).
Supabase · our database, where your account, messages and memory are stored.
Railway · hosts Rook’s servers and their logs.
Cloudflare · receives mail sent to your Rook address (yourname@heyrook.xyz) and passes it to Rook.
Supermemory · stores Rook’s long-term memory about you.
Composio and Pipedream · connect your apps (Gmail, Calendar, Notion, Slack, Stripe and others) and hold the sign-in tokens, so Rook never sees your passwords.
Browserless, Steel and Browserbase · run the web browser Rook uses to look at stores and check out for you.
AgentCard · holds your card and handles purchase payments.
Shop (Shopify) · where Rook offers Shop Pay checkout, searches stores that check out with Shop Pay and opens a checkout with the store you buy from (with the item and your shipping address). If you connect your Shop account, it supplies your saved addresses and Shop Pay for payment after your yes, and your order status. Shop handles your sign-in and payment details under its own privacy policy.
Stripe (Financial Connections) · if you connect a bank, links it and shares read-only balances and transactions with Rook. Stripe handles your bank sign-in under its own privacy policy.
HandyPay, with Stripe as its processor · run checkout and billing for Rook plans.
ElevenLabs · turns voice notes into text.
Google (Gemini API) · makes and edits images you ask Rook for. It gets the description Rook writes for the image and, for an edit, the photo you asked Rook to change. Google doesn’t use them to train its models on the paid Gemini API Rook uses.
Resend · sends the check-in emails to your users, if you turn that on, and emails you ask Rook to send from your Rook address.
Map, weather and search services (like OpenStreetMap, Open-Meteo and web search) · get the address, weather or search terms needed to answer you, not who you are.

When you ask Rook to buy, book or contact someone, it shares what that job needs with that store, restaurant, hotel, airline, business or person (for example your name, email, phone and shipping address for a guest checkout). When Rook schedules with another Rook user, it only shares times that work, never your calendar.

We may also share data if the law requires it, to protect people from harm, or as part of a merger or sale of Rook, in which case this policy keeps applying to your data.

Payments and your card

You add your card on AgentCard’s hosted page, with Face ID or a passkey. Rook never receives or stores your card number. When you approve a purchase, AgentCard either asks you to confirm that exact payment on your phone, or issues a single-use card for the approved amount that goes straight into the store’s checkout. That number is never stored, logged or shown to the AI.

Plan subscriptions are paid on HandyPay’s checkout page, processed by Stripe. Rook stores only your plan, period and payment status.

For Shop Pay checkouts, Rook shows you the store, item and all-in total first. If your Shop account is connected, the order is paid with the Shop Pay method you confirm, only after your texted yes; otherwise Rook sends you the store’s own Shop Pay checkout link and you pay there yourself. Rook never receives your card number either way.

Your bank, if you connect it

Connecting a bank is optional. When you do, Stripe Financial Connections links it: you choose the bank and accounts and sign in on Stripe’s sheet, and your bank login goes to Stripe and your bank, never to Rook.

What Rook can see: balances and transactions, read-only. Rook can’t move money, make payments or see your full account or routing numbers through this connection.
What Rook keeps: Stripe’s IDs for your accounts, the bank’s name, the last four digits and the link status, plus your notice settings. It does not store your balances or transactions; it reads them from Stripe when you ask or when a notice you turned on runs. A subscription Rook finds is saved the same way as one found in your email (merchant, amount, dates).
What Rook uses it for: finding subscriptions and what you spend on, and, only if you turn them on, a text when your balance gets low or a bill is about to renew. Both notices are off unless you ask.
Disconnecting: text Rook “disconnect my bank” and it tells Stripe to disconnect the accounts right away. Deleting your data disconnects the bank too.

How long we keep it

We keep your data while you use Rook, so it can remember and pick up where you left off. Sign-in codes expire after 10 minutes and sign-in links within 30. Server logs are kept for a limited time by our hosting provider. Copies in our providers’ routine backups age out on their own schedules.

If you stop using Rook, your data stays until you delete it. You can delete it any time, as below.

Deleting your data

Two ways, same result:

Text Rook “delete my data”. It asks you to confirm with a yes first.
On your account page, tap Delete my data and type “delete” to confirm.

What’s deleted: your chats and their summary, everything Rook remembers (including long-term memory), connected apps (Rook also revokes its access with each app), a connected bank (disconnected at Stripe), a connected Shop account (Rook revokes its access), reminders, habits and watches, your location, found subscriptions, connections with other people’s Rooks and the questions and answers between them, errands, bookings, calls, queued work, links, the raw message events we received, and your name, email, shipping address, saved card details and preferences.

What’s kept, and why:

Your phone number, so STOP and START keep working and Rook knows you if you text again.
Your plan and billing records, so an active subscription keeps working and can be cancelled, and for tax and accounting.
Purchase receipts, for refunds, returns and disputes.
Usage counts and cost numbers, which hold no message content.
Whether you already used the launch offer.

Deleting can’t be undone. If you also want your number and billing history removed where the law allows, ask us (see Contact).

Your choices and rights

Pause texts: text STOP and Rook goes quiet. START turns it back on.
Text less: tell Rook to text you first less often, set quiet hours, or stop texting first.
Forget something: text Rook “forget …” and it removes that memory.
Disconnect an app: from your account page or by text.
See, correct or get a copy of your data: ask us, and we’ll answer within 30 days.

Depending on where you live (for example Jamaica, the EU, the UK or California), you may have rights to access, correct, delete or move your data, and to object to some uses. You can use them the same way. You can also complain to your local data protection authority, such as Jamaica’s Office of the Information Commissioner.

Security

Data travels over encrypted connections (HTTPS). App sign-ins are held by our connection providers, not by Rook. Card numbers never reach Rook’s database, logs or AI. Logs are scrubbed of keys, codes and card numbers. Access to production systems is limited and protected. Sign-in uses one-time codes, never passwords.

No system is perfectly secure. If we learn of a breach that affects your data, we’ll tell you without undue delay, by text.

Children

Rook isn’t for children under 13, and we don’t knowingly collect data from them. If you think a child under 13 is using Rook, tell us and we’ll delete their data. To make purchases through Rook you must be old enough to make them where you live, or have permission from the card holder.