GigglePointsPrivacy policy
Last updated: 8 November 2026
Draft for review, not for publication. The lawful bases, provider retention periods and international transfer arrangements need to be confirmed before release.
GigglePoints keeps the scores for family card games. A grown-up manages the account and players. Children and guests can appear on the scoreboard without having accounts of their own. This policy explains what happens to those details.
1. Who is responsible
Adam Stone, trading as GigglePoints in England, is the data controller for the personal information described here.
For privacy requests, email help@gigglepoints.s7one.co. Write to Adam Stone, trading as GigglePoints, at The Bristol Office, 2nd Floor, 5 High Street, Westbury-on-Trym, Bristol, BS9 3BY, England.
2. The information we use
- Your account: your email address, an account identifier and sign-in records. We email a six-digit sign-in code. You do not create a password. The app stores session credentials securely on your device so you can stay signed in.
- Players: the display name or nickname entered by the grown-up, the chosen character and colour, whether someone is a family player or guest, and whether a family player has been archived. Please use nicknames and avoid surnames or other identifying details.
- Games: the game type, a custom game name if entered, settings, players, round scores, corrections, results and dates. The app calculates totals and rankings from these entries.
- Technical information: our hosting and email providers process connection and delivery records, which may include IP addresses, request times, device or browser information and email delivery status, to operate and protect their services.
- Optional crash reports: in iOS versions with crash reporting, reports can contain installation identifiers, device and app versions, stack traces and exception messages. They are saved on the device pending your choice to send or discard them.
- Messages you send us: if you contact us, we receive your contact details and whatever you include so we can answer. Please leave out unnecessary information about children.
3. Where scores are saved
Games and players are saved on the device first. When you sign in, the app synchronises that account's players, games and scores with our servers so they can be recovered on another signed-in device. Changes made offline are queued until a connection and a valid session are available. Signing out stops synchronisation but keeps the local games and players on that device. If you back up your device, its backup may include that local data and restore it later.
There are no public profiles, public leaderboards or in-app conversations between households. Anyone who can open the app on your device may be able to see its local scores and player names, so use your device's passcode and take care with shared devices.
4. Why we use information
Proposed lawful bases for owner and legal review: we use the adult's account information to provide the service requested under our agreement with them (contract). For players' names, characters and scores, including information about children supplied by a grown-up, the proposed basis is legitimate interests: enabling the family to keep and revisit its game results. Protecting the service and answering requests also serve legitimate interests. These interests must be assessed against the rights of the people concerned, with particular care for children. Optional transmission of crash reports is based on consent. Where we must retain or disclose information to meet a legal requirement, the basis is legal obligation.
A grown-up needs an email address to sign in before the household can start keeping scores. After signing in, you can keep score offline while the app has a saved session. We do not use player information for advertising, behavioural profiling or decisions with legal or similarly significant effects.
5. Children and other players
A parent or guardian should create and manage a child's player profile. Children do not need to sign in or give us an email address. We do not ask players for a photo, date of birth, location or real surname. Explain to players, in words they understand, that their nickname and scores are saved and may be synchronised to the grown-up's account.
For younger players: GigglePoints remembers your nickname, character and scores so you can see how the game went. Your grown-up chooses what to enter. Other people playing on the same device can see the scoreboard. There are no adverts or public chats.
The app does not currently verify the age of the account holder or who taps the crash-report choice. Requiring an adult account does not by itself establish parental consent under children's privacy laws. The release assessment must confirm the safeguards and any additional notices or consent needed in the countries where the app will be available.
6. Providers and other recipients
| Provider | Information and purpose |
|---|---|
| Supabase | Hosts sign-in and synchronised account data: the adult's email and account ID, player names and characters, games, scores and related records. The project database is hosted in Ireland. Supporting services and subprocessors may operate elsewhere. |
| Resend | Delivers sign-in code emails and processes the recipient address, email content and delivery records. The configured sending region is Ireland. Resend may also process data elsewhere. Your email app or its proxy may contact Supabase to load the images in the sign-in email. |
| Google Firebase Crashlytics | Receives diagnostic reports when you choose Send reports. Automatic report uploads are disabled. Google may process reports outside the UK and EEA, including in the United States. |
| Cloudflare Pages | Hosts the GigglePoints website and handles requests for its pages. Those requests can include an IP address and browser information. |
| Google Workspace | Receives support and privacy requests sent to our support address. Google handles the sender address, message and any attachments you choose to include so we can respond. |
We do not sell personal information or share it with advertisers. We may disclose information where legally required, or where necessary and lawful to investigate misuse or protect people's rights.
7. Crash-report choices
When an enabled iOS version finds pending reports at launch, it asks whether to send them to Google Firebase or discard them. Choosing Discard reports requests deletion of the pending reports from the device. Choosing Send reports sends those pending reports; it does not switch on automatic uploads for future crashes. The app does not deliberately attach your account email, player names or scores to reports, but exception messages can contain information involved in an error.
You can decline future sends without losing the scoring features. If you want to withdraw consent for information already sent, contact us. Withdrawal does not undo processing that was lawful beforehand. Because reports are not labelled with your account email, we may need further information to locate one. Deleting your GigglePoints account does not itself delete a report already sent to Google.
8. Certificates you save or share
A winner's certificate is drawn on the device from a finished game. It includes the winner's name and character, the game, score, rounds, date, number of other players and a short celebratory line. The app creates a temporary image for Save or Share and attempts to remove that temporary file afterwards. The celebratory line can sync with the game record. The certificate image stays on your device unless you choose to share it or back it up.
Save asks permission to add the image to Photos, without reading your existing photos. Share opens the device's share sheet. The app or person you choose receives the image under their own arrangements. Photos may also be backed up by your device's cloud-photo service. Think carefully before sharing a child's name. Deleting a game or account does not remove exported or shared copies.
9. Retention and deletion
We keep account information and synchronised game history while the account is active, unless you delete the account or we fulfil a valid deletion request. Discarding an unscored game removes that game and any temporary guest profiles used only in it. There is no automatic expiry for inactive accounts. Archiving a player hides them from the active family list; it does not erase their name or past games. Correcting a score adds a revision, so earlier score entries remain in the game records.
In Account, choose Delete my data and confirm. An internet connection is required. The operation deletes the account and its player and game records from the live server database, then attempts to clear that account's data on the device making the request. If you get an error after confirming, contact us for help checking whether deletion completed. It does not remotely erase local copies on other devices, saved certificates, recipients' copies or reports already sent to Crashlytics. Signing out or uninstalling is not a request to delete server data.
Google says it begins removing Crashlytics stack traces and associated identifiers after 90 days. Pending reports remain subject to the device's storage and your send or discard choice. Copies in device backups, provider logs or provider backups may remain after account deletion.
Before publication: confirm and state the actual Supabase backup and operational-log periods, Resend message and delivery-log periods, support-message retention and any legal-retention exceptions. Account deletion must not be described as immediate erasure from every provider or backup.
10. International transfers and security
Our database is in Ireland. Providers may also process information in other countries. A European hosting or sending region is not a promise that every supporting service stays in Europe.
Before publication: verify the agreements and safeguards actually in place for each transfer outside the UK, including any applicable adequacy arrangements or contractual clauses and the UK Addendum, and explain how to obtain a copy. Provider template agreements alone do not establish that our deployment has completed that assessment.
Network connections to the backend use HTTPS, server access rules separate accounts, and the app stores sign-in credentials in the device's secure storage. Anyone with access to an unlocked device and an active session can open the app and see the scores.
11. Your rights
Depending on the law that applies and the circumstances, you can ask to access, correct or erase your personal information, restrict its use, object to processing based on legitimate interests, and receive qualifying data in a portable format. You can withdraw consent where we rely on it. These rights also belong to children; a parent or guardian may act for a child where appropriate. You do not have to own the account to ask about information concerning you.
Use the privacy contact in section 1. We may ask for information reasonably needed to check your identity or authority. We normally respond within one month; if the law allows more time, we will explain why. There is no in-app download of all account data, so request a copy directly.
You can complain to the UK Information Commissioner's Office or the relevant data-protection authority where you live.
12. Changes
We update this page when our practices change and email account holders about material changes within 14 days. Where the law requires earlier notice or fresh consent, we provide it before the change takes effect.