Privacy Policy
This describes what SlotCue actually stores, where it lives, and who else touches it. It was written from our own database schema and code — not adapted from a template — so everything below is a description of the running system.
On this page
1. Who we are
SlotCue is a scheduling and booking platform published by Joaico. In this policy, “SlotCue”, “we”, and “us” mean Joaico operating the SlotCue service at slotcue.com and book.slotcue.com.
You can reach a human at privacy@ramsford.ai for anything on this page, or support@ramsford.ai for account and billing questions. These are monitored mailboxes operated by our team.
2. Two different roles — please read this one
SlotCue handles two categories of people, and our responsibilities differ for each.
- Businesses that sign up for SlotCue (“account holders”). We decide what we collect from you and why, so we are the party responsible for that data.
- People who book an appointment through a business's SlotCue booking page (“clients”). We store that information on behalf of the business you booked with. The business decides what it collects, how long it keeps it, and what it does with it. We process it to run their booking page and nothing else.
If you booked an appointment and want your details corrected or removed, the fastest route is to contact the business you booked with. You can also write to us at privacy@ramsford.ai and we will pass the request to them and help action it.
3. What we collect
3.1 When a business creates a SlotCue account
| Data | Detail |
|---|---|
| Business profile | Business name, booking-page address (slug), time zone, and your branding choices (colours, logo URL, page copy). |
| Account & sign-in | Email address, your role on the account (owner, admin, manager, staff, viewer), and a one-way hash of your password. We never store your password itself and cannot recover it. |
| Two-factor authentication | If you turn on TOTP two-factor, the shared secret is stored encrypted, never in plain text. |
| Sign-in security records | Session records with creation, expiry and last-seen timestamps, plus the IP address and browser user-agent of the session, and counters for failed sign-in attempts and lockouts. This is how you can review and revoke your own active sessions, and how we stop password-guessing. |
| Team members | Name and email of staff you add, and invitation records for people you invite. |
| Configuration | Services and prices you publish, working hours, locations, time off, and scheduling rules. |
| Billing references | Your plan tier and status, and the Stripe customer and subscription identifiers for your subscription. See §3.4. |
| How you found us | First-touch acquisition details recorded once when you first arrive: the channel, any UTM parameters, the referring site, and the page you landed on. See §4. |
| Activity log | An audit record of significant actions on your account (booking created, appointment cancelled, configuration changed) with the actor and a timestamp. |
3.2 When someone books through a business's booking page
The booking page asks for a name and an email address, and optionally a phone number and a note. We store those together with the service chosen, the appointment start and end time, and the booking status (booked, completed, cancelled, no-show). We also store short-lived “holds” that reserve a slot while a booking is being completed, and they expire on their own.
This data belongs to the business you booked with (see §2). Email is required because that is where the booking confirmation and any appointment reminder are sent.
3.3 Product analytics
We record first-party product events — for example a landing-page visit, a signup step completed, a trial started — with an event type, a random anonymous visitor identifier, a marketing channel label, and the event's own properties. We use this only to understand which parts of the funnel work. We do not use a third-party analytics provider, and there are no advertising or social-media tracking pixels anywhere on SlotCue.
3.4 Payments
Subscription payments for SlotCue are handled by Stripe. Card details are entered on Stripe's own payment pages and go directly to Stripe. We never receive, see, or store your card number. What we store on our side is your Stripe customer identifier, your subscription identifier, your plan tier and subscription status, and the acquisition tags we attach to a subscription so we can tell which marketing channel it came from.
3.5 Mailing list
If you subscribe from one of our blog posts or resources, we store your email address, the segment you tell us you're in if you tell us, which post you subscribed from, the acquisition details in §3.1, and a one-click unsubscribe token. Every email we send you carries a working unsubscribe link, and unsubscribing takes effect immediately.
4. Cookies and local storage
We use no advertising cookies and no cross-site tracking cookies. The complete list is:
| Name | Where | Purpose |
|---|---|---|
bs_sess | book.slotcue.com | Your signed-in session. Strictly necessary — you cannot use the app without it. Holds a random token only; it expires and you can revoke it yourself from your security settings. |
bs_wiz | book.slotcue.com | Remembers your progress through the signup wizard so you don't lose your answers between steps. |
sc_attr | book.slotcue.com | First-touch marketing attribution — the channel, UTM parameters, referrer, landing page and a random visitor identifier, written once and kept for one year. It is never overwritten by later visits and contains nothing that identifies you personally. |
sc_ft | slotcue.com (browser local storage, not a cookie) | The same first-touch marketing parameters, held in your browser so that when you click through to sign up, we can attribute the signup to the right channel. |
Our marketing pages load web fonts from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). Making that request means Google receives your IP address and browser user-agent, as it does for any site using their font service. No font cookie is set and we send Google nothing else about you.
5. Why we use it
- To run the service you asked for — showing availability, holding a slot, creating an appointment, sending booking confirmations and appointment reminders, and rendering the dashboard.
- To keep accounts secure — authenticating you, supporting two-factor, rate-limiting sign-in attempts, letting you see and revoke your sessions, and keeping an audit trail.
- To take payment — running your subscription and handling upgrades, downgrades, renewals and cancellations.
- To support you — answering your emails, which sometimes means looking at your account.
- To improve the product and understand our own marketing — the first-party analytics in §3.3.
- To meet legal and accounting obligations — for example keeping payment records.
We do not use your data, or your clients' data, to train machine-learning models.
6. Who else processes it
This is the complete list of third parties that handle SlotCue data. Each one processes it only to provide the service listed.
| Provider | What they do |
|---|---|
| Vercel | Hosts and serves the SlotCue website and application. |
| Supabase | Hosts the PostgreSQL database where account, configuration, booking and analytics data is stored. |
| Stripe | Processes subscription payments and stores payment-method details. See §3.4. |
| Resend | Delivers our transactional email — booking confirmations, appointment reminders, sign-in and password emails, and mailing-list messages. |
| Google Fonts | Serves the typefaces on our marketing pages. See §4. |
We do not sell personal information, and we do not share it with advertisers or data brokers. We may disclose information if we are legally required to, or to protect the security of the service, and we would tell you unless we were legally prevented from doing so. If the business is ever sold or merged, account data would transfer with it and we would notify you first.
7. Where it is stored
Our database is hosted in the United States (Supabase, US West region). Our application and website are served from Vercel's global network. Stripe and Resend are US-based providers and process data on their own infrastructure. If you use SlotCue from outside the United States, your information will be transferred to and stored in the United States.
8. How it is protected
- Tenant isolation is enforced in the database, not just in code. Every table holding customer data has row-level security switched on and forced, scoped by tenant. A request without a valid tenant claim returns zero rows. One SlotCue account cannot read another's data even if application code has a bug.
- Passwords are stored as scrypt hashes with a per-user salt. We cannot read them.
- Two-factor secrets and any third-party credentials you connect are encrypted before they are written to the database.
- Sessions are stored as hashes, expire, and can be revoked individually by you at any time. Repeated failed sign-ins lock the account temporarily.
- All traffic to slotcue.com and book.slotcue.com is served over HTTPS.
- Significant account actions are written to an append-only audit log.
No system is perfectly secure, and we will not tell you otherwise. If we ever discover a breach affecting your data, we will contact you directly and tell you what happened.
9. How long we keep it
We keep account data, configuration and booking history for as long as the account exists, because the account is a business record its owner relies on. Cancelling a subscription revokes access to paid features but deliberately preserves the data so the account can be reactivated — it does not delete anything.
To have data actually deleted, ask us. Write to privacy@ramsford.ai from the account's email address and we will delete the account and its associated data within 30 days, other than records we must keep for accounting or legal reasons (for example, payment records held by Stripe). Expired booking holds are swept automatically. Mailing-list unsubscribes take effect immediately, and we keep the record of the unsubscribe so that we do not email you again by mistake.
To be plain about it: we do not currently run an automated retention or purge schedule. Deletion happens when you ask for it or when you delete the account.
10. Your choices and rights
Whatever jurisdiction you are in, you can ask us to:
- Give you a copy of the personal data we hold about you.
- Correct anything inaccurate — most of it you can edit yourself in the dashboard.
- Delete your account and the data associated with it (see §9).
- Stop sending you marketing email — use the unsubscribe link in any message, or just tell us.
Send requests to privacy@ramsford.ai. We handle these by hand and will respond within 30 days. We may need to confirm you control the account's email address before we act, so that someone else cannot use this process to reach your data.
SlotCue is a product for businesses. It is not directed at children, and we do not knowingly collect data from anyone under 16. If you believe a child's information reached us, write to us and we will remove it.
11. What we do not do
Stating these plainly is more useful than a list of assurances:
- We do not connect to your Google or Microsoft calendar. That integration is built but is not enabled in production, so no calendar data reaches us today. If and when we turn it on, we will update this policy and describe exactly what we read and write before it goes live.
- We do not process payments from your own clients. Stripe is used for your SlotCue subscription only.
- We do not sell personal information, and we run no advertising or third-party tracking.
- We do not claim certifications we do not hold. SlotCue is not SOC 2 certified, is not HIPAA compliant, and we make no such claim. Please do not use SlotCue to store health information, payment card numbers, government identifiers, or other special-category data.
- We do not train AI models on your data or your clients' data.
An honest note about this document. This policy was written in-house from our own schema and source code so that it is accurate. It has not been reviewed by a lawyer. We chose an accurate, self-authored policy over having none at all, and over publishing boilerplate that describes a system we don't run. If something here is unclear or you need a specific contractual assurance, write to privacy@ramsford.ai and we will answer directly.
12. Changes and contact
When we change this policy we will update the “last updated” date at the top. If a change materially affects how we handle your data — a new processor, a new category of data, a new integration — we will email account holders before it takes effect rather than relying on you to re-read this page.
Privacy and data requests: privacy@ramsford.ai
Account, billing and support: support@ramsford.ai
Our terms of service: slotcue.com/terms