Cardinall
The information used to create, share and deliver your cards.
| Information | What it is used for |
|---|---|
| Account & profile | Sign-in email and session records provide account access. Optional profile name, contact email, phone, photo and signature preferences support your profile and signing experience. Contact email and phone do not change your sign-in email. |
| Cards & messages | Recipient names, participant/display names, written messages, layout, uploaded media and selected GIF metadata are used to save and display the group card. |
| Sharing & delivery | Invitee/recipient addresses, sender name, optional delivery note, schedule and time zone are used to send invitations, deliver the card and confirm delivery to the organizer. Ownership handoffs also retain the invited address, invitation state and the accounts that hand over and accept the card. |
| Purchases | Payer email, order reference, purchase quantity, amount, payment status, Stripe reference and timestamps are used to confirm payment, assign cards/credits and investigate payment issues. Card orders also retain delivery details. |
| Support & security | Information supplied in support email is used to address the request. Hashed request identifiers, rate-limit counts and limited application logs help prevent abuse and investigate errors. |
Card numbers and security codes are entered into Stripe payment fields. Cardinall’s own forms do not collect those card details. Avoid putting sensitive personal information into a card or support message.
Anyone with a signing link can view and sign the card without an account. Give that link only to the intended group. The recipient link is separate: before a scheduled release it shows a waiting envelope; after release it opens the delivered card. Someone who receives a forwarded link can open it too.
A card owner can invite another verified account to take ownership of a paid card. Control changes only after that account accepts. The former owner remains a contributor, and existing messages, photos and delivered recipient links remain attached to the card. The original purchaser keeps their receipts and remaining card credits.
Card visibility relies on possession of the link, not verification of the person’s email address. Keep sign-in, purchase-claim and recovery links private because they grant access to an account or eligible purchases.
| Provider | Role & information |
|---|---|
| Cloudflare | Hosts the application, structured records and uploaded media using Workers, D1 and R2. Requests also pass through its infrastructure. |
| Stripe | Processes payments and receives payment details, purchaser email, purchase amount and order/purpose references. |
| Resend | Sends sign-in, receipt/claim, recovery, invitation and delivery emails. It receives addresses and rendered email content, including relevant names, notes and access links. |
| PostHog | When enabled on the production website, receives limited product events, pseudonymous account identifiers and masked recordings of selected public pages. |
| GIPHY | When configured, receives searches directly from your browser and serves GIF media. Selected provider identifiers and metadata are stored with the message. |
| Support email services | Apple/iCloud hosts the operator inbox for messages sent to support@cardinall.ca and contact@cardinall.ca. Resend separately handles transactional application emails. |
Current automatic cleanup covers incomplete delivery form contents after one hour from the last saved edit and unconverted demo cards after 24 hours. A demo with pending or paid checkout is protected from demo cleanup; a purchased demo becomes a retained card. Those rules do not set the lifetime of ordinary cards or account records.
Organizers can permanently delete unsent cards through the card controls, with a pending checkout cancelled first. For delivered cards, Remove from My Cards hides the organizer’s dashboard listing while keeping the recipient’s link, messages and photos available. Unreferenced media from deleted cards is removed; shared media remains while still referenced, and failed media deletions are retried. Removing a profile photo also requests storage cleanup.
Card deletion does not erase the associated financial order/payment record. Those records can retain purchase email and delivery snapshots, including sender name, note and recipient email. There is no comprehensive self-service account deletion or data-export workflow.
You can update the available profile fields, remove a profile photo and use the card deletion controls. Choose carefully whom you share card links with and what information you include in messages.
General enquiries can also be sent to contact@cardinall.ca. Both contact and support addresses are established; current mailbox monitoring and response coverage still need confirmation.