Privacy Policy

Swipefast is checkout software operated by Mojo Design Ltd (“we”, “us”). Mojo Design Ltd is the data controller for sellers’ account data; for buyers’ data, the seller is the controller and we process it on their behalf.

There are two kinds of people whose data we touch: sellers, who have accounts with us, and their buyers, whose purchases pass through checkouts we host. This policy covers both, plainly.

If you're a seller

We hold what you give us to run your account: your name, email address, password (stored as a hash, never readable), the products and pages you create, and your subscription status. If you connect other tools, such as a payment provider or an email tool, the keys you paste, or the access you grant when you sign in to Kit or Google, are stored encrypted and used only to do what you connected them for.

If you bought something through a Swipefast checkout

The seller you bought from is responsible for your data; we process it on their behalf. We record what the checkout needs: your name, email address, what you bought, what you paid, and — only where the seller has turned it on — your billing address. When you open a checkout we also note how you got there (the link or site that sent you), the pages you view and what you click there, your type of device and browser, and roughly where your connection comes from (country, region and city as Cloudflare estimates them, never your IP address), so the seller can see which posts and pages bring their buyers. A cookie counts you once rather than on every visit and links a purchase to the visit that led to it. If you choose “Don’t track me” where a checkout offers it, or your browser sends Global Privacy Control, your visits are still counted, but without that cookie and without linking one visit to the next. A seller can add the same visit counting to their own website with Swipefast’s tag; visits there are handled the same way, on the seller’s behalf. Your card number never touches us: it goes directly to the payment provider you see at checkout. Questions about your data should go first to the seller you bought from; their contact details are on your receipt.

If you type your email address on a checkout and leave without paying, it is kept with your name (if you typed it) and the checkout you were on. The seller can then reach you about that checkout: Swipefast may send you one reminder email for them, and if the seller has set up a rule for it, your email address and name are passed to their email tool (such as Kit or Mailchimp) or another tool they connect. The reminder and each rule run at most once per checkout, and never after you have bought it. The seller’s own emails follow their privacy notice and their unsubscribe link.

If you connect Google Calendar

A seller can connect a Google Calendar so their checkout can sell a call that the buyer books while they pay. When you connect, Google asks you to allow four things, and this is all we do with them:

  • Your Google account’s email address, so your settings can show which calendar is connected.
  • Your free and busy times, so a checkout only offers times when you are free. We see when you are busy, never what your events are or who is in them. We ask Google each time a buyer looks for a time and don’t keep the answer.
  • Events on calendars you own, so a booked call goes into your calendar with the buyer invited, and is moved or removed if the booking changes or the order is refunded. We only create and change the events Swipefast books; we don’t read or change your other events.

The access Google gives us is stored encrypted (see “How we protect your data” below) and used only for these bookings. You can disconnect at any time from Integrations in your dashboard: we delete it straight away and ask Google to cancel it. You can also remove Swipefast from your Google account’s permissions page.

Swipefast’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. We don’t sell this data, use it for advertising, or use it to train AI models, and no person at Swipefast reads it unless you ask us to for support, it’s needed for security, or the law requires it.

If you book a call through a checkout, the seller gets your name, email address, the time you picked and any answers the checkout asked for, in an event on their calendar. Google then sends you the invitation.

If you connect Outlook Calendar

A seller can connect an Outlook Calendar (Outlook.com or Microsoft 365) instead of Google Calendar, for the same bookings. Microsoft doesn’t offer a permission limited to the events an app creates, so when you connect, Microsoft asks you to let Swipefast read and write your calendars, plus your email address and lasting access. This is all we do with it:

  • Your Microsoft account’s email address, so your settings can show which calendar is connected.
  • Your busy times, so a checkout only offers times when you are free. We ask your main calendar only for when each event starts and ends and whether it shows you as busy, never its title, details or who is in it. We ask each time a buyer looks for a time and don’t keep the answer.
  • The events Swipefast books, so a booked call goes into your calendar with the buyer invited, and is moved or removed if the booking changes or the order is refunded. We don’t change any other event.

