Effective date: May 19, 2026
Perimeter Brief ("we", "us", or "our") operates the website and service at perimeterbrief.io. This policy describes what personal data we collect, how we use it, who we share it with, and your rights regarding that data. We've written it to be readable, not just defensible.
| Data | When collected | Why |
|---|---|---|
| Email address | Newsletter signup or account creation | Delivering your digest and account communications |
| Name | Account creation | Personalising emails and your dashboard |
| Password (hashed) | Account creation / password change | Authentication. We never store plaintext passwords. |
| IP address | Login, API requests | Rate limiting, abuse prevention, security audit log |
| Browser / device info | Login | Session management and security alerts |
| Payment metadata | Subscription purchase | Billing. Card numbers are handled entirely by Stripe — we never see them. |
| Support messages | Contact form submissions | Responding to your inquiry |
| Ticket and dashboard content | Normal product use | Providing the service. Team plan data is org-isolated — other organisations cannot access it. |
| File attachments | Uploaded to tickets | Stored in Cloudflare R2; accessible only within your organisation. |
| Email delivery events | Automated — from our email provider | Handling bounces and unsubscribes to keep our list clean and compliant. |
We do not use tracking pixels, behavioural advertising, or third-party analytics scripts. We do not sell your data.
We share data with the following processors only to the extent necessary to provide the service:
| Provider | Purpose | Data shared |
|---|---|---|
| Stripe | Payment processing | Email, name, billing address. Card data never passes through our servers. |
| Mailgun | Transactional email delivery | Email address, email content |
| Amazon Web Services (SES) | Bounce and complaint handling | Email delivery events only |
| Cloudflare | CDN, DDoS protection, file storage (R2) | All web traffic passes through Cloudflare. Attachment files are stored in R2. |
| Railway | Database hosting | All database content is hosted on Railway infrastructure. |
| Vercel | Application hosting | Application code and server-side request logs |
We have data processing agreements in place with each of these providers. We do not share data with any other third parties except as required by law.
We use a single, strictly necessary session cookie (pb_sid) to keep you logged in. It is a secure, HTTP-only cookie that expires after 30 days or when you log out. We do not use advertising cookies, third-party tracking cookies, or analytics cookies of any kind.
Regardless of where you're located, you have the right to:
To exercise any of these rights, contact us at [email protected] or use the support page. We will respond within 30 days.
Passwords are hashed using bcrypt before storage. All data in transit is encrypted via TLS. Database access is restricted to application services — no public access is permitted. Team plan organisations have fully isolated data: no query or API endpoint returns data across organisation boundaries. We maintain an internal security audit log of all privileged actions.
Despite these measures, no system is perfectly secure. If you discover a security vulnerability, please report it responsibly to [email protected].
Perimeter Brief is intended for professionals and is not directed at children under 16. We do not knowingly collect personal data from anyone under 16.
We may update this policy from time to time. If we make material changes, we will notify subscribers by email at least 14 days before the changes take effect. The effective date at the top of this page will always reflect the most recent version.
Questions about this policy or your data? Reach us at [email protected] or through the support page.