Security.
Operated by Waelas Ltd · last updated October 2026
You trust Forge with your calendar and your clients’ details. Here is how we look after them, and what to do if you find a problem.
How we protect your data
- Your data is encrypted in transit between your browser and Forge (TLS 1.2+, HSTS).
- Our database is encrypted at rest with AES-256 by our database provider.
- Calendar credentials are additionally encrypted by us with AES-256-GCM before they are stored.
- We never store your Forge password, only a salted hash of it (scrypt). An app-specific password for iCloud or another CalDAV calendar is different: we have to use it to reach your calendar, so it is stored encrypted, not hashed. You can sign in to Forge with Google instead.
- Our database and servers run in London, with point-in-time recovery for the previous seven days.
- Public links to bookings, invoices, proposals and portals use long, unguessable tokens, and are kept out of search engines.
- Before an error report is sent, from our servers or from your browser, we remove cookies and the contents of forms and requests, and scrub the credentials and private-link tokens we can recognise. The error message itself is not filtered, so it can still contain personal data, such as an email address in a database error.
- Sign-in, booking and every other public form is rate-limited.
- We don’t sell data, show ads, or run tracking or session-recording tools.
The companies that help us run Forge are listed in our Privacy Policy, and our commitments to you as a processor are in the Data Processing Agreement.
Reporting a vulnerability
If you think you have found a security problem, email support@forge.page with the subject “Security report”. Include what you found, where, and the steps to reproduce it.
We ask that you:
- give us reasonable time to fix it before telling anyone else;
- only test against your own account, and never access, change or delete other people’s data;
- don’t run denial-of-service, spam or social-engineering tests, or test physical security.
In return, we will:
- reply within three working days, and keep you updated;
- not pursue or support legal action against you for research done in good faith within these rules;
- credit you when it’s fixed, if you would like us to.
We don’t run a paid bug bounty. Our machine-readable contact is at /.well-known/security.txt.