baobun
12 hours ago
For such a sensitive use case with supposed focus on user control and privacy: Why not open source with self-hosting the backend as an option?
> Family Folder uses industry-standard encryption to protect your data. Your information is private and only accessible to those you invite.
This needs further detailing - Especially since sources are not available. What data is encrypted, where, and how? Who controls keys?
tonystaunton
12 hours ago
Thanks for taking the time to look at Family Folder.
With regards to open source & self-hosting, while I agree that open source and self-hosting are strong options for trust and control, for the moment I’ve prioritised ease-of-use and low-friction onboarding for non-technical families. Open-sourcing the core functionality and offering a self-hosted version is something I would consider in the future. As the solo person on this project I need to be very careful with my backlog but definitely something to add to it.
For encryption & privacy details I do need to provide more depth and add to the FAQs. Here’s a brief overview of how Family Folder currently works:
- In transit: All traffic is encrypted via HTTPS/TLS. - At rest: Files uploaded to S3 are encrypted using server-side encryption, and the database is encrypted at the volume level via Heroku Postgres. - Access control: Families are isolated by design — a user can only see the folders they’re invited to. Authentication is handled via Devise with session-based login (no tokens stored on client). - Key management: Encryption keys are managed by AWS and Heroku. I don’t currently offer user-controlled keys, but I understand how important that is for full control and again definitely something to consider in the future.
The project is still early stages, so I’m open to input on how to evolve these parts — especially from a privacy perspective.
Thanks again for the feedback.
Tony.