buildPrivacy Policy
1. Who we are
buildquarter builds software for clients through private project buildrooms. This policy explains what personal data we handle and why.
2. What we collect
- Account and contact: name, email, company, phone, optional GitHub username.
- Project: proposals, milestones, tickets, comments, activity, files and links you share.
- Payment: payment status, invoice details and amounts from Stripe. We do not receive full card details.
- Calls: name, email, selected time and notes you provide when booking.
- Technical: session cookie, sign-in state and basic server logs.
3. Why we use it
| Purpose | Basis |
|---|---|
| Run your buildroom and deliver the project | Contract |
| Take and reconcile milestone payments | Contract and legal obligations |
| Send service emails, invites and updates | Contract and legitimate interests |
| Security, fraud prevention and dispute records | Legitimate interests and legal obligations |
4. Cookies
We use an essential HttpOnly session cookie, pl_session, to keep you signed in. We do not use advertising cookies.
5. Processors
| Processor | Purpose |
|---|---|
| Stripe | Payments |
| Resend | Transactional email |
| Railway | Application hosting |
| GitHub | Code hosting and repo access |
| Jitsi | Video calls |
| Anthropic | Planning and summary generation |
| Namecheap Private Email | Email inbox |
We do not sell personal data.
6. International transfers
Some processors may process data outside the UK or EEA. Where required, we rely on adequacy decisions, Standard Contractual Clauses or equivalent safeguards.
7. Retention
We keep project and account data while we deliver the service and for a reasonable period afterwards for tax, accounting, security and dispute records. We delete or anonymise data when it is no longer needed.
8. Your rights
You can request access, correction, deletion, restriction, portability or object to processing by emailing support@buildquarter.com. You can also complain to the ICO.
9. Security
Passwords are hashed with scrypt. Sessions are server-side and cookies are HttpOnly. Payments run through Stripe. See our Trust Centre.
10. Changes
We will update this page when the policy changes.