Full privacy policy

Gift Huddle privacy policy

Last updated: 2026-11-16

This is a translation of the Spanish policy. If the two differ, the Spanish version prevails.

Gift Huddle is a mobile app (Android and iPhone) where a family notes who gives what to each person at Christmas, Three Kings' Day, birthdays and other occasions, so that nobody doubles up and nobody is left out. It also has a web version for using it from a computer that you have connected to your phone.

Summary

  • You have no account, there are no ads, and the app uses no analytics or crash reporting.
  • Your list is stored encrypted on your phone. While it is only on your phone, the app does not connect to any server.
  • The list only leaves the phone, always encrypted, if you ask for it: when you connect another phone or the web, create a recovery code or send a copy in a file.
  • The sync server cannot read the list: it does not see names, gifts, prices or notes. It does see what it needs to work: the IP address of each connection, when each phone connects, how many phones and web apps the family has and the size of the encrypted copy. It keeps the data in data centres in the European Union.
  • The 24 words of the recovery code are like a house key: whoever has them can get into your list as your phone. Keep them somewhere safe and do not share them.
  • You can stop syncing this phone whenever you like. The copy on the server is deleted once no other phone or web app has access, or after 400 days without use (see "How long it is kept and how it is deleted").

Everything is explained in detail below.

1. Data controller

  • Owner: Daniel Mont Ferrandiz (DanielMF), Spain
  • Contact email: gifthuddle@gifthuddle.app

2. What data is processed

What is stored on your phone

What you enter in the app is stored on your phone. If you sync, we also receive an encrypted copy that we cannot read (see "Sync between the family's phones").

  • People who receive gifts: name, colour, relation to the family and, if you want, the birthday (day, month and, if you enter it, year).

  • Who gives: a free name ("Us", "Grandparents"…), colour and whether the household pays.

  • Occasions: type, name, date and whether it repeats every year.

  • Gifts: title, who it is for, who gives it, occasion, status, planned price and actual price, shop, link, note, size, who asked for it, whether it is a surprise, and the year.

  • Technical data: the name of this phone (the app suggests the model, for example "Pixel 10 Pro", and you can change it), whose phone this is if you have chosen it (Settings → "This phone belongs to"), random identifiers for the list and for this phone, the list of the family's phones, the encryption keys, the credential this phone uses to identify itself to the server and, if you have created one, your recovery code.

    If you sync, the name you have given this phone also goes in the encrypted copy of the list, so the family's other phones and the web app know which one it is; the server cannot read it. When you remove a phone, its name is deleted from that copy; if a phone leaves on its own, it is deleted when another phone in the family completes its removal. An empty deletion mark stays in its place. If there is no shared phone name and no person assigned, "Another phone" is shown.

All of the above is stored encrypted (AES-256-GCM) in the app's private space. The keys that encrypt it, the family key, this phone's keys, the PIN digest and the lock settings are kept in the system's secure storage (Android Keystore or iOS Keychain, on this device only).

Outside that encryption, the app preferences hold only the language, the appearance (accent colour, light or dark theme, occasion themes and vibration), the view you last used on the "Who gives what" screen, whether you have seen the welcome guide, and some technical sync values that contain nothing from the list: random identifiers of the list or of an invitation, its expiry, and status markers (for example, whether you have turned sync off, or whether the copy of an invitation that was not completed still has to be deleted from the server).

The links you note on a gift are stored as text: the app does not open or fetch them. The app does not store photos, does not access your gallery and does not send notifications.

When you delete a gift or a person, its content (name, notes, prices, links) is emptied. An empty "deleted" marker remains so that the deletion also reaches the family's other phones that keep syncing.

Lock with PIN, fingerprint or face

When you start, the app asks you to create a PIN of 4 to 6 digits so that nobody sees the gifts if they pick up your phone. You can leave it for later ("Not now") or remove it in Settings → Lock; without a PIN, anyone who picks up the unlocked phone can see the list. With the PIN on, the app locks when it is opened and after more than 30 seconds in the background, and it covers its content when you leave it so that it does not show in the app switcher (on Android 12 and earlier that protection may not be complete).

The PIN itself is not stored: a digest computed with PBKDF2-HMAC-SHA256 (200,000 iterations and a random salt) is kept in the system's secure storage. After five wrong attempts in a row you have to wait 30 seconds, and the wait doubles with each further failure, up to one hour. The PIN prevents the app from being opened; the encryption of the data does not depend on it, but on the key in the secure storage.

