Privacy Policy
Last updated: November 21, 2026 · BigSavingsDays.com
What we collect
- Account data: name, email, hashed password, plan and workspace preferences.
- Link data: destinations, slugs, titles, deal tags, access controls and creation timestamps.
- Click data: timestamp, country, region/city when provided by the network, device type, browser, operating system, referrer and a salted hash of the IP address.
- Billing data: handled by our payment processor. BigSavingsDays never stores full card numbers.
What we do not collect
We do not set advertising cookies on redirects. We do not sell personal data. We do not build cross-site behavioural profiles. Deployments store click IPs as a SHA-256 hash with a server-side salt, not in plain text.
Cookies
BigSavingsDays uses a minimal number of first-party cookies:
bsd_session— keeps you signed in securely. HttpOnly, SameSite=Lax.bsd_unlock_*— remembers a deal password unlock for 30 minutes.bsd-theme— remembers your light/dark mode preference.
No third-party surveillance or tracking cookies are set on redirects.
Legal bases
For visitors in the EEA/UK, we rely on legitimate interests for security and aggregate analytics, contract necessity for account features, and consent where required for optional communications. You can object to analytics processing by contacting us.
Retention
Click data is retained according to plan (30 days on Free, unlimited on paid plans). Account data is retained while the account exists. Backups are rotated within 30 days of deletion. Aggregated, de-identified counts may be kept for capacity planning.
Your rights
You can access, correct, export or delete your data from the dashboard, or by contacting us. You may also lodge a complaint with your local data protection authority. We respond to verified requests within 30 days.
Processors
A production deployment would use a hosting provider, a transactional email provider, a payment processor and an error-monitoring service. Each would be bound by a data processing agreement.
Security
Passwords use scrypt with per-user salts. Sessions are HttpOnly and SameSite. API keys are shown once and stored hashed. Access to production is restricted and logged. No system is perfectly secure; report issues responsibly.
Contact
Privacy questions: contact us.