A lawyer is reviewing this page. Any change is posted here with its date before it applies.

Privacy policy

Last updated 1 October 2026. Written in plain language from the way Prytan actually works. A lawyer is reviewing it; any change is posted here with its date before it applies.

Prytan is run by [Company name, kennitala, registered address, Iceland] ("Prytan", "we"). Questions and requests go to support@prytan.ai.

1. What Prytan is, and who we are to you

Prytan lets AI agents (for example Claude or ChatGPT) find an independent business that chose to be listed and book an appointment there, through the booking system the business already uses. Three kinds of people meet Prytan, and our role is different for each:

• Owners, who run a business and sign in to the Prytan app. For your account and your businesses, Prytan is the controller (section 2).
• Customers of a business, whose appointments an AI agent books. For the booking made at that business, Prytan acts on the business's behalf, as its processor, under the data-processing terms; the business is the controller (section 3).
• People who book through their AI and sign in to Prytan on their own page (My Prytan). For that personal account, Prytan is the controller (section 4). The same person's booking at a business is also covered by section 3.

A business's account and a personal account are separate and are never linked.

2. Owners: what we hold, and why

• Your account: your email address, your name, a small profile picture if you add one, and a sign-in record kept by our sign-in provider. You sign in with a link or code sent to your email, or a password you choose; a password is kept, hashed, by the provider, never by Prytan.
• Your settings: theme, date format, timezone, whether you want email alerts, and whether you have seen the first-time walkthrough.
• Your organisation: its name, who belongs to it, and your referral code. If another business signed up through your link, we keep that link between you (its name and whether it connected and paid), to count your free months.
• Your businesses: the name, and the optional details you add for agents (a description, languages, accessibility, parking, payment methods), and each business's share code. The services, prices, staff names, hours, address and contact details come live from your booking system and are not stored by Prytan.
• Your connections: the access token your booking system gave Prytan, or the key you pasted, stored encrypted with a key held outside the database; the account's name and id; when Prytan last checked it and what went wrong if it failed.
• The activity log: every request an AI agent made about your business: the time, what was asked for, the name the agent gave itself, its network address and the outcome.
• Notifications in the app and the emails we sent you.
• AIs you connect as a business (the owner connection): if you add Prytan to your own AI and tick "My business insights" when you sign in (it is offered when the email address you sign in with is your business account's), we keep a pass for that AI (its name, when it was connected and last used, and the tokens, stored hashed), tied to your business account. The same pass can also book for you personally if you tick "Book for me"; the two stay separate. The AI can then read, for your own businesses only, the same figures your dashboard shows (look-ups, which agents, what they asked about, bookings made through Prytan with their customers' names, busiest times, what needs attention). It is read-only, and it never sees customers' phone numbers or emails. What you ask your AI, and what it answers, stays with your AI provider under their terms; Prytan sees only which figures were requested. Change what it may do, or disconnect it, in My Prytan or in Settings at any time. Why: you asked for it (Article 6(1)(b)).

Why: to provide the service you signed up for (the contract: Article 6(1)(b) GDPR), and to keep it secure and fair, for example rate limits by network address (our legitimate interest: Article 6(1)(f)).

