Security practices
1. Access control
Administrative access requires an approved staff account on our own domain. Staff roles are stored separately from user profiles and checked on the server for every request. Client information is never exposed to unauthenticated visitors.
2. Client links
Each onboarding link is a single-purpose credential. Links are stored hashed rather than in plain text, expire, can be revoked at any time, and lock themselves read-only once the client has signed. Revoked or expired links show a neutral message that does not reveal whether a deal exists.
3. Documents and signatures
Uploads, signatures and signed agreements are stored in private buckets. Uploaded files are size-limited, quota-limited and content-checked before they are accepted. Downloads by staff use short-lived signed links and are recorded in the audit log.
4. Payments
Card details are entered directly with our payment processor. We never see or store card numbers. Payment webhooks are signature-verified and replay-protected before any status is updated.
5. Monitoring and audit
Link issues, extensions and revocations, agreement changes with before-and-after values, signed-document downloads, email sends and re-sends, and data exports are all recorded with the staff member responsible and the time of the action.
6. Abuse protection
Public endpoints are rate limited per link and per network address, submissions are idempotent so a repeat click cannot create a second agreement, and error messages are deliberately neutral so they cannot be used to probe for valid links.
7. Reporting a vulnerability
If you believe you have found a security issue, email support@placemates.pro with the details and how to reproduce it. Please don't access, modify or delete data belonging to other people while testing. We will acknowledge your report and keep you updated while we investigate.