Privacy Policy
Last updated: 14 October 2026
This Privacy Policy explains how helloswap, CVR no. DK29075794, Halmtorvet 28, 4th, 1700 København V, Denmark ("helloswap," "we," "us") collects, uses, discloses, and protects personal data in connection with the helloswap workforce-scheduling platform (the "Service"). It applies to visitors of our website, account holders, and the people whose work schedules are managed through a customer's account. It should be read together with our Terms of Service, which also covers some of the same ground from a contractual rather than a data-protection angle — where the two differ on a factual point, this Policy is the more current and more detailed statement of our actual practices.
1. Who We Are
helloswap is a workforce-scheduling platform for shift-based teams — a schedule builder, shift swaps, time-off requests, an open-shift board, and related features, sold to companies ("Customers") who use it to organize their own employees' work. We are a Danish company, and Danish and EU data protection law (including the GDPR) apply to how we handle personal data.
2. Scope of This Policy
This Policy covers personal data we handle in three overlapping roles:
- As a website operator — visitors to our public marketing pages, blog, and signup flow, before any account exists.
- As a service provider to account holders — the company admin, managers, and employees who actually sign in and use the Service, and the billing contact for a paid account.
- As a data processor for Customer Data — the schedules, contact details, and other workforce records a Customer inputs about their own employees. See Section 6 for how responsibility splits between us and the Customer for this category specifically.
3. Information We Collect
- Account & contact information: name, email address, phone number (optional), password (stored as a salted hash, never in plain text), company name, and company logo. If you sign in with Google or your company's own identity provider instead of a password, we receive your name and email address from that provider instead — see Section 8.
- Workforce data Customers input: shift schedules and patterns, swap and open-shift requests, time-off requests and approvals, department structure, employee roles, availability, and profile photos.
- Billing information: plan, billing interval, and payment status. Full card details are collected and processed directly by Stripe — we never see or store them.
- Usage & log data: sign-in activity, actions taken in the app (retained in the in-product audit log), IP address, browser and device type, and pages visited.
- Communications: support requests, and replies to emails we send you (for example, replying to an invite or notification email).
- Website analytics: aggregate page-view and usage data collected via Vercel Analytics — see Section 9.
4. How We Use Information
- provide, maintain, and secure the Service, including authenticating sign-ins and enforcing account permissions;
- send transactional communications — invites, password resets, shift reminders, swap and approval notifications, billing receipts, and service updates;
- process payments and manage subscriptions;
- provide customer support and respond to inquiries;
- monitor, debug, and improve the Service's reliability and performance;
- detect, prevent, and investigate fraud, abuse, or security incidents;
- measure and improve our own marketing (for example, understanding which pages lead to a signup); and
- comply with legal obligations.
We do not sell personal data, and we do not use Customer Data (employees' schedules, contact details, or other workforce records) to train AI models or share it with third parties for their own marketing purposes.
5. Legal Bases for Processing
Where GDPR applies, we rely on the following legal bases:
- Contract (Art. 6(1)(b)) — for account-holder and billing information, and to deliver the transactional notifications the Service exists to send.
- Legitimate interests (Art. 6(1)(f)) — for security logging, fraud prevention, and measuring our own marketing, balanced against your rights and interests.
- Legal obligation (Art. 6(1)(c)) — for billing records we're required to keep for tax and accounting purposes.
- Consent (Art. 6(1)(a)) — where we ask for it specifically, such as before setting non-essential cookies (see Section 9).
For Customer Data about a Customer's own employees, the Customer is responsible for having its own lawful basis (typically contract or legitimate interest in the employment relationship) — see Section 6.
6. Data Controller & Processor Roles
For the personal data of a Customer's own employees (names, contact details, schedules, and similar), the Customer is the data controller and helloswap is the data processor, acting only on the Customer's instructions as expressed through use of the Service's features. The Customer is responsible for having a lawful basis to collect and share its employees' personal data with us, and for telling its employees that their schedule data is processed through helloswap.
If you're an employee whose schedule is managed through helloswap and you have a question about how your data is used, please contact your employer first — they control that data and are best placed to answer. We'll support them in responding to you.
For account-holder and billing information a Customer provides directly about itself, helloswap is the data controller. A separate Data Processing Agreement is available on request for Customers that require one under GDPR or similar frameworks — contact hello@helloswap.io.
7. Sub-Processors & Third-Party Services
We use the following categories of sub-processors to provide the Service. We may update this list as our infrastructure evolves.
- Stripe — payment processing and billing.
- Resend — transactional email delivery (invites, notifications, receipts).
- Vercel — application hosting, content delivery, and website analytics.
- Neon — database hosting.
- Google — identity verification, if you choose to sign in with a Google account instead of a password (see Section 8), and Google Ads conversion measurement, only if you accept it (see Section 9).
- AskMint — the support chat on our public website (computers and tablets). It processes the messages you choose to type into it so it can answer them.
- Anthropic — used only to generate editorial content for our public blog; not used to process Customer Data or any personal data about you or your employees.
Some of these providers are located outside the European Economic Area — see Section 10 for the safeguards that applies to those transfers.
8. Signing In With Google or Your Company's Identity Provider
Instead of a password, you can sign in with a Google account. When you do, Google shares your name, email address, and confirmation that Google has verified you own that email address — nothing else. We use it only to match you to an existing helloswap account, or, if signing up, to create one. We never receive or store your Google password, and we don't use this to access anything else in your Google account.
Separately, on our Enterprise plan, a Customer can configure single sign-on so its own employees sign in through the Customer's own identity provider (for example, Okta, Microsoft Entra ID, or Google Workspace) instead of a helloswap password. In that setup, the identity provider is chosen and configured by the Customer, not by us — the Customer is the controller of that relationship, and we simply verify the identity assertion it sends us to complete sign-in, the same way we'd verify a password.
9. Cookies & Similar Technologies
- Strictly necessary cookies keep you signed in and remember your language and display preferences — the Service doesn't function without these, and they're not used for tracking.
- Website analytics (Vercel Analytics) measures overall usage. It's designed to work without setting a cookie or persistently identifying your device.
- Advertising conversion tracking (Google Ads' gtag.js) helps us measure whether ad campaigns lead to signups, and sets a cookie for that purpose. It loads on our public pages and in the administrative areas of the signed-in app, but never in the employee experience. It only loads at all once consent has been given.
- Support chat (AskMint) is available on our public pages on computers and tablets. Anything you type into it is sent to AskMint so it can answer your question.
The Google Ads cookie is the only advertising cookie we use, and only to count whether someone who clicked one of our ads went on to sign up. We've turned off Google's ad personalization for it, so we don't use it to build remarketing lists or to show you targeted ads, and we never sell your data. Google processes this data under its own privacy policy, and may do so outside the European Economic Area (see Section 10). Where your consent is legally required for a category above, we'll ask for it before setting that cookie. You can change or withdraw your choice at any time with the "Cookie settings" link at the bottom of every public page — withdrawing removes the advertising cookie again.
10. International Data Transfers
Some of our sub-processors (Section 7) are located outside the European Economic Area, including in the United States. Where that's the case, we rely on appropriate safeguards recognized under GDPR — such as Standard Contractual Clauses, or the provider's own certification under an approved transfer framework — before personal data leaves the EEA.
11. Data Security
We use industry-standard measures to protect personal data, including encryption in transit, database row-level access controls scoped per company (so one Customer's data is never visible to another), hashed passwords, and an append-only audit log of account activity. No method of transmission or storage is completely secure, and we can't guarantee absolute security.
If a personal data breach affecting your personal data occurs, we will notify the competent supervisory authority without undue delay, and — where the breach is likely to result in a high risk to your rights and freedoms — the affected individuals or the relevant Customer, consistent with GDPR Articles 33 and 34.
12. Data Retention & Deletion
We retain personal data for as long as the relevant account is active. When a Customer closes its account, we schedule the underlying company and workforce records for permanent erasure 30 days later — a short window that exists only to recover from an accidental deletion, not to keep data longer than needed. When a Customer's subscription ends without the account being closed — it is cancelled, or a trial or an invoice is never paid — and the account is not taken up again, the same records are erased 60 days after the subscription ended. Once erased, the records cannot be brought back; what remains is a minimal billing history we keep on file where we're legally required to (for example, for tax and accounting purposes), and an append-only audit trail of account-level actions that, by design, can never be altered or deleted once written.
13. Your Rights
Under GDPR and similar laws, you may have the right to:
- access the personal data we hold about you, and get a copy of it;
- correct inaccurate or incomplete data;
- ask us to erase your data, subject to our legal obligations to retain some records;
- restrict or object to certain processing, including processing based on legitimate interests;
- receive your data in a portable format, where technically feasible; and
- lodge a complaint with a supervisory authority — in Denmark, the Datatilsynet (datatilsynet.dk).
If your employer manages your schedule through helloswap, they're the controller for that data (see Section 6) — please contact them first for requests about your own workforce records. For anything else, or if your employer is unresponsive, contact us at hello@helloswap.io and we'll help.
14. Children's Privacy
The Service is intended for business and employment use and isn't directed at children. We don't knowingly collect personal data from children. If you believe a child's data has been provided to us, contact us and we'll delete it.
15. Changes to This Policy
We may update this Policy from time to time. For material changes, we'll give reasonable notice (for example, by email or an in-app notice) before they take effect. The "Last updated" date at the top of this page always reflects the current version.
16. Contact Us
Questions about this Policy, or a request under Section 13?
helloswap, CVR no. DK29075794
Halmtorvet 28, 4th, 1700 København V, Denmark
hello@helloswap.io