Portalry Data Map

What we store, why, where, and for how long (Effective 28 November 2025)

Data category	Purpose	Location / processor	Retention
User accounts (name, email, username, password hash, profile, connected accounts)	Core service, authentication, profile display	Primary app database on DigitalOcean; user images in encrypted object storage	For the life of the account; inactive accounts deleted after notice period (see privacy policy)
Portalries and portals (names, descriptions, links, settings, images)	Deliver portalry and portal content to members/visitors	Primary app database on DigitalOcean; images in encrypted object storage	Until deleted by owners or via inactive owner deletion workflow
Memberships and invitations	Manage access/roles to portalries; invite flows	Primary app database on DigitalOcean	For the life of the portalry or until removal; invitations per business need
RSVPs and attendance	Event coordination and attendance tracking	Primary app database on DigitalOcean	Business need; removed on account deletion or inactive-owner deletions
Email reminders and logs	Scheduling and troubleshooting reminder sends	Primary app database on DigitalOcean; email delivery via AWS SES	Reminder logs kept 12 months
Login audits	Security and account activity review	Primary app database on DigitalOcean	36 months
Portal creation failure logs	Support/troubleshooting unsupported platforms	Primary app database on DigitalOcean	12 months
Portal integration sync logs	Audit integration sync requests/responses	Primary app database on DigitalOcean	12 months
Audit logs (premium portalries)	Trace admin actions for compliance/support	Primary app database on DigitalOcean	12 months
Backups	Disaster recovery	Encrypted object storage in managed cloud (DigitalOcean)	Operational retention as needed; subject to deletion schedules on restore

Questions? Contact our Data Protection Officer: [email protected]