Security and responsible disclosure
Last updated 22 November 2026
Families trust us with things that matter: the details of someone they loved, photos, and the names and email addresses of the people they want to tell. This explains, in plain words, how we protect them, and how to tell us if you find a weakness.
How we protect data
- Where it lives: the site, its database and uploaded files are hosted on Google Cloud through Firebase, in the United States. Google keeps stored data encrypted.
- Encrypted on the way: every page and every request uses HTTPS, so what you send and see is encrypted between your device and us.
- Only our server reaches the database: browsers can't read or write the database or file storage directly; every request goes through our server, which checks who is asking.
- Signing in: sign-in is handled by Firebase Authentication. If you use a password, it is stored only in scrambled form by Firebase, and we never see it. After you sign in, a signed cookie that scripts on the page can't read keeps you signed in, and you can sign out of every other device from your account page.
- Payments: card payments are handled by Razorpay. Your card details go straight to Razorpay; we never see or store them.
- Email: emails are sent through Amazon SES. Our server uses short-lived credentials for it, so no long-lasting email keys are kept anywhere.
- Access is limited: only the few people who run Tribute Paper can reach the admin area, which is protected by a password. Keys and passwords the site needs are kept in Google Cloud's secret storage, not in the code.
- Private pages: memorial pages are shared by link and we ask search engines not to list them. Forms that anyone can use, such as replies and messages, are limited per visitor to stop misuse.
No system is perfectly secure. If a breach ever affects your data, we will tell you, and the authorities where the law requires it, without delay, as our privacy policy says.
Reporting a security problem
If you believe you have found a security weakness in Tribute Paper, please tell us. Email hello@tributepaper.com with “Security” in the subject, and include:
- what you found, and the address of the page or request where it happens;
- the steps to show it, and what someone could do with it;
- how we can reach you, and whether you would like to be thanked by name once it is fixed.
If you think your own account has been used by someone else, sign out of all other devices from your account page and write to us straight away.
What we ask of you
- Act in good faith, and only test against your own account and your own designs or pages.
- Don't look at, copy, change or delete anyone else's data beyond the least you need to show the problem. If you come across a family's details, stop, don't keep them, and tell us.
- Don't disrupt the service: no denial-of-service testing, no heavy automated scanning, no spam, and no sending emails to families or their guests.
- Don't try to trick our staff or our customers, and don't attempt physical access to anything.
- Give us reasonable time to fix the problem before you tell anyone else. We ask for 90 days, and will work with you if it needs longer or can be done sooner.
Problems in services we use, such as Google, Razorpay or Amazon, should go to those companies, though we are glad to hear about anything that affects Tribute Paper.
What we promise
- We will acknowledge your report within 48 hours.
- We will look into it, keep you told how it is going, and let you know when it is fixed.
- We will thank you by name once it is fixed, if you would like that.
- We won't take legal action against you, or ask anyone else to, for research done in good faith that follows this page.
We are a small company and don't offer payments for reports at present.
This page is also linked from our security.txt file, in the standard place where security researchers look.