Greetlead Privacy Policy
Version of 8 November 2026.
1. Controller
Quantum Liquid LLC, a company governed by the laws of Wyoming (Limited Liability Company), 30 N Gould St, Ste R, Sheridan, WY 82801, United States of America, operates the Greetlead service ("Greetlead" or "the Service"). Contact for any question relating to personal data: hello@greetlead.io.
This policy applies under the Swiss Federal Act on Data Protection (FADP) and, for persons located in the European Union or the EEA, under the General Data Protection Regulation (GDPR).
2. Data subjects
- Organisers, who create cards and sign in with their Lead account.
- Signers, who add a message without an account, and recipients of cards.
- Colleagues whose email address an organiser enters to invite them to sign a card.
- People entered in an organisation's People list (Pro plan).
- Visitors to greetlead.io.
3. Roles
Quantum Liquid LLC is the controller for organiser accounts and technical data. When a card is created at work, the organiser's organisation is the controller of the card content, of the invitation addresses and of the People list, and Greetlead is its processor, using these data only to run the card.
4. Data processed
4.1 Organisers
Greetlead manages no passwords. Sign-in takes place through the Lead account, managed in ERPlead, the identity service shared by the Lead apps (erplead.io). Greetlead stores the Lead account identifier, email address, name, language, organisation, role, plan and entitlements. For a Pro or Pro+ subscription taken in Greetlead, Greetlead stores the Stripe customer and subscription references, the plan, its status and its dates; card details stay with Stripe. Greetlead reports this subscription (plan, status, end of period) to ERPlead, which applies it to Greetlead and, once the subscription is paid, also uses it to unlock VisitLead and CashLead at the same level.
4.2 Cards
The occasion, the recipient's name, the recipient's email address (optional), the card title, the language and the delivery date.
4.3 Signatures
The signer's name, message and ink colour, a photo if one is added (stored in our database), the link to a GIF if one is chosen, and the signer's email address if they wish to receive the recipient's thank-you. A random key is placed in a cookie on the signer's device, so that only they can edit or remove their own message until delivery. Every uploaded photo (signer, cover, logo) is saved again without its metadata: the GPS location, the date it was taken and the device model are removed on upload, and the photo is reduced to the size the card needs.
A signer can add a video of up to one minute and 40 MB. The video is stored in Neon object storage and is delivered through temporary links valid for one hour. A signer can also mark their message as private: it is then shown only to the recipient and to its author; the organiser and the other signers only see that it exists and who wrote it.
A signer can also record a voice message of up to two minutes and 10 MB, stored and delivered in the same way as videos.
On request only, a signer can ask the writing assistant for suggestions. Greetlead then sends the AI provider the occasion, the recipient's first name, the language and, if the signer asks to improve their text, the draft they wrote. No account data, email address or other message is sent. The suggestions are not stored.
4.4 Invitations by email
The email addresses of colleagues that the organiser pastes. Greetlead uses them only for this card: one invitation to each person and, if they have not signed, at most one reminder, sent by the organiser or by Greetlead two days before delivery. Each invitation contains a link to stop receiving them. Each email says why the person receives it. The day before delivery, the organiser receives one reminder. These addresses are deleted with the card. Greetlead keeps only an irreversible fingerprint of the address (HMAC), for at most 400 days, to cap sending and to respect an opt-out or a bounce.
4.5 Gift collection register
When the organiser opens a register, signers can note how much they contributed to a common gift. An amount noted by a signer is visible only to the organiser, the card's co-organisers and the company's administrators. The other signers and other colleagues see the total only. Greetlead never receives, holds or transfers this money: payments are made directly between colleagues by the means the organiser indicates, and Greetlead is not a payment service.
4.5b Gift pot
When the organiser opens a gift pot, colleagues can contribute by card. Greetlead keeps the contributor's name, the amount, the fee and the Stripe payment reference, including that of any refund. The organiser, the card's co-organisers and the company's administrators see each name and amount; other colleagues see the total and the number of contributors, the recipient sees the total and the number of contributors. To receive the gift, the recipient confirms the request through a link sent to the card's email address. The pot is delivered to the recipient as a digital gift card by a gift card provider: Greetlead sends this provider the recipient's email address, first name and the amount, and nothing else. The recipient gets an email to choose the gift card as soon as it is ready.
4.6 People list (Pro)
Names, an optional email address, the birthday as day and month only (never the year) and the start date at work. These data are used to remind the organisation's members 7 days before the date.
If the organisation switches on automatic cards, Greetlead also uses these data to create the card ten days before the date and to invite the other people on the list to sign.
4.6b Slack and Teams
If the organisation enters a Slack or Teams incoming webhook address, Greetlead keeps it and posts there the title of new cards, reminders and deliveries, with the recipient's name as entered by the organiser and the signing link.
4.6c Reactions
The recipient can add a heart or a short reply to each message. They are stored with the card and deleted with it.
4.7 Technical data
To limit abuse, Greetlead keeps a hashed (HMAC) network identifier for at most two hours. The IP address itself is never stored. Greetlead uses no analytics and no advertising cookies.
5. Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Providing the Service and payment of cards and subscriptions | Performance of a contract (GDPR art. 6(1)(b)) |
| Limiting abuse | Legitimate interest (art. 6(1)(f)) |
| Gift pot contributions and their delivery as a gift card | Performance of a contract (art. 6(1)(b)); keeping accounting records (art. 6(1)(c)) |
| Invitations and reminders to colleagues whose address the organiser entered | Legitimate interest of the organiser's organisation in a workplace celebration (art. 6(1)(f)) |
| Card content and People list handled for an organisation | Processing on behalf (art. 28 GDPR, art. 9 FADP) |
6. Retention periods
- A delivered card and its photos, videos and voice messages are deleted automatically 12 months after delivery, unless the recipient chose to keep the card. A card whose paid gift pot has not yet been delivered to the recipient is kept until that delivery.
- A card that was never sent (draft, scheduled card that did not go out) is deleted with its messages, photos, videos and voice messages no earlier than 12 months after its last activity (change, message or invitation), unless its sending date is still ahead, it was paid for or its gift pot received a payment. The person who created it is warned by email 30 days before, and deletion never happens less than 30 days after that notice.
- The organiser can delete a card at any time, except while its gift pot holds money, and can remove a message until the card is sent. After sending, removing a message is requested at the address in section 9.
- Invitation addresses and co-organisers: deleted with the card.
- Gift pot contributions and gift card deliveries: kept 10 years for accounting obligations, without the card content, then deleted.
- Network identifier: two hours at most. Sessions: 12 hours. Cookies: see section 10.
- Account data: while the Service is used. When a person no longer has access to any organisation in Greetlead (removed by an administrator, account disabled or removed in ERPlead), their account (name, email address, language, sessions) is deleted automatically 30 days later; if they were removed by an administrator, only the identifier of their Lead account is kept, without name or address, so that they cannot rejoin that organisation on their own. An organisation with no members left is deleted automatically 30 days later, with its cards, its list of people and its reminders, except while a Greetlead subscription is running, a lifetime licence exists or a paid gift pot is waiting to be delivered; gift pot contributions and deliveries follow the period above. On request, deletion happens sooner, within 30 days.
7. Processors
| Processor | Role |
|---|---|
| Vercel Inc. | Hosting, Frankfurt region (Germany) |
| Neon (Databricks, Inc.) | Database, AWS eu-central-1 (Frankfurt) |
| Neon (Databricks, Inc.) | Object storage for videos, AWS eu-central-1 (Frankfurt) |
| Resend | Emails |
| Stripe Payments Europe | Payments |
| GIPHY | GIF search and display |
| Anthropic (Claude) | Writing suggestions, only when a signer asks for them |
| Gift card provider | Delivery of the gift pot as a gift card: receives the recipient's email address and first name, and the amount |
| Slack, Microsoft | Posts in the channels the organisation chose |
Greetlead never sees card numbers. GIPHY is used only when a signer uses GIFs: Greetlead keeps the link, and the GIF is loaded from GIPHY when the card is displayed.
8. Transfers abroad
Account and card data are hosted in Frankfurt (European Union). Quantum Liquid LLC is established in the United States, and some processors may handle data outside Switzerland and the EU/EEA. Such transfers rely on the safeguards of the FADP and the GDPR, such as standard contractual clauses.
9. Rights of data subjects
Any person may request access to their data, rectification, erasure, restriction of processing and data portability, and may object to processing based on legitimate interest. Requests should be sent to hello@greetlead.io. For card content, the organiser can also remove a message directly until the card is sent, or delete the card.
A complaint may be lodged with the Federal Data Protection and Information Commissioner (FDPIC, www.edoeb.admin.ch) or with the supervisory authority of the place of residence in the European Union.
10. Cookies
Greetlead uses only cookies the Service needs:
| Cookie | Purpose | Duration |
|---|---|---|
| __Host-gl_session | Organiser session | 12 hours |
| gl_in | Shows that a session is open (no data) | 12 hours |
| gl_lead_login_… | Sign-in request to the Lead account | 3 hours, 12 hours for its confirmation |
| __Host-gl_lead_bind | Ties the sign-in request to this browser (security) | 3 hours |
| lead_probe | Prevents a sign-in loop | 10 minutes |
| gl_s_… | Keys of the messages signed from this browser, to edit or remove the latest one for 30 minutes | Until one week after the planned sending date (at least 30 days, at most one year; 180 days without a date) |
| gl_sid | Random signer identifier, for sending limits | 30 days |
| NEXT_LOCALE, gl_lc | Language preference | 1 year |
| gl_cur | Currency chosen on the pricing page | 1 year |
11. Changes
Material changes are announced on the website and, for organisers, by email or in the application before they take effect.