If you turn on fingerprint or face, the check is done by the phone's system. The app only learns whether it succeeded: it never sees or stores your fingerprint or your face. Any fingerprint or face enrolled on the phone will be able to open the app.

Screenshots

On Android, while the words or the QR code of the recovery code are shown or typed, the app blocks screenshots and screen recordings. In the version published in the stores, it blocks them throughout the app on Android. On iPhone the system does not allow blocking them: the app warns you not to take screenshots and hides the words when you leave it.

System backups

On Android, the system backup is disabled for this app: none of its files go into the cloud backup or the transfer to another phone. On iPhone, the app's encrypted data is excluded from the device and iCloud backup, and the Keychain keys do not leave that iPhone; only the preferences described above may go into the backup you manage with your Apple account. That is why the list does not travel on its own when you change phones: you get it back by connecting the new phone with another one in the family or with your recovery code.

Sync between the family's phones

Sync keeps the same list on all of the family's phones and on the web. At first the list is only on your phone: the app sends nothing to the server and does not connect to it. The connection with the server starts when:

  • you prepare an invitation to connect another phone (with the QR code or a link; see "Connecting another phone");
  • you connect the web on a computer (see "The web version");
  • you create a recovery code, even if you only have this phone (see "Recovery code").

To connect another phone or the web, your phone first creates an invitation on the server and, if the list was only on your phone, uploads an encrypted copy of it. If nobody joins (you cancel the invitation, the codes do not match, it fails or it expires), your phone deletes that copy from the server; if there is no connection at that moment, it tries again when you open the app or return to it. Even if you never open the app again, the server deletes that copy on its own if nobody has joined: 24 hours after the last invitation you created for it and, at the latest, 7 days after the copy was created (copies created with earlier test versions of the app follow the general 400-day period without use).

