Qshot Privacy Policy
Last updated: 16 November 2026
Version: 1.0
This policy explains how Qshot collects, uses, shares and protects personal data under the EU General Data Protection Regulation (GDPR). It is available in English and Arabic. If the two versions differ, the English version prevails, unless mandatory law in your country requires otherwise.
Contents
- Who we are and how to contact us
- Data we collect: your account
- Data we collect: profiles, public content and QR codes
- Data we collect automatically
- Data about visitors and other people who are not Qshot users
- Data from platforms you connect
- Payments and the affiliate program
- Why we use data and our legal bases
- Automated processing and AI
- Who receives your data
- Emails, push notifications and marketing
- How long we keep data
- Deleting your account
- Your rights
- Security
- International transfers
- Children
- Cookies, local storage, SDKs and device permissions
- Platform-specific annexes
- Changes to this policy
- Contact
1. Who we are and how to contact us
Qshot provides digital profiles (mini-websites), QR codes, NFC/QR business cards and related tools through the Qshot apps and websites (together, "the Service").
| Controller | Qshot, Sweden |
| Company registration number | [Company registration number] |
| Postal address | [Company postal address] |
| Privacy contact | [email protected] |
| Data Protection Officer | We are not required to appoint a Data Protection Officer and have not appointed one. Contact us at [email protected]. |
| Lead supervisory authority | Integritetsskyddsmyndigheten (IMY), Box 8114, 104 20 Stockholm, Sweden — www.imy.se — [email protected] |
1.1 Our two roles: controller and processor
We handle personal data in two different roles. Which role applies decides who you should contact first.
- Qshot as controller. We decide why and how data is used for: your account and login, subscriptions and billing, security and logs, moderation of contact-form messages, visitor statistics, the affiliate program, our own emails and notifications, and messages sent to our WhatsApp number.
- Qshot as processor for the profile owner. When a profile owner uses Qshot to collect data from their own visitors and customers, the profile owner is the controller and we process that data on the owner's instructions. This covers: contact-form messages, bookings (including the details of staff the owner lists as booking providers), the owner's address book (contacts), and business cards the owner scans. The terms of this processing (a data processing agreement under GDPR Art. 28) are part of our Terms of Use.
If you sent a message, made a booking or were saved as a contact through someone's Qshot profile, the profile owner is responsible for that data. You can contact them directly, or contact us and we will pass your request on and help the owner answer it.
2. Data we collect: your account
2.1 Registration with email and password
| Data | Notes |
|---|---|
| Name | Required. Used as your account name. |
| Email address | Required. Stored in lower case. |
| Password | Required. We store only a bcrypt hash, never the password itself. |
| Referral code | Optional, only if you sign up through an affiliate link (see section 7.3). |
| Acceptance of the Terms | Required. To register in the web app or the mobile apps, you tick a box that is not ticked in advance to confirm that you accept the Terms of Use. The Terms and this Privacy Policy are both linked on the sign-up page. The policy is there for your information: you are not asked to consent to it, and ticking the box is not consent to data processing (our legal bases are in section 8). We record when you accepted and which version. |
| Technical identifiers | A random account ID (UUID), creation and update dates. |
We do not ask for your date of birth, phone number or gender when you register.
2.2 Sign in with Google, Apple or Facebook
| Provider | What we receive | What we store |
|---|---|---|
| Account ID, name, email, profile picture, email-verified flag | Name, email and the Google account ID. The picture and the verified flag are not stored. | |
| Apple | Apple user ID and email (from Apple's identity token) | Email and the Apple user ID. We do not receive your name from Apple. |
| Account ID, name, email | Name, email and the Facebook account ID. |
We do not store the sign-in token from the provider. A social sign-in account is marked as verified immediately. If an account with the same email already exists, the provider is linked to that existing account.
When a new account is created through a social sign-in, in the web app or the mobile apps, we also ask you to accept the Terms of Use in the same way, with a link to this Privacy Policy, and record your acceptance.
2.3 Device and session data
| Data | Purpose |
|---|---|
| Push notification tokens (Firebase), a random device ID created by the app, platform (iOS/Android) — up to 10 devices | Sending push notifications to your devices |
| App language (locale) | Language of notifications and emails |
| Time zone | Showing times correctly and respecting quiet hours for notifications |
| Last active day | Account activity, shown to our administrators |
In the web app, your login session and some display preferences are kept in your browser's local storage (section 18.1.2). For the services built into the mobile apps and the data they keep on your device, see section 18.3.
2.4 Other account data
- Account photo that you upload. It is stored in our file storage at a publicly readable address (anyone with the exact link can open it).
- Email-change requests: your current and new email address and a confirmation link.
- Feedback you send in the app: your message and an optional screenshot. The screenshot is stored at a publicly readable address.
- Company accounts: if a company account manages your profile, the company can view and edit that profile and see how many unread form messages it has.
3. Data we collect: profiles, public content and QR codes
3.1 Your profile is public
Everything you publish on a Qshot profile is public: the profile name (which is also its web address), photos, cover image, bio, links, social media links, contact buttons (WhatsApp, phone, email, Telegram, Messenger), location blocks, videos, products, services, music links, reviews and any other content block.
- Search engines. Profiles are listed in our sitemap and can be indexed by search engines by default. You can turn this off in the profile settings (the "archive" / search visibility option). The profile then stays reachable through its direct link.
- Previous names. When you rename a profile, the old name keeps redirecting to the new one and stays reserved.
- Hidden items. Content you mark as hidden is not shown to visitors and is not sent to visitors' browsers.
- Images and videos are published as you upload them. Photos can contain embedded information (for example GPS location) added by your camera. Remove it before uploading if you do not want it to be public. For photos uploaded from the mobile apps, see section 18.3.2.
- Custom domains. If you connect your own domain, the domain name is sent to Cloudflare to set up the connection.
3.2 Profile history and support copies
- We keep an edit history of your profile (the last 300 versions, plus up to 10 versions you pin) so that you can compare and restore earlier versions. Each version records who made the change: you, your company account, or a Qshot administrator.
- Before our automated repair tool fixes a broken profile, it saves a copy of the profile so the change can be undone.
- Temporary redirect. If you redirect your profile address to another link for a period, we store the target link, the period and a count of human visits.
- Transfers. If you transfer a profile to another user, we store the transfer request.
3.3 Optional tools that use your profile content
- AI profile generator. If you use it, we send the profession, purpose, bio, services (name, price, description, link, image link), image links, social links and video links you enter to OpenAI. We do not send your account name, email or user ID. The result is returned to you and is not stored by this feature. See section 9.
- AI website generator (web app). If you use it, your business description, the contact details you enter and, optionally, your logo and cover image are sent to OpenAI. See section 9.6.
- Location block. Your search text, the selected place and its coordinates are sent to Google Maps. In the mobile apps, if you tap "my location" in the map picker, your device's coordinates are sent to our server, which looks up the address with Google (section 18.3.2).
- Smart links. If you create smart links (a link that sends people to a different address according to their device), we store the link, its name, the platform and the destination for each device type.
- Music block. Your search text (and the country, by default "US") is sent to Musicfetch and, as a fallback, to Deezer. Your user ID is not sent.
- YouTube block. The channel link or handle is sent to the YouTube Data API to read the channel ID and subscriber count.
- Google reviews block: see section 5.6.
3.4 QR codes
| Data | Notes |
|---|---|
| QR code name, type, content and design (colours, shape, logo, frame text) | Stored in your account. |
| QR content | By type: a link or text, phone number, SMS text, email recipient/subject/body, Wi-Fi network name and password, vCard (name, company, title, phone, email, website, address), or geographic coordinates. |
| QR images (PNG/SVG), uploaded logos and PDF files for dynamic codes | Stored in our file storage at publicly readable addresses. |
| Saved scanned QR codes (mobile apps) | The picture you scanned, the name you give it and everything decoded from the code (see below). |
Anyone who scans a QR code can read its content, so do not put information in a QR code that you would not share with whoever scans it.
Scanning QR codes in the mobile apps. The app decodes QR codes on your device, from the camera, from your gallery or from an image shared from another app. Nothing is sent to us unless you choose to save the scanned code. When you save it, the app uploads the full picture (the camera frame or the chosen image) and everything decoded from the code. For some codes this includes website links, phone numbers, email and SMS content, geographic coordinates, calendar events, other people's contact cards, Wi-Fi network names and passwords, and, for codes printed on identity documents such as driving licences, the holder's name, date of birth, gender, address and licence number. Save only codes you are entitled to keep. Saved scanned-QR pictures are stored privately (only you can open them through the app) and are deleted together with the item or your account.
To draw QR images we send the full QR content and design settings to a QR code rendering service provider, which processes them only on our instructions (including when you preview a design before saving). Dynamic QR codes contain a short Qshot link; the destination is stored with us. When someone scans a dynamic QR code, our public website asks our servers for the destination, forwards the person to it and records the scan. Only the number of scans is stored; we do not store the scanner's IP address, device or location for dynamic QR scans.
3.5 Apple Wallet and Google Wallet passes
You can add your profile to Apple Wallet or Google Wallet from the app.
- The pass contains your profile display name, profile picture (Apple), profile link and a QR code to your profile. For Google Wallet it also contains your bio.
- For Apple Wallet, your device sends us a device library identifier and a push token so that the pass can be updated. We store these together with the pass.
- A pass saved on your phone stays there until you remove it.
3.6 Physical QR/NFC cards
- If you claim a printed Qshot card, we link the card number to your profile and keep a history of assignments.
- Platform cards (cards that send people straight to your Google review page, Instagram, TikTok, WhatsApp, Facebook or Snapchat) store the destination link you set, a label you choose, and a count of human scans with the time of the last scan. We do not store the scanner's IP address or location for these cards.
4. Data we collect automatically
4.1 Server logs
Every request to our API is logged with: the IP address, the request method, the full address requested (including query parameters), the response code and the response time. We do not log request headers, your browser user agent or cookies in this log.
When an error occurs, we also log the request body (with passwords, tokens and receipts removed), the address requested and the IP address.
Logs for our connections to Instagram, Facebook, TikTok, WhatsApp and the music services record the technical steps of a connection, including the replies we receive from those platforms (for example account name and posts), with tokens masked.
Logs are kept for up to 6 months (section 12). Where this policy says that an IP address is "not stored", it means that we do not save it in our database or link it to a message, booking, scan or statistic. The address still appears, like any request, in these server logs and in the network logs of Cloudflare and Amazon CloudFront (section 10.1).
4.2 Security and abuse prevention
We use your IP address in memory to limit how many requests can be sent in a short time. These counters are kept for about one minute and are not written to the database.
4.3 Profile visitor statistics
When someone views your profile or clicks a block, we record:
| Data | Notes |
|---|---|
| Which profile and which block was viewed or clicked | |
| Approximate country | Looked up from the visitor's IP address in a GeoIP database that runs on our own servers. The IP address is not sent to any other company. Only the country is kept. |
| Browser and device type | Derived from the browser's user agent. The full user agent is not stored. |
| Date (rounded to the day) |
We use the visitor's IP address only to determine the approximate country. We do not store it with the statistics or anywhere else in our database; like any request, the visit appears in our server logs, which are kept for up to 6 months (section 4.1). Profile owners see only aggregated figures (views, clicks, countries, browsers, devices) and never see a visitor's IP address.
Automated traffic (bots and crawlers) is not counted.
Profile owners can receive a push notification for each profile view that names the visitor's country (outside quiet hours, 22:00–08:00 in the owner's time zone).
We also keep monthly view and click totals per profile and a daily count of QR/NFC card scans per profile (without IP). To avoid counting the same scan twice, the scanner's IP address is held in memory for 10 minutes and is not written to the database.
5. Data about visitors and other people who are not Qshot users
Where this data comes from. If you are not a Qshot user, we receive data about you in one of three ways: from you (when you visit a profile, send a contact form, make a booking or message our WhatsApp number); from a Qshot user (when they save you as a contact, scan your business card, put your details in a QR code or list you as a booking provider); or from Google (when a profile shows public Google reviews). Each subsection below states the source, the data and what happens to it.
5.1 People who send a contact form
When you send a message through a contact form on a Qshot profile, we receive:
- The answers you enter. The profile owner decides the questions; typically your name, email address, phone number and message. An email address is required unless the owner made it optional.
- Your IP address is used only at the moment of sending, to limit the number of messages that can be sent in a short time. It is not stored with your message.
- The date and time, and the result of our automated check (see section 9.1).
What happens to the message:
- Every message is first checked automatically for fraud, spam and abuse (section 9.1). A message that our checks block is withheld from the profile owner.
- Otherwise it is shown to the profile owner in the app, and the owner gets a push notification (without the message text).
- If the message passes our checks, it is emailed to the owner, with all your answers in the email and your email address as the reply-to address. These emails are sent through ZeptoMail.
- If the owner's plan includes it, your name, email address and phone number are added automatically to the owner's Qshot address book (your message text is not copied there).
For this data, the profile owner is the controller and we are their processor (section 1.1). We use the message for our own purposes only to protect the Service from fraud, spam and abuse (section 9.1).
5.2 People who make a booking
When you book an appointment through a Qshot profile, we receive your name, email address, phone number (optional), time zone, any notes, the selected service, provider, extras and time, and the payment status and amounts.
- The booking and your contact details are shown to the profile owner and to the service provider you booked with (in their staff portal).
- Confirmation, cancellation and reminder emails are sent to you and to the profile owner; the owner's email contains your name, email, phone and notes. The owner may also get a push notification showing your name and the service.
- If the provider has connected Google Calendar, the booking is written to their calendar with the service, your full name, phone number, extras and notes.
- Your name, email and phone are added automatically to the profile owner's address book.
- Deposits are paid on a Stripe Checkout page. The profile owner is the seller and the provider of the service you book; Qshot is a technical intermediary that facilitates the payment through Stripe Connect and keeps a platform fee of 10% of the deposit. You enter your card and contact details directly with Stripe; we do not receive or store card details. We send Stripe only the service name, amount, currency, our platform fee and booking references.
- You can view the status of your booking with the booking reference, and cancel it with the booking reference and your email address.
For this data, the profile owner is the controller and we are their processor (section 1.1).
5.3 People saved as contacts
Profile owners can keep a private address book in Qshot. A contact can be entered by hand, saved from another person's public Qshot profile (by QR code, link or exchange), created from a scanned business card, or added automatically from a contact form or booking (sections 5.1–5.2).
We store the details entered or copied: name, company, job title, phone numbers, email addresses, websites, social links, address, a private note, tags, the source, and the date captured. For contacts saved from a Qshot profile we keep a copy of that profile's public contact details and update it when the profile changes.
If you are a Qshot user and someone saves your profile:
- You get an "added you" notification (immediately or as a digest). You can switch these notifications off.
- You appear in your contact's "who added me" list, and they appear in yours. This is on by default; you can hide yourself from these lists in your contact settings.
- You can block a person from notifying you. You can stop everyone from saving your profile as a contact with the "allow saving as contact" profile setting.
- If you delete your account, copies already saved in other users' address books stay there, frozen, as part of their personal address book.
For contacts that the owner keeps about other people, the owner is the controller and we are their processor (section 1.1).
5.4 People on scanned business cards
When a user scans a business card, the photo of the card (front and, optionally, back) is sent to OpenAI to read the details (section 9.2). The photo is resized to 1600 px, stored privately (only the user can open it through the app) and the extracted details are shown to the user, who must review them before anything is saved. We also check whether the card's phone or email matches a public Qshot profile, to suggest linking them.
5.5 People in QR codes
If a user creates a vCard or other QR code with another person's details, those details are stored with the QR code, sent to our QR rendering service (section 3.4) and encoded in a publicly readable image. When a user saves a scanned QR code that contains another person's details, for example a contact card or the data on a driving licence, those details and the scanned picture are stored in the user's account (section 3.4).
5.6 Authors of Google reviews
If a profile owner adds a Google reviews block, we fetch the business's reviews from Google, including each reviewer's name, profile photo, rating and review text, and display them publicly on the profile. Reviews are kept only as a temporary cache, in line with Google Maps Platform terms.
5.7 People who message our WhatsApp number
If you send a message to Qshot's WhatsApp Business number, Meta passes it to us. We store your phone number, WhatsApp profile name, the message content (text and descriptions of any media; media files are not downloaded) and delivery status. We use these messages only to answer you and to provide support. Only authorised Qshot staff can read them.
5.8 Service providers listed on a booking page
If a profile owner lists staff as booking providers, the provider's name, photo, specialisation, bio and working hours are shown publicly on the booking page. Their email and phone are visible only to the profile owner.
6. Data from platforms you connect
You choose whether to connect these services. You can disconnect them at any time in the app.
| Platform | What we receive | What we store | What we show publicly |
|---|---|---|---|
| Instagram (Instagram Login) | Your Instagram user ID, username, name, profile picture, follower count and recent posts (caption, media, link, date) | IDs, username, name, picture, follower count and an access token (encrypted). Posts are cached for up to 24 hours only. | Your recent posts and basic account details in your profile's social feed |
| Facebook Pages (Facebook Login for Business) | Your Facebook user ID, name and picture; the Pages you manage and any linked Instagram account; Page posts | User ID, name, picture, Page IDs and names, and access tokens (encrypted). Posts are cached for up to 24 hours only. | Your Page or Instagram posts in your social feed |
| TikTok | Your TikTok open ID and union ID, display name, handle, avatar, follower count (if granted) and videos (title, description, cover, link, date, duration) | IDs, name, handle, avatar, follower count and access/refresh tokens (encrypted). Videos are cached for up to 24 hours only. | Your recent videos in your social feed |
| Google Calendar (for bookings) | Your Google account email; your calendar events for the next 90 days | Only the busy start and end times (the event title, guests, description and location are not stored), plus access tokens (encrypted) | Nothing |
Two older feed features also exist: if you connect a Facebook feed the older way, we exchange your Facebook token for a long-lived one and store it on your account; and if you enter the username of an Instagram business account, we fetch that account's public bio, follower count and posts with Qshot's own Instagram account to display them (this data is not stored).
Tokens for Instagram, Facebook and TikTok are renewed automatically in the background while the connection is active. Posts from connected accounts are shown with a link back to the original platform.
We do not sell data from these platforms, use it for advertising, or use it to build profiles of you. See section 19 for the Google, Meta, Instagram and TikTok annexes.
7. Payments and the affiliate program
7.1 Subscriptions
- In the iOS or Android app, you buy subscriptions through Apple or Google. We receive and store the purchase receipt or purchase token and the subscription details returned by Apple or Google (product, dates, renewal and trial status, price and currency, order ID, country). Each store purchase is linked to the Qshot account that made it: the app gives Apple or Google a pseudonymous identifier of your account with the purchase, and restores earlier purchases only when you ask it to.
- If you buy on the web, you pay through Stripe Checkout. We create a Stripe customer with your email, name and Qshot user ID, and pass Stripe your plan and any affiliate discount. Stripe collects your card details directly; we never receive or store card numbers.
- We store a record of each subscription (plan, type, transaction IDs, dates, amount paid, status) and short-lived technical records of Stripe checkout sessions and events.
When a subscription ends without a replacement, your account is moved to the limits of the free plan automatically (see section 9.4).
7.2 Paid bookings (for profile owners)
To take booking deposits, a profile owner connects a Stripe Connect account. Stripe collects the owner's identity and business information (KYC) directly. We store the Stripe account ID and whether charges are enabled.
7.3 Affiliate program
This section applies only if you take part in the affiliate program, either as an affiliate or by signing up through an affiliate link.
If you are an affiliate (accounts are made affiliates by Qshot; affiliates must be at least 18 years old):
- We store your affiliate code (generated from your name unless chosen otherwise), an optional public display name, your commission and discount rates, your payout method and payout details (for example IBAN or PayPal address), admin notes, and your commissions and payouts.
- Your display name is public: it is shown on the referral landing page, to referred users at checkout and in their welcome email.
- You see referred users' masked email address (first letter and full domain), their status, signup and first-payment dates, the plan they bought, and total revenue from your referrals. You do not see their name or IP address.
If you sign up through an affiliate link:
- We record which affiliate referred you, the code, your discount, your status (registered, subscribed, cancelled) and your IP address at signup. We use the IP address only to detect fraud (for example several signups from the same address) and delete it after 180 days.
- If a code is rejected, we record the attempt with the code, the reason and your IP address for 180 days.
- A referral is permanent; you cannot move to another affiliate.
8. Why we use data and our legal bases
| Purpose | Data | Legal basis (GDPR Art. 6) |
|---|---|---|
| Creating and running your account, login, email verification, password reset, email change | Account, device and session data | Contract (6(1)(b)) |
| Publishing your profile, QR codes, wallet passes and cards | Profile and QR content, files | Contract (6(1)(b)) |
| Optional tools you request: AI profile generator, AI website generator, card scanning, saving scanned QR codes, music, location (including "my location" in the app), smart links, YouTube, social feeds, Google Calendar, writing your link to an NFC tag | Data you enter or connect | Contract (6(1)(b)) |
| Running the mobile apps: push-notification token, remote configuration (maintenance mode, minimum app version, feature switches) and app code updates (Firebase Cloud Messaging, Firebase Remote Config, Shorebird) | Device token, random device ID, installation ID, app version, platform, IP address | Contract (6(1)(b)) |
| Crash reports from the mobile apps (Firebase Crashlytics) | Crash report, device model, operating system and app version, installation ID | Legitimate interest (6(1)(f)) — keeping the apps stable and fixing errors |
| Usage analytics in the mobile apps (Firebase Analytics) | App-instance ID, device and app information, usage events, pseudonymous account ID — never your name or email | Consent (6(1)(a)); the app asks before collecting (section 18.3.1) |
| Keeping you logged in to the web app and remembering your language and display preferences | Login token, language, preferences stored in your browser | Contract (6(1)(b)); this storage is strictly necessary under the ePrivacy rules (section 18) |
Affiliate referral cookie (qshot_ref) on the web app, the marketing website and public profile pages |
Affiliate code and time of click | Consent (6(1)(a)) |
| Pre-filling the country code of phone-number fields, using the GeoIP database on our own servers | IP address (not stored) and the country code derived from it | Legitimate interest (6(1)(f)) — making phone numbers easier to enter |
| Recording your acceptance of the Terms of Use (and the version of this policy shown to you), and your consent choices | Time of acceptance or choice, document version | Legitimate interest (6(1)(f)) — being able to show what you agreed to; for consent records, our obligation to demonstrate consent (Art. 7(1)) |
| Answering requests to exercise data protection rights | Your request, identity check, our reply | Legal obligation (6(1)(c)) — GDPR Arts. 12–22 |
| Delivering contact-form messages and bookings to the profile owner, and adding them to the owner's address book | Visitor and booker data | Processing on behalf of the profile owner (Art. 28); the owner chooses the legal basis |
| Checking contact-form messages for fraud, spam and abuse | Form answers | Legitimate interest (6(1)(f)) — protecting owners and visitors from scams and abuse |
| Visitor statistics for profile owners and for running the Service | Country, browser, device, block, date | Legitimate interest (6(1)(f)) — giving owners usage figures and keeping the Service working |
| Contact exchange between Qshot users: "added you" notifications, "who added me" lists and keeping saved copies of public contact details up to date (section 5.3) | Your public profile contact details; who saved your profile and when | Contract (6(1)(b)) — a feature of the Service; you can switch it off in your contact and profile settings |
| Showing public Google reviews on a profile when the owner adds a reviews block (section 5.6) | Reviewer's name, photo, rating and review text | Legitimate interest (6(1)(f)) — letting a business show reviews that are already public on Google |
| Subscriptions, payments and plan limits; for profile owners, booking deposits and our platform fee | Billing and purchase data | Contract (6(1)(b)) |
| Keeping accounting records | Payment and payout records | Legal obligation (6(1)(c)) — Swedish Bookkeeping Act (Bokföringslagen) |
| Affiliate program: attribution, discounts, commissions, payouts | Affiliate and referral data | Contract with the affiliate (6(1)(b)) |
| Affiliate fraud prevention | Signup IP, rejected attempts | Legitimate interest (6(1)(f)) — preventing referral fraud |
| Service emails and push notifications | Email, name, device tokens, event details | Contract (6(1)(b)) |
| Marketing emails, including choosing recipients by segment | Email, name, language, plan, activity data | Consent (6(1)(a)) |
| Security, logs, rate limiting, backups | IP address, request data | Legitimate interest (6(1)(f)) — keeping the Service secure, available and recoverable — and our security obligation (Art. 32) |
| Customer support and administration, including audit logs of administrator actions | Account, profile and payment data | Legitimate interest (6(1)(f)) — running and supporting the Service |
| Answering messages sent to our WhatsApp number | Phone number, name, message | Legitimate interest (6(1)(f)) — answering people who contact us and giving support |
| Feedback you send us | Message, screenshot | Legitimate interest (6(1)(f)) — improving the Service |
| Establishing, exercising or defending legal claims and complying with legal requests | Relevant records | Legal obligation (6(1)(c)) or legitimate interest (6(1)(f)) — protecting our legal position and that of our users |
Where we rely on legitimate interest, you can object at any time (section 14).
8.1 Do you have to provide your data?
- Account. Your name, email address and a password (or a Google, Apple or Facebook sign-in) and your acceptance of the Terms of Use are needed to enter into the contract with us. Without them we cannot create your account.
- Paid plans. To buy a paid plan you give payment details to Apple, Google or Stripe. Without them you stay on the free plan.
- Affiliates. Payout details are needed to pay your commissions. Without them we cannot pay you.
- Visitors. You can view a public profile without giving any data. To send a contact form or make a booking you fill in the fields marked as required; without them the form or booking cannot be sent.
- Everything based on consent is optional. Marketing emails, analytics in the mobile apps and the referral cookie are used only if you agree. Refusing or withdrawing consent does not limit your use of the Service.
- No law requires you to give us personal data.
8.2 How we weigh legitimate interests
For each purpose based on legitimate interest we have checked that our interest is not overridden by your interests and rights. We limit the data to what the purpose needs (for example, we keep a visitor's country but not the IP address), keep it only for the periods in section 12 and give you the right to object. You can ask us for more information about this assessment at [email protected].
9. Automated processing and AI
We use automated tools in the following ways. None of them produces a decision with legal effects or a similarly significant effect on you within the meaning of GDPR Art. 22. You can always ask a person at Qshot to review an outcome by writing to [email protected].
9.1 Contact-form moderation
Every contact-form message is checked before it is delivered to the profile owner. Messages that our checks block are withheld from the owner; flagged messages are shown to the owner with a warning but are not emailed.
- Local rules at Qshot look for known scam phrases (for example requests for card security codes, one-time codes or wallet recovery phrases), blocked domains, link shorteners, many links, HTML code, and the same message sent repeatedly.
- OpenAI then receives the message as text made of the form's questions and answers, with the sender's name, email address and phone number replaced by placeholders before it leaves our server; email addresses and phone numbers typed inside the message are replaced too. Links in the message are kept, because they are needed to detect fraud. We do not send the sender's IP address or any data about the profile owner, and we ask OpenAI not to store the classification request in its stored-completions feature. Two OpenAI models are used: OpenAI's moderation model (default
omni-moderation-latest) and a classification model (defaultgpt-4.1-mini) that labels the message as safe, spam, scam, phishing, abusive or illegal, with a confidence score and a short reason.
Possible outcomes:
| Outcome | What happens |
|---|---|
| Clean | Delivered normally: shown in the app, push notification, email to the owner, added to the owner's address book (if in their plan). |
| Flagged (suspicious) | Shown to the owner in the app with a warning; a neutral push notification; no email; not added to the address book. |
| Not checked (the check failed after several retries) | Shown to the owner with a note; no email. |
| Blocked | Hidden from the owner; no notification and no email. |
When a message is blocked, the sender is told on the page that it was not delivered and how to ask for a review, unless the message is deceptive, high-volume commercial content (spam). In all other cases the sender sees the normal "message sent" confirmation. Very long messages (more than 30 questions, 3,000 characters in one answer or 8,000 characters in total) are rejected with an error and not stored.
Human review. Qshot administrators can review held messages, release a message wrongly held (it then becomes visible to the owner, without a new email) or confirm the decision. A blocked message stays hidden unless an administrator releases it. If you think your message was wrongly blocked, or you are a profile owner who believes messages are missing, write to [email protected]. A member of our team reviews the case and we tell you the outcome.
OpenAI processes this data for us under a data processing agreement and does not use data sent through its API to train its models. See section 12 for how long OpenAI keeps it.
9.2 Business-card scanning
The card photo is sent to OpenAI (default model gpt-4.1-mini). If the result is uncertain, the photo is sent a second time to a stronger model (default gpt-4.1). Your user ID and name are not sent. The result is shown to you for review; nothing is saved as a contact until you confirm it. Photos that are not business cards or are unreadable are rejected.
9.3 AI profile generator
The content you enter (section 3.3) is sent to OpenAI (gpt-4.1). The suggestion is returned to you; you decide whether to use it.
9.4 Other automated rules
- Plan limits. When a subscription ends without a replacement, extra profiles, custom domains, the verified badge and some QR types are switched off automatically; they are switched back on when you subscribe again. Paid content blocks are hidden from visitors if your plan does not include them.
- QR readability. A QR design that our rendering service reports as unreadable is not saved; you can change the design and try again.
- Bookings. A booking is cancelled automatically if the payment session expires (after 30 minutes) or if the time was taken while you were paying (the payment is then refunded). Times are hidden automatically according to the owner's booking rules and the provider's Google Calendar.
- Affiliate referrals. Codes are rejected automatically if unknown, inactive, self-referrals or already used; repeated signups from one IP address are flagged for a person to review. Commissions are approved automatically after the holding period and reversed automatically after a refund.
- Bots. Visits from bots and crawlers are not counted in statistics.
- Rate limits. Too many requests in a short time are refused for about a minute.
- Email bounces. An address that hard-bounces or reports a complaint is blocked from further emails.
9.5 Internal segmentation
Our administrators can filter users by plan, activity, country (inferred from the phone number on your profile or from your account time zone), language, platform, push status, profile views and scans, and referral status. This is used for support, reports and choosing recipients of marketing emails (section 11). No automated action is taken against you on the basis of these filters.
9.6 AI website generator (web app)
If you use the AI website generator ("Try with AI") in the web app, our web server sends the following to OpenAI: your business description and business name, the colours you chose, the interface language, any contact details you enter (phone, email, address, WhatsApp, Instagram, website) and, if you add them, your logo and cover image. Only add photos of other people if you have the right to use them. We do not send your account ID. A text model (default gpt-5.6-terra) writes the website; if necessary the request is sent a second time to correct the format. An image model (default gpt-image-2.5-flare) then creates up to 4 images from text instructions derived from your description and business name; your own images are not sent to the image model. The generated images are stored with your profile like any other image, and an address in the generated site is looked up through our API with Google to show a map (section 3.3). Our web server does not store your request.
The generated website opens in the editor so that you can review and change it; review everything before you publish or share it. Every generated website includes a contact form, which collects visitors' names and email addresses once your profile is live (section 5.1). Content the generator cannot know, such as customer reviews, ratings or figures, is shown only as clearly marked examples that you must replace with real information or remove; we never present it as genuine reviews.
10. Who receives your data
10.1 Service providers
We use the following providers. "Transfer" means data is processed outside the EU/EEA; see section 16.
| Provider | What for | Data | Location | Transfer safeguard |
|---|---|---|---|---|
| Server hosting provider (data centre in Germany) | Running our API, database and cache, the web app, the marketing website and the public pages | All data | Germany (EU) | Not a transfer |
| Amazon Web Services (S3) | File storage (photos, videos, QR images, logos, PDFs, card scans) | Uploaded files; file names contain your user ID | USA (us-east-1) | Transfer — see section 16 |
| Amazon Web Services (S3, backups) | Encrypted database backups, kept for up to 15 days | All database data | USA (us-east-1) | Transfer — see section 16 |
| Amazon Web Services (CloudFront) | Content delivery: serving files from cdn.qshot.com |
IP address and browser data of anyone who loads a file; the files requested | Global network, US company | Transfer — see section 16 |
| Cloudflare | Network protection, routing and custom domains | All traffic to our domains, including the API, file delivery (cdn.qshot.com) and custom domains (IP address, request data); custom domain names |
Global network, US company | Transfer — see section 16 |
| OpenAI | Contact-form moderation; business-card reading; AI profile generator; AI website generator (sent from our web server) | Form answers, with the sender's name, email and phone replaced by placeholders; card photos; profile content you enter; for the website generator, your business description, contact details, logo and cover image | USA | Transfer — see section 16 |
| Shorebird | Delivering app code updates to the mobile apps (section 18.3.1) | App ID, app version, patch number, platform, a random client ID, IP address | USA | Transfer — see section 16 |
| QR code rendering service provider | Drawing QR code images | Full QR content and design; no account data | EU/EEA, or another country under the safeguards in section 16 | See section 16 |
| Musicfetch | Finding a song on all music platforms | Search text, country, song link — sent from our server, without your account, device or IP address | EU/EEA, or another country under the safeguards in section 16 | See section 16 |
| Deezer | Music search fallback | Search text | France (EU) | Not a transfer |
| Google — Sign-In, Calendar, Wallet, Maps/Places, YouTube Data API, Google Play | Login, booking calendar sync, wallet passes, location and review blocks, YouTube block, in-app purchases | As described in sections 2, 3, 5, 6 and 7 | USA / Ireland | Transfer — see section 16 |
| Google — Fonts, YouTube, Maps and Identity Services, loaded by your browser in the web app | Editor previews and Google sign-in (section 18.1.3) | IP address, browser data, video links, map coordinates | USA / Ireland | Transfer — see section 16 |
| Google — Maps SDK, Fonts and YouTube, used directly by the mobile apps | Maps in the location editor, font choices, video previews (section 18.3.1) | IP address, device data, map area shown, video links, fonts requested | USA / Ireland | Transfer — see section 16 |
| Google — Firebase Cloud Messaging | Push notifications | Device token and notification text (may contain a visitor's country, a booker's name or the name of a profile that added you) | USA | Transfer — see section 16 |
| Google — Firebase Crashlytics, Remote Config and Installations (mobile apps) | Crash reports; app configuration | Crash report, device model, operating system and app version, installation IDs | USA | Transfer — see section 16 |
| Google — Firebase Analytics (mobile apps, only with your consent) | Usage analytics | App-instance ID, device and app information, IP address, usage events and screens, pseudonymous account ID — never your name or email | USA | Transfer — see section 16 |
| Providers of embedded content in the mobile apps' editor (YouTube, Vimeo, TikTok, X, Pinterest, Behance, Telegram) | Previews of video, social-post and embed blocks | IP address and the content link; their own cookies inside the preview | Mostly USA | Transfer — see section 16 |
| Apple — Sign in with Apple, App Store, Apple Wallet | Login, in-app purchases, wallet passes | As described in sections 2, 3 and 7 | Ireland / USA | Transfer — see section 16 |
| Meta — Facebook Login, Facebook Pages, Instagram, WhatsApp | Login, social feeds, receiving WhatsApp messages | As described in sections 2, 5.7 and 6 | Ireland / USA | Transfer — see section 16 |
| TikTok | Social feed | As described in section 6 | Outside the EU | Transfer — see section 16 |
| Stripe | Web subscriptions, affiliate discounts, booking deposits | Email, name, user ID, plan, affiliate code, booking references; Stripe collects card and KYC data itself | Ireland, with transfers to the USA | Transfer — see section 16 |
| ZeptoMail (Zoho) | Service emails, booking emails, contact-form emails | Email, name, email content and links; booker and form details in owner emails | EU | Not a transfer |
| Brevo | Marketing email campaigns, only for users who agreed to receive them | Email, first and last name, language, plan name and status, number of profiles, profile link; opens and clicks | France (EU) | Not a transfer |
Every provider that processes personal data on our behalf does so under a data processing agreement (GDPR Art. 28) and only on our instructions. Google, Apple, Meta, TikTok and Stripe are also independent controllers of the data they collect themselves when you use their services; their own privacy policies apply to that data.
10.2 Other users
- Visitors to a profile see everything published on it (section 3.1).
- Profile owners see the contact-form messages, bookings and statistics for their profiles (owners never see visitors' IP addresses).
- Booking providers see the bookings assigned to them, with the customer's contact details.
- Company accounts see and edit the profiles they manage for their employees.
- Affiliates see limited information about the users they referred (section 7.3).
- Users who saved your profile keep your public contact details in their address book (section 5.3).
10.3 Qshot administrators
Authorised Qshot staff can access the administration dashboard to provide support, prevent abuse and run the Service. Within their permissions, administrators can see:
- your account details, sign-in method, last activity, inferred country, language, platforms, plan and payment history;
- all phone numbers, emails, social links and addresses in your profiles, including those you hid from visitors, and can export lists of users and profiles;
- held contact-form messages;
- emails we sent you, with their content and open/click events, and your marketing preference;
- affiliate payout details and referral IP addresses.
Administrators can edit profile content, move a profile to another account, verify or archive a profile, grant or withdraw plans, manage custom domains and cards, and edit platform card links. Edits are recorded in the profile history and most administrative actions are recorded in an audit log with the administrator's ID, email and IP address. Administrators cannot log in as you. When an administrator moves a profile to another account, both the old and the new owner are notified. Administrators can only switch your marketing emails off, not on. Access is limited by individual permissions.
10.4 Authorities and legal requirements
We disclose data to authorities when the law requires it, and we use data where this is necessary to establish, exercise or defend legal claims.
10.5 We do not sell personal data
We do not sell personal data and we do not share it for advertising.
11. Emails, push notifications and marketing
11.1 Service emails
We send emails that are needed to run your account and the features you use: account confirmation, password reset, email change, booking confirmations, cancellations and reminders, contact-form messages, purchase confirmations, plan grants and affiliate notices. You cannot unsubscribe from service emails while you have an account, because they are part of the Service.
We also send automated emails triggered by account events (for example after you register, verify your email or create your first profile). Each of these is classified either as a service email or as a marketing email; the marketing ones follow section 11.2.
11.2 Marketing emails
We send marketing emails (newsletters, offers and campaigns) only if you have agreed to receive them. You can agree when you register, through a separate optional box that is not ticked in advance, or later in your settings. Your agreement is never a condition for using the Service.
- Every marketing email contains an unsubscribe link and a one-click unsubscribe header. The unsubscribe page asks you to confirm and lets you subscribe again.
- You can also change your choice at any time in your settings or by writing to [email protected].
- We choose recipients by segment (section 9.5). You can object to this at any time; we then stop sending you marketing emails.
- For marketing emails we measure delivery, opens and clicks.
- Campaign emails are sent through Brevo (section 10.1). When a campaign ends, the recipient list is deleted from Brevo within 35 days, and your contact record at Brevo is deleted when you unsubscribe or delete your account.
If an email to your address bounces permanently or is reported as spam, we add the address to a block list, stored only as a hash (a one-way fingerprint of the address), and stop sending to it.
11.3 Push notifications
We send push notifications about: profile views (with the visitor's country), new contact-form messages (without the message text), bookings (with the customer's name and the service), someone adding you as a contact, custom domain approval or rejection, and plan changes. Profile-view and contact notifications respect quiet hours (22:00–08:00 in your time zone). We do not send marketing push notifications. The mobile apps also subscribe each installation to a general topic, which we use only for service announcements to all app users. You can switch "added you" notifications off in your contact settings; for other notifications use your device's notification settings.
12. How long we keep data
We keep data only as long as needed for the purpose. The periods below apply. "Until account deletion" means until you delete your account (section 13).
| Data | Retention |
|---|---|
| Account data, account photo, device tokens, settings, contact settings and blocks, "who added me" entries | Until account deletion. Device tokens: up to 10 devices, older ones are replaced. |
| Email-change links | 24 hours |
| Password-reset links / email-confirmation links | 1 hour / 7 days |
| Feedback and screenshots | 24 months |
| Emails you send us (support and data-protection requests) and our replies | 24 months after the matter is closed |
| Profile content, sub-pages, photos and videos, smart links, custom domain names | Until you delete the profile or your account |
| Profile edit history | The last 300 versions plus up to 10 pinned versions; deleted with your account |
| Copies saved before automated repair | 30 days |
| Temporary redirects | 12 months after the redirect ends |
| Previous profile names (kept reserved and redirecting to the new name) | For as long as the profile exists |
| Profile transfer requests | Until account deletion |
| Visitor statistics (country, browser, device, date — no IP address) | For as long as the profile owner's account exists; deleted when the account is deleted |
| Monthly totals and daily scan counts per profile | For as long as the profile owner's account exists; deleted when the account is deleted |
| Scanner IP for duplicate-scan check | 10 minutes, in memory only |
| QR codes, QR images, logos, scanned-QR images, PDF files | Until you delete the item or your account |
| Wallet pass records and Apple device registrations | Until you delete your account |
| Contact-form messages, including messages blocked by moderation (the sender's IP address is not stored) | For as long as the profile owner's account exists; deleted when the account is deleted |
| Data sent to OpenAI (form moderation, card reading, AI generators) | OpenAI keeps it for up to 30 days to monitor for abuse and then deletes it. It is not used to train OpenAI's models. |
| Address-book contacts | Until the owner deletes them or deletes their account; deleted contacts are erased 30 days after deletion |
| Contact change history | 180 days |
| Business-card photos and extracted details | Free plan: 90 days. Paid plans: until the user deletes them or their account. Extracted details are deleted together with the photo. |
| Bookings and customer details | For as long as the profile owner's account exists; deleted when the account is deleted |
| Booking provider details | Until the owner removes the provider, then 30 days |
| Google Calendar connection | Until you disconnect it or delete your account |
| Busy times from Google Calendar | Only for the next 90 days |
| Booking hold while you pay | 5 minutes |
| Stripe Connect account ID and charge status (profile owners who take deposits) | Until you remove the Stripe connection or delete your account |
| Subscription and payment records | 7 years after the end of the financial year to which the record belongs, under the Swedish Bookkeeping Act (Bokföringslagen), then deleted. When you delete your account we keep only the details needed for accounting (amount, date, currency, payment reference, country). |
| Stripe event and checkout records | 90 days / 30 days |
| Rejected referral attempts with IP | 180 days |
| Referral signup IP address | 180 days |
| Referral record (which affiliate referred you, the code, your discount and your status) | Until you delete your account; amounts in commission records follow the 7-year rule below |
| Affiliate profile and payout details | Until the affiliate membership ends and the last payout is settled. If an affiliate deletes their account with an unpaid balance, the balance remains owed and we keep the payout details and email address only to pay it. |
| Commissions and payouts | 7 years after the end of the financial year to which the record belongs, under the Swedish Bookkeeping Act (Bokföringslagen), then deleted |
| Instagram, Facebook and TikTok connections | Until you disconnect them or delete your account |
| Cached posts and videos | Up to 24 hours |
| WhatsApp webhook raw events | 30 days |
| WhatsApp messages and delivery statuses | 12 months |
| Google reviews shown on profiles | Temporary cache only |
| Physical and platform card history | The card stays in our stock; your ID and scan counts are removed from it when you delete your account |
| Content of emails we sent | 180 days |
| Email delivery records (address, name, opens and clicks) | 12 months |
| Marketing preference | Until account deletion |
| Email block list (bounces, complaints and unsubscribes) | Kept only as a hash of the address, also after account deletion, so that we keep respecting the block |
| Administrator audit log | 24 months; your email is removed from it when you delete your account |
| Administrator tags on your account | Until account deletion |
| Request logs / error logs / integration logs | Up to 6 months, then deleted automatically |
| Records of your acceptance of the Terms (with the policy version shown), and of your consent choices | Until account deletion |
Referral cookie qshot_ref (only with your consent) |
60 days. The cookie-choice record is kept for 12 months |
| Rate-limit counters | About 1 minute, in memory |
| App usage analytics (Firebase Analytics, only with your consent) | 14 months, then deleted by Google |
| App crash reports (Firebase Crashlytics) | 90 days |
| Data the mobile apps keep on your device | Login token, device ID, account preferences, offline queue, widget and watch data, push token and analytics ID: cleared when you log out or delete your account. Display preferences and the image cache: until you uninstall the app (section 18.3.3) |
| Encrypted backups | Up to 15 days, then deleted automatically. Data you delete remains in backups until they expire. |
13. Deleting your account
You can delete your account in the app. Deletion is immediate and cannot be undone.
Before you delete:
- Cancel any auto-renewing subscription first. You cannot delete an account while it has a subscription that renews automatically. Cancel a web (Stripe) subscription in the billing portal, and an App Store or Google Play subscription in your Apple or Google account settings. Once automatic renewal is switched off, you can delete your account. This does not limit your right to erasure (section 14): if you are unable to cancel, write to us.
- Download anything you want to keep, for example your contacts (vCard; CSV/VCF export on Business and Team plans).
What we delete: your account and login methods, all your profiles and their sub-pages, edit history, statistics, photos, videos and files, QR codes and their images, logos, wallet records, your address book and scanned cards, contact-form messages and bookings received through your profiles, connections to Instagram, Facebook, TikTok and Google (we also revoke our access at Meta, Instagram, TikTok and Google), your email preferences, your contact record at Brevo, and administrator tags. Physical cards linked to you are unlinked and returned to stock. If you delete your account in a mobile app, the app also clears the data it keeps on that device (section 18.3.3).
What we keep, and why:
| Data | Why | How long |
|---|---|---|
| Subscription, payment, commission and payout records (only the details needed for accounting) | Swedish Bookkeeping Act (Bokföringslagen) | 7 years after the end of the financial year to which the record belongs, then deleted |
| If you are an affiliate with an unpaid balance: the balance, your payout details and your email address | To pay you the commission you earned | The balance remains owed to you after deletion; payout details and email are kept only until it is paid, then the financial records follow the 7-year rule above |
| A hash of your email address on our email block list, if it is there | To keep respecting a bounce, complaint or unsubscribe | For as long as the block is needed |
| Data in encrypted backups | Backups cannot be edited | Until the backup expires (up to 15 days) |
| Server logs | Security | Up to 6 months (section 12) |
| Copies of your public contact details in other users' address books | Part of their personal address book | Until they delete them |
| Bookings written to a provider's Google Calendar | Controlled by the provider in their Google account | Until the provider deletes them |
| Records kept by Stripe, Apple and Google | Their own legal obligations | Under their policies |
| A wallet pass saved on your phone | Stored on your device | Until you remove it |
14. Your rights
Under the GDPR you have the following rights. Exercising them is free of charge.
- Access — get confirmation of whether we process your personal data, a copy of it, and information about how we use it.
- Rectification — have inaccurate data corrected and incomplete data completed. You can change your name, email, password, photo and profile content in the app.
- Erasure — have your data deleted. You can delete your account in the app (section 13) or ask us.
- Restriction — ask us to limit how we use your data, for example while we check its accuracy or examine an objection.
- Data portability — receive the data you gave us, where we process it by automated means on the basis of consent or contract, in a structured, commonly used and machine-readable format, and have it sent to another controller where technically feasible.
- Objection to legitimate-interest processing — object at any time, on grounds relating to your situation, to processing based on legitimate interest (section 8). We then stop, unless we have compelling legitimate grounds that override your interests or need the data for legal claims.
- Objection to direct marketing — object at any time to the use of your data for direct marketing, including the selection of recipients by segment. We always stop.
- Withdrawal of consent — where we rely on consent (marketing emails, analytics in the mobile apps and the referral cookie), withdraw it at any time: through the unsubscribe link, the app settings, the cookie settings link, or by writing to us. Withdrawal does not affect the lawfulness of processing carried out before it.
- Human review — ask a person at Qshot to review an automated outcome (section 9).
- Complaint — lodge a complaint with the Swedish Authority for Privacy Protection, Integritetsskyddsmyndigheten (IMY), Box 8114, 104 20 Stockholm, Sweden, www.imy.se, [email protected], or with the supervisory authority of the EU/EEA country where you live, work or where you believe the infringement took place.
How to exercise your rights. Write to [email protected], preferably from the email address of your account. To protect your data we check your identity before we act; if we cannot identify you from your message, we ask for additional information. We answer without undue delay and at the latest within one month. If a request is complex or we receive many requests, we extend this by up to two further months and tell you why within the first month. If we do not act on a request, we tell you why and how to complain. We refuse or charge a reasonable fee only for requests that are manifestly unfounded or excessive.
Visitors, bookers and people saved as contacts. For data a profile owner collected about you (sections 5.1–5.4), the owner is the controller; contact them first. You can also write to us at [email protected]: we forward your request to the owner and help them respond. For visitor statistics, moderation records, logs and WhatsApp messages, Qshot is the controller; write to us directly.
15. Security
We protect personal data with technical and organisational measures appropriate to the risk, including:
- Passwords are stored only as bcrypt hashes.
- Access tokens for Google Calendar, Instagram, Facebook and TikTok are encrypted with AES-256-GCM.
- Business-card photos are stored privately and are only available to their owner through the app.
- Backups are encrypted before they are uploaded.
- All connections to our domains — the API, our websites, file delivery and custom domains — use HTTPS (TLS) and pass through Cloudflare's network protection.
- Request rate limits protect against abuse.
- Only authorised administrators can access the administration dashboard. Each administrator has individual permissions, and administrative actions are recorded in an audit log.
- In the web app, code embedded in a profile runs isolated from your login, our servers accept AI requests only from logged-in users within rate limits, and the web app sends security headers that restrict which content can run on it.
- In the mobile apps, your login token is kept in the device's secure storage and excluded from device backups, and the release versions of the apps do not write the contents of requests or responses (such as passwords or tokens) to the device log.
No system is completely secure. If a personal data breach is likely to result in a risk to your rights and freedoms, we will notify IMY within 72 hours and, where the risk is high, inform you.
16. International transfers
Our servers and main database, the web app, the marketing website and the public pages are hosted in Germany. Some providers process data outside the EU/EEA, mainly in the USA: Amazon Web Services (file storage and encrypted backups in us-east-1, and content delivery through Amazon CloudFront), Cloudflare, OpenAI, Google (including Firebase), Apple, Meta, TikTok, Stripe and Shorebird. Section 10.1 lists each provider, the data it receives and its location.
We transfer personal data outside the EU/EEA only under one of these safeguards:
- Adequacy decision. For providers in the USA that are certified under the EU-U.S. Data Privacy Framework, we rely on the European Commission's adequacy decision for that framework.
- Standard Contractual Clauses. For all other transfers to countries without an adequacy decision, we rely on the Standard Contractual Clauses adopted by the European Commission (Decision (EU) 2021/914), together with additional measures where needed, such as encryption.
Our encrypted database backups are stored with Amazon Web Services in the USA (us-east-1) for up to 15 days and are then deleted automatically. They are encrypted before they leave our servers and are covered by the same safeguards.
You can obtain a copy of the safeguards that apply to a transfer of your data by writing to [email protected].
17. Children
The Service is not intended for children. You must be at least 13 years old, or the higher age of digital consent in your country (up to 16 in some EU countries), to create an account. If you are below that age, you may not create an account. If you are under 18, you need the agreement of your parent or guardian to make purchases. Affiliates must be at least 18 years old.
We do not knowingly allow children below the required age to create an account. If we learn that such an account exists, we delete it and its data. If you believe a child has given us personal data, contact [email protected].
18. Cookies, local storage, SDKs and device permissions
This section describes what Qshot stores on or reads from your device in each place where you use Qshot: the web app, where you manage your account, profiles and QR codes (18.1); our marketing website qshot.com (18.2); and the Qshot iOS and Android apps (18.3). Our API servers do not set any cookies. Public profile pages, QR landing pages and public booking pages are covered in section 18.4.
18.1 Web app
18.1.1 Cookies
| Cookie | Set by | Purpose | Content | Duration | Type |
|---|---|---|---|---|---|
NEXT_LOCALE |
Qshot (first party) | Remembers the interface language you chose | Language code (for example en or ar) |
Until you close your browser | Strictly necessary |
| Cookie-choice record | Qshot (first party), on .qshot.com |
Remembers whether you accepted or refused the referral cookie, so that we do not ask on every visit | Your choice and its date | 12 months | Strictly necessary |
qshot_ref |
Qshot (first party), on .qshot.com, so it is shared with our marketing website (section 18.2) and our public profile pages |
Credits an affiliate when you sign up after following their ?ref= link (section 7.3) |
The affiliate code and the time you clicked the link; no other data about you | 60 days; deleted earlier when you register or sign in | Affiliate attribution (not strictly necessary) — set only if you accept it in our cookie banner |
We do not use cookies to keep you logged in. The web app does not use analytics, advertising or tracking cookies, pixels or similar tools.
18.1.2 Local storage in your browser
| Name | Purpose | Content | When it is removed |
|---|---|---|---|
qshot-auth |
Keeps you logged in | Your login token and basic account details (account ID, name, email address, picture) | The token and account details are cleared when you log out, when your session is no longer accepted, and when you delete your account |
qshot.v1.device.* |
Display preferences on this device (for example whether you have seen the "get the app" prompt, and the quick-action button in your contacts) | Small setting values | They stay on the device until you clear your browser data |
qshot.v1.acc.<account ID>.* |
Preferences for your account on this device (recently used colours in the editor, tips you dismissed, the last plan-activation notice shown) | Small setting values; the name contains your account ID | They stay after you log out, so they are there when you log in again, and are removed when you delete your account |
This storage is needed to provide the web app you asked for. The web app does not use session storage or IndexedDB.
18.1.3 Content from other providers loaded by the web app
When you use some features, your browser connects directly to another provider. That provider receives your IP address and browser information and may set its own cookies under its own privacy policy:
| Provider | When | What it receives |
|---|---|---|
| Google Fonts | Automatically when you open the profile editor, theme settings or the font list | IP address, browser information and the fonts requested. The fonts of the web app's own interface are hosted by us. |
| YouTube | Video titles and thumbnails load automatically when the editor shows a video block; the YouTube player (youtube.com) loads only when you click play | IP address and the video link; when the player loads, YouTube's own cookies |
| Google Maps | Automatically when the editor shows a location block (as a map image or an embedded map) | IP address and the coordinates; an embedded Google map may set Google cookies |
| Providers of embedded content | Automatically when the editor shows an Embed block that you or a template added (for example a review widget) | Whatever that code requests, at least your IP address. Embedded code runs in an isolated frame and cannot access your Qshot login. |
| Google (example images) | When you preview some ready-made templates | IP address |
| Google Identity Services | Only when you click "Continue with Google" | IP address and your Google cookies, as part of signing in (section 2.2) |
Video feeds from YouTube and Vimeo shown in the editor are fetched through our own server, so those providers do not receive your IP address for them. When a phone-number field is shown empty, the country code is pre-filled by our own server from its GeoIP database; no other provider receives your IP address for this.
18.1.4 Device permissions and browser features
| Feature | When it is used | Does data leave your device? |
|---|---|---|
| Camera (QR scanner) | Only on the QR scanning page, after your browser asks for permission | No. QR codes are decoded on your device and camera images are not sent anywhere. The camera stops after the first result or when you leave the page. |
| Camera or file picker (business-card scanning) | When you choose to scan a card | Yes. The photo is uploaded to Qshot (sections 5.4 and 9.2). |
| File uploads (photos, logos, images) | When you choose a file | Yes. The file is uploaded to Qshot; cropping happens on your device. |
| Clipboard | Writing: when you click to copy a link or code. Reading: only when you click "Paste" (your browser asks first) | No |
| Sharing | When you click share | Handed to your device's share menu |
| Sign-in windows | When you connect Google Calendar, Facebook, Instagram or TikTok | The provider's own page opens (section 6) |
| Live updates | While you are logged in, the web app keeps a connection open to our API to receive plan updates | No (receive only) |
The web app does not use your location, notifications, microphone or screen sharing.
18.1.5 Your choices
You can delete cookies and local storage in your browser settings at any time; if you delete qshot-auth, you are logged out. Our cookie banner offers "Accept" and "Refuse" with equal prominence, and nothing that needs consent is stored before you choose. You can change your choice about the referral cookie at any time through the cookie settings link in the web app; withdrawing consent deletes the cookie.
18.2 Marketing website (qshot.com)
Our marketing website at qshot.com presents Qshot and links to our apps. It has no forms and no user accounts.
| Name | Type | Purpose | Content | Duration |
|---|---|---|---|---|
qshot_ref |
Cookie, first party, on .qshot.com (shared with the web app and our public profile pages) |
Credits an affiliate if you sign up after following their ?ref= link (section 7.3); the web app reads it when you register |
The affiliate code and the time of the click. It is written only after our API has confirmed that the code is valid; an invalid code is not stored. Not strictly necessary — set only if you accept it in our cookie banner (section 18.1.1) | 60 days; a newer referral replaces the older one |
qshot-theme |
Local storage | Remembers whether you chose the light or dark display | light or dark |
Until you clear your browser data |
| Cookie-choice record | Cookie, first party, on .qshot.com |
Remembers whether you accepted or refused the referral cookie. Strictly necessary | Your choice and its date | 12 months |
- Referral check. Only when the link you followed contains
?ref=, your browser sends the code to our API to check it, so our API receives your IP address like any other request (section 4.1). - No analytics or trackers. The marketing website uses no analytics, advertising or tracking tools, pixels, chat widgets, CAPTCHA, third-party scripts or embedded frames. Its fonts and images are delivered from our own server, so no other provider receives your IP address when you browse it. It does not set a language cookie.
- Contact links. The WhatsApp button opens WhatsApp (a Meta service) with our number, and the email link opens your own email program with a message to us. Nothing is sent until you choose to send a message there; WhatsApp then handles it under its own terms and we receive it as a message to Qshot.
- App store links open the App Store or Google Play.
- The pages for this Privacy Policy and our Terms, QR landing pages (
qshot.com/qr/…), public booking pages and platform-card redirect pages are served on the same domain by a different part of our website (section 18.4).
You can delete the cookie and local storage in your browser settings at any time, and change your choice about the referral cookie through the cookie settings link on the website.
18.3 Mobile apps (iOS and Android)
18.3.1 Services built into the app (SDKs)
| Service | Provider | What it does | Data it receives | When |
|---|---|---|---|---|
| Firebase Analytics | Measures how the app is used (screens viewed, sessions, app updates, purchases, notification opens) so that we can improve it | An app-instance ID, device model, operating system, app version, language, IP address (used by Google to derive an approximate region), usage events and screen names, and a pseudonymous Qshot account ID. Never your name or email address. | Only if you agree when the app asks; you can change your choice at any time in the app settings | |
| Firebase Crashlytics | Reports app crashes so that we can fix them | Crash report (technical stack trace), device model, operating system and app version, a random Crashlytics installation ID. Not linked to your account | When the app crashes | |
| Firebase Remote Config and Installations | Lets us switch on maintenance mode, set the minimum supported app version and switch features on or off | A Firebase installation ID and the app version | When the app starts (at most every 6 hours) | |
| Firebase Cloud Messaging | Delivers push notifications (section 11.3) | A device token, which the app sends to us with a random device ID, the platform and the app language | After you log in; notifications appear only if you allow them | |
| Shorebird | Shorebird | Delivers updates to the app's code without a new store release | App ID, app version, patch number, platform and processor type, a random client ID and the IP address | When the app starts |
| Google Maps SDK | Shows maps in the location-block editor | IP address, the map area displayed and device information | When you open the map editor or a location block | |
| Google Places (through our server) | Address search and "my location" in the map picker | Search text, the chosen place and, if you tap "my location", your coordinates — sent to our server, which asks Google | When you search or tap "my location" | |
| Sign in with Google / Sign in with Apple | Google / Apple | Signing in (section 2.2) | Handled by Google or Apple on your device; we receive a sign-in token | Only if you choose it |
| App Store / Google Play billing | Apple / Google | In-app purchases (section 7.1) | The purchase is handled by the store; we receive the receipt or purchase token | When you buy or restore a purchase |
| Apple Wallet / Google Wallet | Apple / Google | Adding your profile pass (section 3.5) | The pass created by our server | When you tap "Add to Wallet" |
| Embedded content and fonts | YouTube, Vimeo, TikTok, X, Pinterest, Behance, Telegram; Google Fonts | Previews of video, social-post and embed blocks in the editor; font choices | IP address and the content link. Embedded posts and YouTube videos load in a web view where the provider may set its own cookies. Google Fonts receives the font requested | When you add or preview such a block, or open the font, frame or template choices |
The app contains no advertising SDKs, does not use the advertising identifier of your device and does not track you across other companies' apps or websites. Our Firebase project is not linked to advertising products. In the booking-provider editor, the app suggests your country's phone code from your SIM card or, if that is not available, asks our own server, which uses its GeoIP database; no other provider receives your IP address for this. QR codes are decoded on your device. AI features (business-card reading, website generation) run on our servers, not in the app (section 9).
18.3.2 Device permissions
The app asks for a permission only when you use the feature that needs it, except notifications, which it asks for shortly after you log in. You can change any permission at any time in your device settings.
| Permission | Used for | Does data leave your device? |
|---|---|---|
| Camera | Scanning QR codes and photographing business cards | QR codes are decoded on your device; nothing is sent unless you save the scanned code, and then the picture and its decoded content are uploaded (section 3.4). Business-card photos are uploaded to Qshot to read the details (sections 5.4 and 9.2). The camera records no sound. |
| Photos | Choosing images to upload (account photo, profile and QR images, logos, feedback screenshots, business cards) and saving images to your gallery | Only the images you choose are uploaded, when you save. Before uploading a photo, the app removes embedded metadata such as the GPS location. On Android the app uses the system photo picker and does not ask for access to all your files. |
| Location (only while using the app) | Placing the pin when you tap "my location" in the map picker | Your coordinates are sent to our server, which looks up the address with Google (section 3.3). If you save the place, it becomes part of your public location block. The app never uses your location in the background. |
| NFC | Writing your public profile link to an NFC tag or card you hold | The app only writes one link to the tag. It does not read the tag's content or its ID, and nothing is sent to us. |
| Notifications | Push notifications (section 11.3) | The device token (section 18.3.1) |
The app does not access your device's contacts or address book or your microphone. The "Contacts" feature in the app is your Qshot address book stored with us (section 5.3).
18.3.3 Data stored on your device
| Data | Purpose | When it is removed |
|---|---|---|
| Login token | Keeps you logged in | Stored encrypted in your device's secure storage (iOS Keychain / Android Keystore) and excluded from device backups. Removed when you log out or delete your account. |
| Random device ID | Identifies this installation for push notifications | When you log out or delete your account |
| Account settings (watch settings, contacts inbox state, offline-capture setting, the profile shown in the home-screen widget) | Remembering your choices in the app | When you log out or delete your account |
| Offline queue: contacts and business-card photos captured without a connection | Sent to Qshot when you are back online | When you log out or delete your account; excluded from device backups |
| Home-screen widget and watch data (QR image of your profile, display name, profile link) | Showing your QR code on the home screen and on your own watch | When you log out or delete your account |
| Display preferences (recent colours, default currency, interface language, update reminders) | Convenience | When you uninstall the app |
| Image cache | Faster loading of images from cdn.qshot.com |
Managed automatically; removed when you uninstall the app |
| Firebase identifiers and the push token (section 18.3.1) | Analytics, crash reports, configuration and notifications | The analytics ID and the push token are reset when you log out or delete your account |
When you log out or delete your account, the app clears the data listed above as removed at that point, resets the analytics ID and the push token so that later activity on the device is not linked to your account and the device no longer receives your notifications, removes your QR code from the home-screen widget and ends the Google sign-in session in the app.
18.3.4 Your choices in the app
- Analytics: you can switch app analytics on or off at any time in the app settings (section 18.3.1).
- Permissions and notifications: manage them in your device settings. If you have refused a permission, the app shows a button that opens the settings. "Added you" notifications can also be switched off in your contact settings.
- Home-screen widget: remove it from your home screen.
- Account deletion: you can delete your account in the app settings (section 13).
- Uninstalling the app removes all the data it keeps on your device, except copies in your own device backups.
18.4 Public profile pages, QR landing pages and public booking pages
This section applies when you visit a Qshot public profile (at {name}.qshot.com or on the owner's own domain), a QR landing page (qshot.com/qr/…), a public booking page, a platform-card redirect page, or the pages where this policy and our Terms of Use are published. These pages are hosted on our servers in Germany. You do not need an account to use them.
What these pages store on your device
| Name | Type | Purpose | Duration | Consent |
|---|---|---|---|---|
qshot_ref |
Cookie, first party, on .qshot.com |
Credits an affiliate if you sign up after following their ?ref= link (section 7.3). Contains the affiliate code and the time of the click |
60 days | Set only if you accept it in our cookie banner |
| Cookie-choice record | Cookie, first party, on .qshot.com |
Remembers whether you accepted or refused the referral cookie | 12 months | Not needed — strictly necessary |
Qshot sets no other cookies on these pages. The cookie banner appears only when a page is about to use something that needs your consent, and it offers "Accept" and "Refuse" with equal prominence.
What these pages do not use. Qshot does not place third-party analytics, advertising or tracking tools, pixels or fingerprinting on these pages, and does not build a profile of you across visits.
Counting visits and scans. When you open a profile, click a block or scan a QR code or card, our servers count the event and record the profile and block, the date, your approximate country (derived on our own servers from your IP address), and your browser and device type (section 4.3). Your IP address is not stored with these statistics and is not sent to any other company for them. No cookie or device identifier is used for counting. Visits from bots are not counted. The legal basis is legitimate interest (section 8).
Contact forms and bookings. What you enter in a contact form is handled as described in section 5.1, and a booking as described in section 5.2. Nothing you type is sent before you press send or confirm. If a booking requires a deposit, you are taken to a Stripe Checkout page, where Stripe sets its own cookies under its own privacy policy.
Dynamic QR codes and platform cards. A QR landing page or card redirect page asks our servers for the destination, forwards you to it and adds one to the scan count. Nothing else about you is stored with the scan (sections 3.4, 3.6 and 4.1). The destination is a website chosen by the owner of the code or card and has its own privacy policy.
Files and images on these pages are delivered from cdn.qshot.com through Amazon CloudFront and Cloudflare, which receive your IP address and browser data in order to deliver them (section 10.1).
Content embedded by the profile owner. A profile owner can add content from other platforms to their page, for example a YouTube or Vimeo video, a Google map, a social media feed or post, a music player or a review widget. When a page shows such content, your browser loads it directly from that platform, which then receives your IP address and browser data and sets its own cookies under its own privacy policy. The profile owner chooses this content and is responsible for it.
Your choices. You can change your cookie choice at any time through the cookie settings link at the bottom of these pages, and delete cookies in your browser settings. For your rights regarding data collected through these pages, see section 14.
19. Platform-specific annexes
Annex A — Google user data (Google API Services, Limited Use)
This annex explains what Google user data Qshot accesses, and how we use, store, share and delete it.
Qshot'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.
A.1 Google user data we access
| Google feature | Permissions (scopes) we request | Google user data we access |
|---|---|---|
| Sign in with Google | email |
Your Google account email address, your name and your Google account ID |
| Google Calendar (optional, for people who offer bookings) | https://www.googleapis.com/auth/calendar.events, openid, email |
Your Google account email address (to show which account is connected), and the events in your primary calendar for the next 90 days |
We request Google Calendar access only when you choose Connect Google Calendar in your booking settings. We do not access your contacts, Gmail, Drive, or any other Google data.
A.2 How we use Google user data
- Sign in with Google: to create your Qshot account and log you in.
- Google Calendar — reading: to see when you are busy, so that customers cannot book you at a time when you already have an event. From each event we read only its start time, end time and whether it marks you as busy.
- Google Calendar — writing: to add each Qshot booking to your primary calendar as an event (with the service, the customer's name and phone number, extras and notes), and to update or remove that event when the booking is changed or cancelled.
We use Google user data only to provide these features to you. We do not use it for advertising, we do not sell it, and we do not use it to develop, improve or train AI or machine-learning models.
A.3 How we store and protect Google user data
| Data | What we store |
|---|---|
| Google sign-in | Your name, email address and Google account ID, in your Qshot account |
| Google Calendar connection | Your Google account email address and the access and refresh tokens, encrypted with AES-256-GCM |
| Calendar events | Only the start and end times of busy events. We never store event titles, descriptions, guests or locations |
This data is stored on our servers in Germany and is sent over encrypted connections (TLS). Access is limited to the systems that run the booking feature.
A.4 Who we share Google user data with
We do not share Google user data with third parties, except with the service providers that host our servers and only as needed to run the feature (section 10), where the law requires it, or as part of a merger or acquisition with notice to you. People at Qshot do not read your Google user data unless you give us permission, it is necessary for security purposes (for example investigating abuse), or the law requires it.
A.5 How long we keep Google user data and how to delete it
- Busy times are kept only for the coming 90 days and are replaced at each sync.
- Calendar connection and tokens are kept until you disconnect Google Calendar or delete your Qshot account. In both cases we revoke our access at Google and delete the stored tokens, your Google account email for that connection, and the busy times.
- Google sign-in data is kept for as long as your Qshot account exists and is deleted with it (section 13).
- Events that Qshot wrote to your calendar stay in your Google Calendar under your control until you delete them there.
You can disconnect at any time in your booking settings, remove Qshot's access at https://myaccount.google.com/permissions, or ask us to delete your data by writing to [email protected].
Note: the calendar.events permission technically allows access to events in all your calendars; Qshot only uses your primary calendar.
Annex B — Facebook and Instagram: how to delete your data
1. Disconnect in the Qshot app. In your profile editor's social feed block, choose Disconnect. We immediately delete the stored access tokens, Page and account details, and cached posts.
- For Facebook Pages we also ask Meta to revoke Qshot's permissions.
- For Instagram we also ask Instagram to revoke Qshot's access. You can in addition remove Qshot from the apps and websites connected to your account in Instagram's settings.
2. Remove Qshot in Facebook or Instagram settings. Facebook: Settings & privacy → Settings → Apps and websites → Qshot → Remove. When you do this, Meta notifies us and we delete the tokens, account details and cached content we hold from that connection.
3. Delete your Qshot account. All data from Facebook and Instagram is deleted together with your account, and we revoke our access at Meta and Instagram (section 13).
4. Email us. Write to [email protected] from your account's email address with the subject "Data Deletion Request". Tell us whether you want to delete a connected account or your whole Qshot account, and for Facebook data include the Page name. We complete the request within one month and confirm by email.
Technical log entries about the connection remain until the log period ends (up to 6 months, section 12).
Annex C — TikTok: how to delete your data
- Disconnect in the Qshot app. We ask TikTok to revoke our access and delete the stored tokens, account details and cached videos.
- Remove Qshot in TikTok: remove Qshot from the apps and services that have access to your account in TikTok's settings. When TikTok notifies us, we delete the connection.
- Delete your Qshot account — your TikTok data is deleted with it and we revoke our access at TikTok (section 13).
- Email us at [email protected] as described in Annex B.
Annex D — WhatsApp
If you message Qshot's WhatsApp number, see section 5.7. To have your messages deleted, write to [email protected] and include the phone number you wrote from.
20. Changes to this policy
We update this policy when the Service or the law changes. The date and version number at the top show the current version. If we make material changes, we tell you in the app or by email before they take effect, and where a change needs your consent we ask for it. Earlier versions are available on request. The current version is published at https://qshot.com/privacy, which our apps link to.
21. Contact
Qshot, Sweden (our postal address is in section 1) Email: [email protected]
We answer privacy questions and requests within one month (section 14).
You can also contact the Swedish Authority for Privacy Protection, Integritetsskyddsmyndigheten (IMY): Box 8114, 104 20 Stockholm, Sweden — www.imy.se.