Privacy at GroupNote
Last updated:
GroupNote lets organisers create group greeting cards and contributors add messages without accounts. This notice explains how the current free version handles information.
What we collect and why
We store the details you submit when creating or signing a card: the occasion, card title, recipient and organiser names, introductory note, selected theme, contributor names, messages and emoji. We also store creation times and whether contributions are open or closed. We use this information to display cards, collect messages and let organisers manage their cards.
The app does not require accounts, email addresses, phone numbers or payment details to create or sign a card. Any personal information you choose to put in a name or message becomes part of that card.
For basic abuse prevention, we store daily salted hashes derived from network addresses, dates, action types and request counts. The app uses these records to limit card creation and message submissions.
Who can see a card
Anyone with a card's invitation link can read its contents and add messages while contributions are open. A link can be forwarded by anyone who has it. Closing contributions stops new messages; it does not stop people with the link from reading existing messages.
The private organiser link allows its holder to close, reopen or delete the card. Keep that link private and use Copy invite link when inviting contributors. Avoid putting confidential or sensitive information in cards.
Storage and other services
The app saves an organiser key in the browser's local storage when a card is created. Deleting the card through its organiser link removes that saved key from the browser used for deletion. Copies saved in other browsers are not automatically cleared.
We keep daily aggregate counts of landing-page visits, create-form opens and successful card creations to understand how people find and start using GroupNote. Visits directly to shared cards are not counted as landing visits. Counts are grouped by Australia/Sydney date and a small set of campaign labels, such as uni_email. Unknown source labels are grouped as other; we do not store the raw URL parameter.
For these counts, session storage in your browser remembers the campaign label and which events have already been counted in that tab for the day. This normally clears when the tab's session ends. We do not send a session identifier, full page URL, referrer, card content or organiser key with these events, and the analytics table contains only a date, campaign label, event type and count. We do not store IP addresses, email addresses or browser fingerprints in this analytics table. Counts represent approximate tab sessions and events, not unique people.
We also keep content-free card lifecycle records: successful creation, share-button actions, invitation opens, successful contributions and deletion. These record a separate random card alias, event time, allowed campaign label when known, and fixed share-method/outcome labels. They contain no names, titles, message contents, email addresses, IP addresses or organiser keys. A live-card mapping connects the alias to a card while it exists; that mapping is removed when the card is deleted. Share-button clicks, clipboard copies and browser-reported share completion do not prove an invitation was delivered.
To deduplicate invitation refreshes, session storage remembers a random event token for each card in that tab. The token is sent without the page URL or referrer and is transformed into a card-scoped event key on the server. It is not a cross-card visitor identifier. Private organiser URLs do not emit invitation-open events. Anonymous tab sessions are approximate and do not establish unique people or whether a contribution came from someone other than the organiser.
Card and message submissions use random private request tokens held in page memory so network retries can reuse a result. The server does not store the raw tokens. Separate operational creation receipts retain only a hash and a random card ID, including after deletion, to prevent a retried creation from restoring a deleted card. Receipts contain no card contents or organiser keys. Older clients without request tokens cannot reliably deduplicate repeated submissions.
You can exclude this browser from analytics. This saves a local preference with no identifier; reload other open GroupNote tabs after changing it. Excluded browsers send no landing, form, share or invitation events. A boolean on creation, contribution and deletion requests tells the server to skip their analytics without preventing the actual action or storing a browser identity. Operational retry receipts still work. This does not remove your cards, messages or previous counts/history; later activity from other browsers on the same card can still be counted. You can resume counting in this browser. Set the preference separately on each browser/device; clearing site storage or starting a new private-browsing session loses it. If browser storage is blocked, the exclusion applies only to the current page.
No advertising cookies, analytics cookies or third-party analytics services are used. Pages load fonts from Google Fonts, which requires your browser to connect to Google. When GroupNote is hosted online, the hosting provider also processes technical connection information needed to deliver the service. The app is configured to use Cloudflare for hosting and database storage.
How long information stays
Cards and their messages have no automatic expiry. They remain in the app's database until the organiser or site operator deletes them. Deleting a card removes its associated messages from the app's database. Closing a card does not delete its data.
Abuse-prevention records currently have no automatic deletion schedule. Deleting a card does not delete those separate records. Deleting a card also cannot remove copies that other people have saved, printed or exported.
Daily aggregate acquisition counts have no automatic expiry. They are not linked to individual cards or people, so deleting a card does not change these historical counts. Current-card and contribution statistics still exclude deleted cards and messages.
Content-free lifecycle history and operational retry receipts have no automatic expiry and remain after card deletion. They cannot restore deleted card contents. Lifecycle tracking begins with its deployment; activity never recorded before that time is not reconstructed. Excluded activity and tracking failures can leave reporting gaps.
Questions, corrections and removal requests
To ask about your information, request a correction or removal, or raise a privacy concern, contact the GroupNote operator using the details below. Contributors can also contact the organiser who invited them. There is currently no self-service option to edit or delete a single message.
Include the card's invitation link and enough information to identify your contribution. Do not send the private organiser key or unrelated sensitive information. If you contact us by email or phone, we will receive the contact details and information you choose to share so we can respond to your request.
GroupNote privacy contactEmail: sssafiullahhh@gmail.com
Phone: +61 405 974 360