3. Customers of a business (Prytan as the business's processor)

When an AI agent books an appointment through Prytan, the agent gives us the customer's full name, phone number and, where the business needs it, email address. We send them to the business's booking system, which creates the appointment and sends its own confirmation, and we keep a booking record: those details, the business, the service, the time, the name the agent gave itself, its network address, and what became of the booking.

The business's owner sees the customer's name and the booking in Prytan (in notifications, emails and the log); the phone number and email are never shown in Prytan, because the booking system already holds them. A short-lived confirmation token (ten minutes) carries the booking details between the agent's two steps; it is signed, not stored.

Prytan never reads a business's customer list or its other appointments. It reads back only the bookings it made, each by its own id, to notice when one was changed or cancelled. The one exception is the known-customer check in section 4, which asks the business's booking system a single yes-or-no question and is not made today.

4. People who book through their AI (Prytan as controller)

When you add Prytan to your AI, you sign in on your own page with a six-digit code we email you, and you give us your name the first time. We hold:

• Your account: the email address you proved is yours with that code, and your name. (Accounts made while sign-in by text was switched on may also hold a phone number proved by a text code. Sign-in by text is switched off; if it comes back, this policy will say so first.)
• Details for your bookings: most businesses need a phone number on a booking. Your AI asks for it once, only when a business needs it, and Prytan keeps it for your next bookings only if you say yes. It is passed to the business's booking system as you gave it, not verified by Prytan. You see it on your page and "Forget it" removes it. You can save one phone number, and change it whenever you like.
• Your bookings made through Prytan: the business, service, time and outcome, shown on your page.
• Which AIs you connected: the name each one registered with, what you allowed it to do, when, and when it was last used; and the passes we issued them (an access pass that lasts an hour and a renewal pass that ends after 90 days without use). Disconnect on your page, or removing Prytan in the AI, revokes the pass at once.
• Your preferences (all optional): usual businesses and staff, the days and times that suit you, areas, a budget, a language and accessibility needs, in your words. You add or change them on My Prytan; your AI saves one only after you say yes in the chat, and every AI you connect reads them when it searches and suggests times, so switching AI loses nothing. Why: you asked for it, and you can remove any of them at any time (Article 6(1)(a) and (b)).
• Busy times your AI passes when searching (from your own calendar, if your AI can see it) are used for that one search to offer only times that fit, and are never stored or logged. Prytan never reads your calendar.
• Booking emails: when you book, move or cancel through Prytan (or the business changes your booking), we email your sign-in address once, with a calendar file so the appointment can be added to, updated in or removed from your calendar.
• How you found Prytan: if you made your account from a business's "Book us through your AI" page, or typed a business's code the first time you connected an AI, which business and when, and the date you first connected an AI. It is counted as a number towards that business's free months. The business never sees who you are. Opening a business's page adds one to a count of visits for that business; nothing about you is kept with it, and no cookie is used for this.
• Safeguards: we count your bookings through Prytan to apply the limits in the terms (5 in 24 hours, 10 upcoming, 3 at one business). If we suspend your account for misuse, we keep when it was suspended and our own short note of why, until it is restored or the account is deleted. Why: protecting businesses' calendars and the service (Article 6(1)(f)).
• Sign-in codes (stored only as a hash, unusable after ten minutes, at most three an hour per address) and browser sessions (30 days; "Sign out everywhere" ends them all).

Known customers. Some staff at some businesses take only customers who have booked with them before. Prytan can check that only with a phone number it has verified by a text code, and texts are switched off, so today no such check is made: your AI points you to the business's own booking page, or its phone number when it has none. A phone number you save on your account is a booking detail: it is passed to the business with your booking and is never checked against any business's records. If text verification returns, the check asks the business's booking system (today: Noona) one question: has this verified phone number booked with this staff member before? The answer is used only to let you book, or not; it is never shown to anyone, the business included, and it is not stored (only a count of how many checks were made for your account that day, kept for two days, so the number of checks can be limited). Why: you asked to book (Article 6(1)(b)).

We do not hold your conversations with your AI, and we do not use your bookings for anything but showing them to you and to the business you booked with. Why we hold the rest: the contract you enter by creating the account (Article 6(1)(b)); keeping the service secure, for example rate limits (Article 6(1)(f)); and, for the saved phone number, your consent, which you can withdraw with "Forget it" (Article 6(1)(a)).

5. What we never hold

• Your conversation with your AI, or the question a customer asked their agent.
• Payment details of any kind. Prytan takes no payment; the business does.
• A business's other appointments or its customer list.

6. Who else handles the data

The booking system is the business's own processor, not ours: Prytan hands the data to it on the business's instruction. The AI you use is your own choice; its provider is not Prytan's processor. Where a provider handles data outside the EU/EEA, we rely on the European Commission's standard contractual clauses or an adequacy decision.

7. How long we keep it

These periods are enforced by a nightly deletion job.

• Bookings: 24 months after the appointment, then deleted.
• Activity log: 12 months, then deleted.
• Notifications: 12 months, then deleted.
• AI passes and sign-in requests: deleted the day after they expire.
• Connection tokens and keys: cleared the moment a connection is disconnected.
• When an owner removes a business: its connections, bookings and notifications are deleted at once; log rows lose their link to it.
• When an owner deletes their account (Settings, Account in the app): the account and its sign-in record at once; if nobody else belongs to the organisation, the organisation too, with its businesses (offline for agents at once), connections, bookings and notifications; log rows lose their link and follow the log period. The free-period record for each booking account is kept, because it belongs to the booking account, not to the owner.
• When a person deletes their personal account (a button on their page): the account, its sessions and its passes at once; bookings lose their link to the person and follow the booking period above.
• Sign-in codes and browser sessions: deleted the day after they were used, ended or expired.
• Encrypted backups of the database are kept for up to 14 days, so deleted data leaves them within that time.

8. Your rights, and how to use them

You may see the data we hold about you, have it corrected or deleted, receive a copy, object to a use, restrict it, and withdraw a consent you gave. How:

We answer within one month. A customer who does not know which business their agent booked can still write to us; the booking record is enough to find it. You may also complain to the Icelandic Data Protection Authority (Persónuvernd) or your own country's authority.

9. Security

Tokens and keys are encrypted at rest with a key held outside the database. All traffic is over HTTPS. Every owner request is limited to the owner's own organisation, and every personal request to the person's own account, and both are covered by automated tests. Logs are cleaned of email addresses and phone numbers as they are written. Database backups are encrypted.

10. Children

Prytan is for businesses and adults. We do not knowingly hold data about anyone under 16.

11. Changes

We post changes here with the date. Material changes are announced in the app and on your page before they apply.

Questions: support@prytan.ai. Report a bug.