Privacy Policy
Last updated: November 2026 · Plain-English summary of how OneGroupCard protects your cards, photos, and personal data.
1. What We Collect (Minimal by Default)
Card Signers & Recipients: Signing or viewing a group card never requires creating an account or sharing an email address. When you sign a card, we store only the display name, optional team/role label, message, handwritten signature stroke data, and optional photo you explicitly submit to that card.
Optional Google Sign-In (Organizers): If an organizer chooses “Continue with Google” to sync cards and 10-Pack credits across devices, we receive only basic Google Identity profile claims (sub, verified email address, display name, and profile avatar URL). We never request access to your Gmail, Google Contacts, or Google Drive.
Spam protection: to limit abuse, we store a daily-rotating hash of the visitor’s IP address with submitted signatures and Google sign-ins. We do not store the IP address itself.
2. Private Group Cards Are Never Indexed
Every individual group card (/c/*, /sign/*, and /manage/*) uses an unguessable random URL slug and strict noindex, nofollow directives so personal coworker, classroom, and family messages are excluded from search engines.
3. Payments & Billing Security
Optional one-time Keepsake Pass ($2.49) and Office & School 10-Pack ($14.90) purchases are processed directly by PayPal (including Debit/Credit Card, Apple Pay, and Google Pay checkout). OneGroupCard never sees or stores credit card numbers or banking credentials—only PayPal’s transaction/order identifier, amount, and payer receipt email.
4. Cookies & Analytics
Essential cookie: we set a first-party session cookie (AUTH_SESSION) only when an organizer chooses to sign in with Google.
First-party counters: we keep aggregate, non-identifying daily usage counts (such as page views, cards created, and downloads) to keep the service fast and reliable.
Google Analytics 4: we use Google Analytics 4 (Google LLC) to understand which of our public pages (home, guides, pricing, create) and features people use. It sets first-party cookies (_ga and _ga_*, lasting up to two years) and receives page views, approximate location, device and browser type, the referring website, and usage events from those pages (for example a card created, a template picked and, when a 10-Pack is bought on the pricing page, checkout started and purchase completed—with the item, amount, payment method, and our own order number). Google states that GA4 does not log or store IP addresses. We do not load Google Analytics on the pages where a card is viewed, signed, or managed (/c/*, /sign/*, /manage/*), so Google receives no card link, organizer key, recipient or signer name, message, or photo from them; the only exceptions are the four public sample cards linked from our homepage, whose content is fictional. Those pages do not pass the card’s address to the next page you open as its referring page (at most they share our site’s domain).
PVUV: we also use PVUV (pvuv.ai), a web analytics service, to count visitors and see which public pages and campaigns bring people to us. It sets first-party cookies (_pv_id, _pv_sid, _pv_ft and _pv_uid, lasting up to about 13 months) and receives page views, the referring website and campaign tags in the address, approximate location, device and browser type from our public pages, plus the same usage events. PVUV states that it keeps only keyed hashes of IP addresses, not the addresses themselves. Like Google Analytics, it is not loaded on the pages where a card is viewed, signed, or managed (/c/*, /sign/*, /manage/*), apart from the four public sample cards.
Cloudflare Web Analytics: Cloudflare, which hosts and delivers our site, adds its own small measurement script to the pages it serves for us. It measures how fast a page loads for you and counts visits, and our Cloudflare account shows us the totals by page address, referring website, country, device type, browser and operating system. Cloudflare states that this script sets no cookies and uses no local storage, does not fingerprint visitors, and discards your IP address at its nearest data center instead of storing it. We have also switched on the option that makes Cloudflare drop the measurements it collects in its data centers in the European Union. Unlike Google Analytics and PVUV, Cloudflare adds this script to every page automatically, card pages included (/c/*, /sign/*, /manage/*). So for a card page, the page address, which is the card’s own link, appears in our Cloudflare report. It is not sent to Google or PVUV.
Events reported from our server: some steps happen where we cannot run those scripts: on card pages, or in the background (for example PayPal confirming a payment). For those, our server itself sends a short event to PVUV: the event’s name (for example card created, message signed, card opened, checkout started, purchase completed), a few non-identifying details (such as the occasion, template, item, amount, payment method and our own order number) and one identifier: the PVUV cookie your browser already has, a random account number if you are signed in, or a pseudonym derived from a one-way hash of your network address and browser details that changes every day. We never send the card’s address, an organizer key, a name, a message, a photo, an email address or an IP address this way.
Opting out: if your browser sends the Global Privacy Control signal (for example Firefox, Brave, DuckDuckGo or a browser extension), we load neither the Google tag nor PVUV and send no events from our server. Blocking scripts or using the Google Analytics opt-out browser add-on stops the browser-side scripts only, not the events our server reports, so use Global Privacy Control if you want to opt out of Google Analytics, PVUV and those server events. Global Privacy Control does not switch off Cloudflare’s measurement script described above; blocking static.cloudflareinsights.com in your browser does. The service works the same either way.
We never sell personal data or run advertising-network trackers.
5. Moderation, Deletion & Contact
Card organizers can hide or remove individual entries at any time from Organizer Studio, and signers can delete their own entry from the browser where they signed. To request permanent deletion of a card or synced Google account record, email support@onegroupcard.com.