Trust & Security

• Accounts are protected by email and password. Passwords are stored only as salted hashes and are never visible to us or to staff.
• New couples and suppliers must confirm their email address before their account is usable.
• Administrators can turn on two-step verification, which emails a six-digit code that expires after 10 minutes and locks out after repeated wrong attempts.
• A couple can add one partner as a co-owner. That partner verifies their own email and sets their own password — accounts are never shared by passing a password around.
• Helpers invited by a couple see only what that couple chooses to share with them.

Every table holding personal data enforces access rules in the database itself, not just in the app. A signed-in couple can read and write only their own wedding, guest list, budget and messages; a supplier can see only their own listing, enquiries and invoices. Guest RSVP and gift registry links work from a single-purpose token that grants access to that one invitation and nothing else.

Staff accounts are separate from couple and supplier accounts and carry named permissions — reviewing supplier listings, managing accounts, viewing payments, editing content or managing the team — granted individually by the master administrator. Staff join by invitation only, on a time-limited invite link. Nobody gets blanket access by default.

• All traffic to the site and to our backend is served over HTTPS with TLS.
• Data at rest is encrypted by our managed cloud database provider.
• Credentials and API keys are held in a secrets store, never in application code.
• Card details are handled entirely by our payment processor and never touch our systems.

Service emails are sent from our own verified sending domain with SPF and DKIM authentication, which protects recipients against spoofed invitations. Bounces, complaints and unsubscribes are recorded on a suppression list so we do not keep emailing an address that does not want to hear from us.

We ask only for what the planning tools need. Sensitive details — religion, heritage, dietary requirements and allergies — are optional and collected with explicit consent. Guest data is deleted on the schedule set out in our privacy policy, and account deletion is available to every user from their own account settings.

We keep application error and email delivery logs, and run regular automated security reviews of our database rules and dependencies. If a personal data breach occurs, we investigate immediately, and where the law requires it we notify the Information Commissioner's Office within 72 hours and tell affected individuals without undue delay.

• Ours: securing the platform, enforcing access rules, patching, encrypting data, vetting our processors and responding to incidents.
• Yours as a couple: choosing a strong password, deciding who you invite as a co-owner or helper, and adding guests only when you are entitled to.
• Yours as a supplier: keeping your listing accurate, protecting any couple or guest data you receive, and telling us quickly if something goes wrong.

If you believe you have found a security issue, email security@plannedmemories.co.uk with enough detail to reproduce it. Please give us a reasonable window to fix it before disclosing publicly, and do not access or alter data belonging to anyone else while testing. We will acknowledge your report and keep you updated.

We operate to the UK GDPR and the Data Protection Act 2018, and maintain internal governance documents including a record of processing activities, a retention schedule, a subject access request procedure and a breach response plan. We do not currently hold ISO 27001, SOC 2 or any equivalent third-party certification, and we do not claim to.