Last updated: October 16, 2026
Privacy policy
This policy describes the data Congratsly actually processes and the controls available to you. It does not claim legal compliance or invent operator details that have not been provided.
Data we process
We process account name, email and profile image when you sign in; recipient names, dates, celebration text, participant names and contributions; uploaded media and technical metadata; access tokens stored as hashes; and limited security and product analytics events. We do not sell personal data.
Why we use it
We use this data to authenticate users, create and deliver celebrations, invite contributors, protect private routes, operate live shows, prevent abuse, troubleshoot failures and understand aggregate product usage.
Accounts and authentication
Authentication is provided through Better Auth using Google OAuth or a one-time code sent by email. Necessary session cookies keep you signed in. Provider tokens may be stored with the account when required by the authentication flow.
Links and visibility
Organizer, contributor and recipient tokens are private. A published celebration can be viewed by anyone who receives its public link until access expires or the celebration is deleted. People with an invitation can see and add content allowed by that invitation. Avoid sharing links or content beyond the intended group.
Media and service providers
PostgreSQL/Neon stores application records. Cloudflare R2 stores uploaded files and provides short-lived signed viewing links. Resend delivers sign-in codes. Google handles OAuth sign-in. Vercel hosts the service and Speed Insights receives limited performance measurements. Embedded YouTube or Vimeo content is requested from those providers when viewed.
Cookies and device storage
Congratsly uses necessary authentication and contributor-session cookies. A locale preference cookie and local theme preference remember interface choices. No advertising cookies are configured. Speed Insights is used for operational performance measurement; the site does not load a marketing consent banner because no optional marketing cookies are currently configured.
Retention
Guest celebrations use the existing 72-hour access lifecycle. Account celebrations remain subject to the product's current storage rules. Short-lived signed media links expire after five minutes. Authentication codes expire after ten minutes. Infrastructure backups and security logs may persist for limited provider-controlled periods after live records are deleted. Without registration: 72 hours. Registration is optional. Free: drafts expire 3 days after creation; published greetings 3 days after publication. Premium storage remains available while the grant is active. Administrator grants only. No paid subscription or payment checkout is connected.
Deletion
An owner can permanently delete an individual celebration from the profile. This invalidates its public, organizer, contributor and recipient access by removing the related database records. R2 objects are queued before database deletion and retried safely if storage deletion fails. An authenticated user can delete the whole account after confirming the account email and typing DELETE; owned celebrations are removed before the user and sessions are deleted.
Other people's contributions
Deleting an owned celebration also removes contributions invited into that celebration because they cannot exist independently of it. Account deletion does not remove content a person submitted to celebrations owned by someone else.
Your choices and contact
You can delete celebrations or your account from the profile. The operator's verified legal identity, postal address, jurisdiction and privacy contact have not yet been supplied. A configured privacy email is shown below when available; the site owner must provide these legal details before relying on this page as a complete statutory notice.
Privacy contact
A verified privacy contact has not yet been configured by the site owner.