The access Microsoft gives us is stored encrypted and used only for these bookings. You can disconnect at any time from Integrations in your dashboard, and we delete it straight away. Microsoft has no way for an app to hand that access back, so to remove it on Microsoft’s side too, remove Swipefast in your Microsoft account’s privacy settings (Apps and services), or in My Apps for a work or school account. We don’t sell this data, use it for advertising, or use it to train AI models. If you book a call with a seller who uses Outlook, Microsoft sends you the invitation.

How we protect your data

We protect personal and sensitive data, including the Google user data described above, in these ways:

  • Encryption in transit. Every connection to Swipefast uses HTTPS (TLS), and browsers are told to use nothing else (HTTP Strict Transport Security). Our servers talk to our database, Google and the other services listed below over TLS too.
  • Encryption at rest. Our database runs on Cloudflare D1, which encrypts everything it stores with AES-256. On top of that, we encrypt the most sensitive items ourselves before they are stored, with AES-256-GCM: the access Google or Microsoft gives us when you connect a calendar, the access you grant when you sign in to Kit, and the keys you paste for payment and email tools. The encryption key is kept as a secret in Cloudflare, apart from the database, so a copy of the database alone can’t be read.
  • Passwords. We store only a one-way hash of your password (bcrypt), never the password itself. You can also turn on two-step sign-in in your settings.
  • Only what we need. From Google Calendar or Outlook Calendar we keep the access itself and the events Swipefast books. Your free and busy times are checked when a buyer looks for a time and are not stored. Card numbers never reach us.
  • Limited access. Only the people who run Swipefast can reach the production systems, and they look at your data only when you ask for support, for security, or when the law requires it.
  • Deletion. When you disconnect Google Calendar, Outlook Calendar or Kit, we delete the stored access straight away, and ask Google or Kit to cancel it (for Outlook, see above).
  • If something goes wrong. We keep a written plan for replacing every key and secret if one is exposed, and if a breach affects your personal data we will tell you without undue delay.

What we do with it

Run the checkout, deliver receipts and account emails, retry failed payments, show sellers their own sales, and keep the service secure. We do not sell personal data, we do not rent it, and we do not use buyer data to advertise to anyone.

Who else touches it

The service runs on infrastructure and services that process data for us: Cloudflare (hosting and database), Stripe, PayPal or Lemon Squeezy (depending on the seller’s payment choice), Resend (transactional email), and Google Calendar or Microsoft Outlook for sellers who connect one to sell calls. Each holds only what its job requires.

Cookies

We use essential cookies to keep you signed in and to attribute a sale to the link that brought the buyer. That is what makes partner tracking work. On checkouts, thesf_vid cookie (one year) and sf_vs cookie (30 minutes) count each visitor once for the seller’s reports, as described above. On Swipefast’s marketing pages, you can also allow analytics cookies from Google Analytics and Swipefast’s own visit counting (the same sf_vid and sf_vs cookies). They help us understand which pages people visit and, if you subscribe to Swipefast, which visit led to it. You can change your analytics choice from the footer.

A seller may connect Google Analytics or Meta Pixel to their checkout. We show a clear choice before either service loads. If you allow it, checkout visits and purchases are sent to that seller’s account with the service they connected. Swipefast does not use those seller reports to advertise to you.

How long we keep it

Checkout visit details (pages viewed and clicks) are deleted after 13 months, and the summary of each visit after 25 months.

Order records last as long as the seller's account does, because they are the seller's books. When a seller closes their account, their data is exportable for thirty days and then deleted, except what the law requires anyone to keep.

Your rights

You can ask us what we hold about you, ask for it to be corrected, or ask for it to be deleted by contacting Mojo Design Ltd through our support form. If you're a buyer, we may route the request through the seller you bought from, since the records are theirs.

Changes

If this policy changes in a way that matters, we'll say so on this page and, for sellers, by email.