What travels. When there are changes, your phone compresses the list, encrypts it (AES-256-GCM), signs it and uploads it over HTTPS to the sync server, a service of our own hosted on Cloudflare (Cloudflare Workers), at sync.gifthuddle.app. The other phones download it, check the signature, decrypt it and merge the changes. While the app is open, each phone also keeps a connection to the server so that it learns right away that there is a new copy; only notices come through it, with no list data. The keys that open the list only pass from one device to another encrypted for that specific device (when connecting it, or inside the recovery code's capsule), and the server can never use them. The server does not decrypt or merge anything.

How each phone identifies itself. Each phone (and each connected web app) has its own service credential: a random value that is not derived from the family's keys and only lets the server allow it to read and write the copy. The server does not store the credential: it stores only its digest (SHA-256). The request's authorisation header and cookies do not reach the list's storage.

What the server stores for each list:

  • the main encrypted copy of the list, without the secret gifts; each upload replaces the previous one. While a new device is being connected, an encrypted copy of the approved list may also be kept (see "Connecting another phone");
  • if you use "Secret gifts", one encrypted block for each protected person and each phone that writes their gifts; all blocks have the same size, so they do not reveal how many gifts there are;
  • the register of the family's phones, signed but not encrypted: for each phone, its random identifier, its public keys, whether it is a web app, the random identifier of the family member it belongs to (if one has been chosen) and, if it was removed, the marker that it no longer has access. It contains no names of phones or people;
  • key packages, each one encrypted for a specific phone in the family;
  • for each phone: the digest of its credential, which phone gave it access, whether it is a phone or a web app, the approximate time of its last request (rounded to the hour), whether it has been removed, and timestamps used to apply the daily quotas;
  • a random sync identifier, the version number of the copy, the approximate time the list was last used (rounded to the hour) and request counters per phone and per minute, which are deleted when each minute ends;
  • while there are any, the open invitations and their checkpoints (see "Connecting another phone");
  • if you have created a recovery code, its encrypted capsule and the data needed to find it (see "Recovery code");
  • if a web app is connected, the piece of its key that the server keeps (see "The web version");
  • while a phone has the app open, the time it opened its connection to the server, its identifier and the digest of its credential, which are discarded when the connection closes.

What the server can and cannot see. It does not see names, gifts, prices, notes, links or birthdays, nor the family's keys, nor your PIN, nor your recovery code. It does see, because this is unavoidable to provide the service:

  • the size of the encrypted copy and the times at which each phone connects, uploads or downloads;
  • a small unencrypted technical header that comes with the copy: random identifiers of the list and of the phone that wrote it, version numbers and the numbers of the keys used, and a signature;
  • the register of phones described above: how many phones and web apps there are, which one gave access to which, which person (by their random identifier) each one belongs to and, from the "Secret gifts" blocks, how many protected people there are (also by their random identifier);
  • the IP address of each connection, which reaches Cloudflare as with any internet connection.

What the IP address is used for. Only to limit abuse: the server counts requests per address (the IPv4 address, or the /56 prefix for IPv6) with limits such as these: 200 requests a minute in general, 120 a minute for invitations, 12 new lists an hour, 30 recovery code lookups a minute and 30 attempts a minute to unlock a web app. The first two are applied by Cloudflare over a one-minute period; the others are our own counters that delete themselves at the end of their period (one minute or one hour). The IP address is not stored with the list, and our service keeps no request logs: its logs are turned off. Cloudflare processes the IP address and the technical data of each connection in two ways: as a processor, to provide the service to us; and on its own account, for the operation and security of its network, producing aggregated statistics and security records (for example, firewall events) that may include the IP address and the requested address. The latter is governed by Cloudflare's privacy policy (https://www.cloudflare.com/privacypolicy/), which sets no specific period for those data.

How long it is kept and how it is deleted. The encrypted copy stays on the server for as long as the list exists there. Operations that delete something from the server need a connection and only complete when the server confirms them. It is deleted as follows:

  • "Stop syncing" (Settings → Family phones → More options): this phone leaves the family's sync. The server stops accepting its credential and deletes its invitations and its recovery code, and the register keeps the marker that this phone no longer has access. If other phones or a web app still have access, they keep syncing among themselves and the list stays on the server; the secret gift blocks this phone had written are deleted after 30 days (see the next point). If nobody else is left, the whole list is deleted from the server. What is on each device stays as it is, and on this phone the list is only on it again: to sync again it has to be connected again.
  • "Delete everything" (in Settings): does the same on the server and also deletes from this phone the whole list, the PIN, the settings and the keys, and the app starts again from scratch. It asks you to confirm first, and it cannot be undone. If the server cannot be reached, you can choose "Delete this phone only": then what is on the server stays as it was. The family's other phones keep their copy.
  • Removing a phone or a web app from another phone ("Remove this phone" or "Remove this web app", in Family phones): the server stops accepting its credential as soon as the request reaches it (if there is no connection, when there is one) and deletes its invitations, its recovery code and, if it is a web app, its piece of key. The encrypted secret gift blocks that phone had written are deleted 30 days after its access is withdrawn. That margin only lets the other phones collect anything they had not received yet while they have not acknowledged the signed removal of that phone; it does not guarantee that pending gifts are recovered. What that device had already stored cannot be deleted remotely.
  • Being left as the only device with access: if the other phones and the web app have left or you have removed them, and you have no active recovery code, the app deletes the list from the server and the list is only on your phone again. It does so when there is a connection and nothing is pending (for example, an open invitation or an unconfirmed removal). It does not do so while this phone has secret gifts on hold (the app shows "Surprises on hold") or secret gift blocks it has not been able to read, because the copy on the server may be the only one that keeps them: the list then stays on the server until you use "Stop syncing" or "Delete everything", or until the 400-day expiry without use.
  • Removing the recovery code when no other phone or web app is connected: the list is also deleted from the server and is only on your phone again (see "Recovery code").
  • Invitation that ends with nobody: the copy uploaded to create it is deleted, as explained at the start of this section.
  • Expiry: if for 400 days the list is not used from any of its devices (phones or web), the server deletes it automatically, with everything it holds about it.

When a whole list is deleted, the server keeps for 400 days a minimal marker, with no content or device identifiers, that prevents a list from being created again with that same random identifier; after that it deletes itself. The same applies to the lookup identifier of each retired recovery code (see "Recovery code"). Markers, lookup identifiers and blocks of withdrawn phones that already existed before 16 November 2026 (only from test versions) count their 400-day and 30-day periods from that date.

Connecting another phone

From Settings → Family phones → "Connect another phone":

  • "It is here": your phone shows a QR code and the other one reads it with the camera ("Scan the QR code").
  • "It is far away": your phone gives you an invitation link (https://gifthuddle.app/i#…) to share through the app you choose. If tapping it does not open Gift Huddle, the other person pastes it into their app ("Join with a link" or "Paste an invitation link").

Neither the QR code nor the link carries any key: only the identifier of an invitation. In the link it goes after #, so the browser does not send it to the gifthuddle.app website. The invitation expires after 24 hours and works for one phone only.

Then both phones show the same 6-digit code, calculated from what each one has sent. You compare it (in person, by phone or by message) and only if it matches do you give access ("They match"), choosing whose phone it is. Your phone then leaves on the server, encrypted for that specific phone, the keys it needs, and a checkpoint with an encrypted copy of the list and of the register that you approved, so that the other phone can check that it receives exactly that.

While it lasts, the server stores about the invitation: its identifier, the list it belongs to, the expiry, the phone that created it, the public keys and the signed record of both phones, the digest of the new phone's credential, the proposed person (by their random identifier) and the encrypted package. When the new phone confirms that it has been set up, the server deletes the invitation, the package and the checkpoint (if that confirmation is interrupted, the new phone repeats it). If it is never confirmed, everything is deleted when it is cancelled, if either phone is removed or when it expires; at the latest, after 24 hours. A small index that lets the invitation be found by its identifier is also deleted when it expires.

The camera image is analysed on the phone itself to read the code and is neither stored nor sent. The reader is built into the app, works offline and uses no Google or other third-party services: on Android it is the open-source ZXing library and on iPhone, the system's own code reader.

Secret gifts

On a person's card you can turn on "Secret gifts". With it on, the phone that belongs to that person (the one that has that person chosen in "This phone belongs to") receives none of the gifts for them, nor how many there are; the rest of the family still sees them. Those gifts travel in separate blocks, encrypted with a key of that person's own that their phone never receives. The web app does not open them either. Gifts that their phone already received before you turned it on cannot be withdrawn from it. This protection depends on each phone being assigned to the right person.

Recovery code

In Settings → "Recovery code" you can create a code to get the list back if you lose your phone or change it for another one ("Create recovery code"). This is how it works:

  • The code is 24 words (from the standard BIP-39 list, in English) that come from a random value generated on your phone. While you create it, the app shows them so that you can write them down and check them; it can also show them as a QR code ("Show QR code"). If you have the app lock turned on, it first asks for your PIN or your fingerprint or face; without a lock, this step asks for nothing. Once you finish, they cannot be shown again. The words never reach the server and we do not have them. Your phone keeps them encrypted so that it can keep the recovery copy up to date.
  • The capsule. With the words, your phone encrypts a capsule (the key is derived from the words with Argon2id and a new random salt each time; it is encrypted with AES-256-GCM) and stores it on the server next to the copy of the list. Inside are the family's and this phone's keys, its service credential, the register of phones, the name of this phone and of the phone it connected with, the person it belongs to and technical data to continue syncing. It does not contain the list: the list is downloaded afterwards from the encrypted copy on the server. The server cannot decrypt the capsule: it only sees a technical header (identifier, revision number, salt and encryption parameters) and its size.
  • Lookup identifier and verifier. One-way functions (HKDF and SHA-256) also derive from the words an identifier to find the capsule and a read key. The server stores the identifier and only a digest of the read key; neither of them allows the words to be obtained.
  • If you only have this phone, creating the code turns on sync with the server: the encrypted copy of the list is uploaded and kept up to date, because that is the copy you get back if you lose the phone.
  • Getting the list back. On a new phone, "I have a recovery code" or "Get the list back" ask for the 24 words (or read their QR code). The new phone downloads and opens the capsule, asks the server for a new credential and downloads the list. It joins with the permissions of the phone that created the code, without comparing a 6-digit code or needing another phone's approval: it sees the same as that phone saw, and it does not recover what was never synced.
  • The previous phone. Its credential stops working. When it finds out, it shows "This list has moved to another phone" and stays in "Read only": it keeps its copy, but no longer sends or receives changes. From there you can delete everything from that phone.
  • Whoever has the words can join as that phone, even after they have been used, for as long as the code is active. Keep them somewhere safe, do not take screenshots and do not send them by message.
  • If someone may have seen the words, change the code or remove it: those words then no longer let anyone in. But that does not remove anyone who has already joined with them, nor delete what they took. If you think someone used them, also remove that phone from the family from another phone you trust ("Remove this phone") and connect it again.
  • Changing the code ("Change the code"): the phone creates new words and a new capsule; the previous one is deleted once the new one is ready, and the previous words stop working.
  • Removing the code ("Remove the code"): the capsule is deleted from the server and the 24 words stop working. If another phone or a web app is connected, the encrypted copy of the list stays on the server for them; if you are later left as the only device with access, the app deletes it (see "How long it is kept and how it is deleted"). If there is none, the encrypted copy of the list is also deleted and the list is only on your phone again; the app warns you before you confirm.
  • How long it is kept. The capsule is kept for as long as the code is active and the list exists on the server. It is deleted when you change or remove the code, when that phone is removed from the family (also with "Stop syncing" or "Delete everything") and when the list is deleted, including by the 400-day expiry without use. For a code that has been removed or changed, while the list exists the server keeps only control data with no content (its lookup identifier, the digest of its read key, the identifier of the phone that created it, dates, revision number and digests of replaced credentials), so as not to accept it again. When the code or the list is retired, the lookup identifier is marked as retired for 400 days, with no other data, and is then deleted.
  • This feature does not exist on the web.

The web version

From a computer you can open web.gifthuddle.app and connect it once with your phone (Family phones → "Connect the web"): the computer shows a QR code, your phone reads it, you compare a 6-digit code and choose whose computer it is. In the list of phones it appears as "Web for" followed by that person's name.

  • What the browser stores. The browser's storage (IndexedDB) holds an encrypted box (AES-256-GCM) with what is needed to get back in: the keys, that web app's credential, the register of phones, the latest copy of the list and any changes not yet uploaded. Outside the box there are only technical data with no list content (random identifiers and encryption parameters) and, in the browser's local storage, the language, the appearance, the "Who gives what" view and whether you have seen the guide. The web app sets no cookies.
  • The web PIN. The box is opened with a PIN of at least 6 digits, or a passphrase of at least 8 characters, that you choose when connecting it. The box's key is derived from that PIN (PBKDF2 with 600,000 iterations) and from a random piece kept by the server. The server only hands over that piece when the browser proves it knows the PIN, without receiving the PIN. It allows one attempt every 2 seconds and, after 10 failures, stops handing it over until you allow it from a phone ("Allow unlocking again"). This way, anyone who copies the browser's data cannot open it without the PIN. The web PIN cannot be recovered.
  • While you use it, the open list is only in the page's memory. The web app locks after 15 minutes without use or 5 minutes in the background, and when you close it.
  • What it can do. View and edit the list, the people and the occasions. It cannot manage phones, invite, export, make copies or use the recovery code, and it never opens secret gifts.
  • Forgetting it. On the web, "Forget this computer" takes it out of the family (the server stops accepting its credential and deletes its piece of key) and empties the browser's box; if it is no longer connected, "Erase this computer's data" empties the box. The language and appearance preferences stay until you clear the site's data in the browser. From a phone, "Remove this web app" withdraws its access, but what it already had cannot be deleted remotely.
  • No third parties. The web app loads nothing from elsewhere: the engine, the fonts and the other resources are served from web.gifthuddle.app. It uses no analytics.

Backup to a file

In Settings → Backup, "Save a copy" creates a .gifthuddle file with the list, encrypted with the family's keys, and hands it to the app you choose in the system share menu: it only goes where you send it. The file carries no key that anyone other than a phone already in your family could use, so only those phones can open it, and it does not carry the secret gifts. It carries, unencrypted, random identifiers and the public records of the phones needed to check it. An encrypted copy stays in the app's temporary folder until the system clears it or you use "Delete everything". "Restore a copy" → "Paste from the clipboard" reads the clipboard only when you tap it. The app can also open a .gifthuddle file that reaches you through another app.

Permissions

  • Camera: only to read a QR code: that of another phone or of the web when connecting them, and that of the recovery code. It is requested at that moment.
  • Fingerprint or face (on Android, USE_BIOMETRIC and USE_FINGERPRINT; on iPhone, Face ID): only if you turn on biometric unlock.
  • Internet (INTERNET): for sync, invitations and the recovery code.

The app does not ask for location, contacts, calendar, microphone, notifications or access to your photos or files, and it does not use the advertising identifier. To open or share a .gifthuddle file it uses the system menu, which needs no permissions.

Data that is NOT processed

  • We do not ask for your name, email, phone number or age to use the app: there are no accounts. (If you write to us, we receive your email; see "If you write to us".)
  • The app uses no analytics or crash reporting (no Crashlytics either), and there are no ads, personalised advertising or cross-app tracking.
  • We cannot read your list: not the names, the gifts, the prices or the notes.
  • The app connects only to the sync server (sync.gifthuddle.app), and only in the cases described above: while the list is only on your phone, it makes no connection at all. The links in "About Gift Huddle" ("Privacy policy" and "Help and support") open in your browser or your email app.

Gift Huddle's websites

The public website (gifthuddle.app, which hosts this policy and the page for invitation links) and the web version (web.gifthuddle.app) are served by Cloudflare. They use no analytics and set no cookies. As with any website, Cloudflare receives the IP address and the technical data of the connection to deliver the page.

For a while the previous addresses of the web version (gifthuddle-app.mainshai.com) and of the server (gifthuddle-sync.mainshai.com) also keep working, with the same service. On them, Cloudflare's bot protection may set technical security cookies (for example __cf_bm, which lasts 30 minutes, or cf_clearance), which only serve to tell people apart from automated programs; they are not used for advertising or to track you.

Earlier versions

Earlier test versions of the app used another sync system, which was not restricted to the European Union. That system has been retired and the data it kept on the server has been deleted.

If you write to us

You can write to us at gifthuddle@gifthuddle.app. We will process your email address and what you tell us only to reply to you, and we will keep those emails for one year from the last reply; after that we delete them. Emails reach the owner's mailbox, hosted by Proton AG (Switzerland) under Proton's terms of service, through Cloudflare's email forwarding service. Cloudflare and Proton process the address, the content and the technical data of the message to deliver and store it. Please do not send us your 24 words, screenshots of the QR codes or real data about your family: for a bug, test data is enough. We will never ask for your words, your PIN or your keys.

If you do not give us data

You are not obliged to give us any data. You can use the app on your phone alone, with no connection at all; the only things that stop working without the server are sync with other phones and the web, and the recovery code.

3. Purposes and legal basis

Processing Purpose Legal basis (GDPR)
List, settings, PIN and keys on your phone or in your browser Letting you use the app and keep your list This is not processing carried out by us: the app keeps that data on your device and it does not reach us, except for the encrypted copy in the following rows
Encrypted copy of the list, secret gift blocks, register of phones, credential digests and technical data on the sync server Keeping the same list on the devices you connect and keeping the copy needed for the recovery you request Providing the service you request when you connect another phone or the web or create the code (Art. 6(1)(b)); you can stop syncing whenever you like, and the copy is deleted once no other device has access
Invitations and checkpoints Connecting another phone or the web Providing the service you request when you create or use the invitation (Art. 6(1)(b))
Recovery capsule, its identifier and its verifier Letting you get the list back on another phone Providing the service you request when you create the code (Art. 6(1)(b)); you can remove it whenever you like
Piece of key of the web app Making sure nobody opens your browser's data without the PIN Providing the service you request when you connect the web (Art. 6(1)(b))
Data about other family members inside the encrypted copy (names, birthdays and gifts of relatives, including children) Storing and syncing the list the family shares The legitimate interest of the person using the app and ours in providing that service to the family (Art. 6(1)(f)), balanced as explained below
IP address and request counters Delivering the connection and protecting the service against abuse Our legitimate interest in the security of the service (Art. 6(1)(f))
Minimal markers of deleted lists and codes (400 days) Making sure a used identifier cannot be taken again or reactivated Our legitimate interest in the security of the service (Art. 6(1)(f))
Support emails Replying to your enquiry Your request and our legitimate interest in handling it (Art. 6(1)(f))

Data about other family members. The list usually includes people who do not use the app (for example, children or grandparents). The person using the app decides what to note about them, within their own household. We only store those data and deliver them, encrypted, to the devices of that same family. We have balanced that interest against the rights of those people, with particular attention to children: the data are end-to-end encrypted and we cannot read them, we do not use them for anything else, no profiles are built and no decisions are taken about anyone, only the minimum is kept, and the family can delete them at any time. Because we cannot read the list or know whom it concerns, we cannot inform each of those people separately (Art. 14(5)(b) GDPR); that is why we explain it here, and the person using the app can show them this policy. If one of those people wants their data deleted, they can ask the family or write to us.

Legitimate interest and objection. For processing based on legitimate interest (Art. 6(1)(f)), you can object on grounds relating to your particular situation by writing to the contact email.

We make no automated decisions and do not build profiles about you.

4. Who receives the data

  • The other phones and web apps in your family, for whom the list exists: each one has a copy of what it is meant to see and the keys to open it.
  • Cloudflare, Inc., which hosts the sync server and the websites and forwards support email, as a data processor: it receives the encrypted copy, the encrypted recovery capsule, the technical data described above, the IP address of each connection and the emails you send us. It cannot read the list or the capsule. In addition, on its own account and under its own privacy policy, it processes connection data for the operation and security of its network (see "What the IP address is used for").
  • Proton AG, which hosts, under its terms of service, the owner's mailbox in which we receive and answer support emails.
  • The app you choose in the share menu when you send a .gifthuddle file or an invitation link.
  • The owner, at gifthuddle@gifthuddle.app, if you write to us.

We do not sell or pass on data to anyone else.

5. International transfers

The sync storage (the encrypted copy of the list, the secret gift blocks, the register of phones, the invitations, the recovery capsules, the web apps' pieces of key and our own request counters) is configured in Cloudflare's European Union jurisdiction, which keeps it in data centres in the EU.

Cloudflare, Inc. is a United States company with a worldwide network. Each connection normally enters through the Cloudflare data centre closest to the device, which will be outside the European Economic Area if you connect from outside it. The IP address, the technical data of the connection and the encrypted content pass through that centre in transit, and Cloudflare may process the IP address and the technical data outside the European Economic Area to deliver the traffic and protect its network, including when applying the general request limits and when forwarding email. Those transfers are covered by Cloudflare's data processing agreement (version 6.4, of 3 April 2026), which incorporates the European Commission's standard contractual clauses (modules 2 and 3) and Cloudflare's participation in the EU-U.S. Data Privacy Framework. You can read it at https://www.cloudflare.com/cloudflare-customer-dpa/ or ask us for information at the contact email. In any case, the list and the capsule are encrypted and Cloudflare cannot read them.

Proton AG is in Switzerland, a country the European Commission recognises as providing an adequate level of protection.

Any other services you decide to use (email, messaging or the destination of a shared file) are governed by their own terms.

6. How long data is kept

  • Data on your phone: until you delete it in the app (a gift, a person or everything, with "Delete everything" in Settings), clear the app's data in the system settings or uninstall it. On iPhone, the system may keep the app's keys in the Keychain after you uninstall it; the encrypted list is deleted. If you install the app again, it empties the Keychain on its first launch, so nothing from the previous installation is recovered.
  • Data in the browser: the encrypted box, until you use "Forget this computer" or "Erase this computer's data" or clear the site's data in your browser; the language and appearance preferences, until you clear the site's data.
  • Encrypted copy on the server: for as long as the list exists there; it is deleted when the last phone or web app with access leaves, when you are left as the only device with access and have no recovery code (except for secret gifts on hold or unread; see section 2), when you remove the code with no other phone or web app, or when 400 days pass without any use of the list. The copy uploaded when an invitation is created is deleted earlier if nobody joins: 24 hours after the last invitation and, at the latest, after 7 days (those created with earlier test versions follow the general 400-day period without use).
  • Data of a phone or web app that leaves the family: its credential stops working and its invitations, its recovery capsule and, if it is a web app, its piece of key are deleted. The encrypted secret gift blocks it had written are deleted 30 days later (for departures before 16 November 2026, 30 days from that date). Its entry in the register (identifier, public keys and the marker that it no longer has access) stays for as long as the list exists; if it was the last one with access, the whole list is deleted.
  • Invitations, packages and checkpoints: until the new phone confirms it has been set up, they are cancelled or they expire; at the latest, 24 hours.
  • Recovery capsule: for as long as the code is active and the list exists; its control data, for as long as the list exists.
  • Minimal markers of deleted lists and codes: 400 days from deletion (those from before 16 November 2026, from that date); after that they disappear on their own.
  • Request counters: one minute, or one hour for the new lists limit.
  • Request logs: our service does not keep them. The technical and security records that Cloudflare produces on its own account are governed by its privacy policy, which sets no specific period.
  • Support emails: one year from the last reply; then they are deleted.

7. Your rights

You can exercise your rights of access, rectification, erasure, objection, restriction of processing and portability by writing to gifthuddle@gifthuddle.app. We will reply within one month; if the request is complex, that period may be extended by two further months, and we will tell you so within the first month.

Bear in mind how the app is built:

  • Data on your phone or in your browser. We do not receive it, so we cannot see, correct or delete it for you. You see and correct it in the app itself. Deletions of gifts and people reach the other devices that keep syncing. To delete everything from a device, use "Delete everything" (on the phone) or "Forget this computer" (on the web), clear the app's data in the system settings or uninstall it; that does not delete the copies on the other devices.
  • Encrypted copy and capsule on the server. They are not linked to an account or to any name or email the server can read, and we cannot read them or find them by your name or email (Article 11 GDPR). You can withdraw this phone and its code with the options described in section 2. The shared list is deleted from the server once no other device has access. "Remove the code" deletes its capsule, and also the list if no other phone or web app is connected. "Delete this phone only" deletes nothing from the server. If you no longer have the app, the copy of the list and the capsule are deleted after 400 days without use; the minimal markers follow the periods in section 6.
  • Access and portability. If you give us information that allows your list to be identified securely (Art. 11(2)), we will handle your request for access and, where applicable, portability: we can give you the technical data we hold about it (for example, the identifiers, the register of phones and the rounded times of use) and the encrypted copies, with information about their format. We cannot decrypt the content of your list. We will never ask for your words, your PIN or your keys.
  • Taking the readable list with you. It is on your phone. "Save a copy" creates an encrypted file that only Gift Huddle can open on your family's phones. The app does not yet have an export in a format other apps can read.

If you believe we have not handled your data properly, you can lodge a complaint with the Spanish Data Protection Agency (Agencia Española de Protección de Datos): https://www.aepd.es

8. Children

Gift Huddle is intended mainly for the adults who organise a family's gifts. The minimum age to use it is 14. Teenagers aged 14 to 17 may also use it with a phone connected to the family, if the adults who organise the list decide so; that phone sees what the person it is assigned to and the protections turned on allow, and the server processes its identifiers and IP address like those of any other phone. It is not directed at children under 14, even though gifts for children are noted in it.

We do not ask for anyone's age or require an account, and we do not check age. If you use the connected features, we process the identifiers and technical data described in this policy.

The person using the app, normally an adult, can enter names and birthdays of other relatives, including children. They are stored encrypted on the family's devices and, if sync is in use, in the encrypted copy on the server. We cannot read them (see "Data about other family members" in section 3).

9. Security

  • The list is stored encrypted on the phone (AES-256-GCM) and the keys are in the system's secure storage.
  • The synced copy is end-to-end encrypted and signed, with keys that only the family's devices have, and travels over HTTPS. The server does not store those keys in a form it can use and cannot derive them from what it knows.
  • When a device is connected with an invitation, the keys are handed to it encrypted only after comparing the 6-digit code and after a phone in the family gives access. Recovery is a different route: with the 24 words, the permissions of the phone that created the code are recovered without any other approval.
  • Each phone has its own service credential. From another phone you can remove a phone or a web app from the family: the server stops accepting its credential as soon as it receives the request and the secret gift keys it knew are changed. What it had already stored cannot be deleted remotely; if you lose a phone, remove it from another one, and meanwhile its screen lock and the app's PIN are the protection.
  • The recovery capsule only opens with your 24 words. Whoever has them can join as that phone: keep them safe. Changing or removing the code stops anyone joining with them from then on, but does not remove anyone who has already joined.
  • The app does not go into Android backups, and on iPhone the list and the keys are kept out of backups.

Protecting your phone and your computer (screen lock, encryption, no root or jailbreak) is up to you.

10. Changes to this policy

If what the app does with data changes, we will update this page and the date at the top. If the change is significant (for example, if a new feature sent more data off the phone), we will also let you know inside the app.

The current version of this policy can also be opened from the app, in Settings → "About Gift Huddle" → "Privacy policy".

11. Contact

gifthuddle@gifthuddle.app