Privacy Policy
_Last updated: 2026-08-21_
Whitney Solutions LLC ("we", "us"), a limited liability company formed in the State of Idaho, USA, operates the scheduling service at https://slotmein.xyz (the "Service"). Contact for privacy matters: andrew@whitneysolutions.tech.
We have no establishment in the EU or the UK and have not appointed a representative under GDPR Art. 27. Privacy questions from anywhere reach us at the address above.
1. What we collect
| Category | Data | Source |
|---|---|---|
| Booking data | attendee name, email, phone number, timezone, language, chosen times, answers to booking questions | provided by the attendee |
| Qualification data | answers submitted on routing forms | provided by the visitor |
| Messages | the full text of SMS messages you exchange with a business through the Service, and the phone number they came from | provided by the sender |
| Host account data | name, email, phone, timezone, sign-in tokens (hashed) | provided by the host |
| Calendar connections | OAuth refresh tokens / CalDAV credentials — encrypted at rest (AES-256-GCM); busy/free times and event data read from connected calendars | authorized by the host |
| Payment data | payment status and amounts. Card details never touch our systems — payment is processed by Stripe | Stripe |
| Technical data | IP address (rate limiting and abuse prevention), server logs | automatic |
We do not sell personal data and do not use it for advertising.
2. Why we process it (legal bases, GDPR Art. 6)
- Performance of a contract: creating, confirming, rescheduling, cancelling bookings; sending booking confirmations, calendar invites, and reminders (transactional email).
- Legitimate interests: service security, rate limiting, fraud prevention, aggregate scheduling analytics for the host organization.
- Consent: where required for optional features — SMS messaging and the AI receptionist described in §3.1. Both are off unless the business you are booking with turns them on.
3. Subprocessors
We use the providers below to run the Service. "When enabled" means the feature is off unless the business you are booking with turns it on, or the operator configures it.
| Subprocessor | Purpose | What reaches them | Location |
|---|---|---|---|
| Railway | infrastructure — application servers and the Postgres database | everything stored by the Service | USA |
| Resend | transactional email delivery | your name and email, booking times, your answers to booking questions, and a calendar (.ics) attachment naming you and the host | USA |
| Twilio | SMS delivery and receipt (when enabled) | your phone number and the full text of every message sent or received, which for on-site services includes the address or access notes you provided | USA |
| Stripe | payment processing (when the business charges for bookings) | your email address, the service name, and the amount. Card details never touch our systems — you enter them on Stripe's own page | USA |
| Anthropic, OpenAI, or OpenRouter | the AI receptionist (when enabled) — see §3.1 | the text of your SMS conversation | USA |
| calendar sync and Google Meet links (when a host connects it) | your name and email on the calendar event, and the booking time | USA | |
| Microsoft | calendar sync (when a host connects Microsoft 365) | your name and email in the event body, and the booking time | USA |
| Zoom | video meeting links (when a host connects it) | your name in the meeting title and your name and email in the agenda | USA |
| Sentry | error monitoring (when enabled) | error reports, which may incidentally contain a request URL or an error message mentioning your address | USA |
International transfers rely on the EU Standard Contractual Clauses (Module Two), together with the UK International Data Transfer Addendum where UK personal data is involved.
3.1 The AI receptionist
Some businesses enable an AI assistant that replies to their SMS messages. When it is on, the text of your recent conversation with that business — up to the last 50 messages, exactly as written — is sent to the AI provider named above so it can draft a reply, along with the business's own description of its services. Your phone number and name are not included in what is sent to the provider.
This feature is off by default and each business chooses whether to turn it on. If you would rather not have your messages processed this way, say so in the conversation and ask to speak to a person, or contact the business directly by another channel.
3.2 Destinations the business chooses
Businesses using the Service can connect it to systems we do not control and cannot list in advance:
- Their own calendar server (CalDAV, e.g. iCloud, Fastmail, Nextcloud) — receives a calendar event containing your name, email, the booking time, and the manage link.
- Their own webhook endpoints — receive the full booking record, including your name, email, phone number and every answer you gave, whenever a booking is created, changed or paid.
Where a business directs your data to a system of its own choosing, that business is the controller for that transfer and its own privacy notice governs it.
4. Retention
Booking records, and the message history attached to them, are retained for as long as the business you booked with keeps its account with us. They are not deleted on a fixed schedule, so if you want yours gone sooner, ask — see §5, and we will act on it.
Calendar credentials are deleted immediately when a host disconnects a calendar. Server logs are kept only while they are useful for security and abuse investigation, and are never used to build a profile of you.
Some of the providers in §3 keep their own copies for their own retention periods — for example a message-delivery log at Twilio or a payment record at Stripe. Deleting your data here does not by itself erase those; where you ask us to, we will pass the request on.
5. Your rights
Subject to applicable law (GDPR, UK GDPR, CCPA/CPRA), you may request access to, export of, correction of, or deletion of your personal data, and may object to or restrict certain processing. Write to the privacy address above. We honor deletion by cancelling your upcoming bookings (with notice) and irreversibly anonymizing your records. You may lodge a complaint with your supervisory authority.
6. Cookies
The booking pages set no tracking cookies. The admin dashboard sets one strictly-necessary, HTTP-only session cookie for sign-in.
7. Security
Transport encryption (TLS), encryption of calendar credentials at rest (AES-256-GCM), hashed sign-in tokens, signed manage links, role-restricted admin APIs, and rate limiting. No system is perfectly secure; we notify affected users and authorities of breaches as required by law.
8. Changes
We will post material changes here and update the date above. Where a change materially affects how we handle personal data, we will email the owner of every active organization before it takes effect.