01
EU/EEA-hosted primary service data
Primary production service data is hosted in the EU/EEA, with documented safeguards for limited infrastructure metadata where required.
Privacy-focused email infrastructure for product teams
Postscale combines transactional sending, inbound webhooks, masked email aliases, suppressions, DMARC reporting, retention controls, and GDPR documentation for teams that treat email as sensitive product infrastructure.
Need the full developer surface? Start with the email API platform for sending, inbound, SMTP, and aliases.
Everything the product needs. Nothing it does not.
A focused API surface with production controls, predictable resources, and the operational visibility to run email confidently.
02
Masked addresses for users
Generate revocable aliases that forward to real inboxes so users can communicate without exposing personal addresses in your product.
03
Inbound privacy controls
Receive parsed inbound email through signed webhooks, store attachments separately, and route messages through rules before your app processes them.
04
Authentication and DMARC visibility
Use DKIM, SPF, DMARC, return-path alignment, and parsed DMARC reports to reduce spoofing risk and catch unauthorized senders.
05
Suppressions by default
Keep hard bounces, complaints, unsubscribes, and manual blocks close to the send pipeline so privacy-sensitive workflows do not repeatedly contact recipients who should be excluded.
06
Clear processor documentation
Link your legal and procurement reviews to the DPA, subprocessors page, privacy policy, data retention docs, and provider comparison material.
Start with one request.
The public API uses explicit resources and familiar JSON. Move from a first request to production without changing integration models.
Read privacy alias docscURL: create a privacy alias ready
curl -X POST https://api.postscale.io/v1/shield/aliases \
-H "Authorization: Bearer ps_live_..." \
-H "Content-Type: application/json" \
-d '{
"forward_to": ["user@example.com"],
"description": "marketplace:buyer-481"
}'Further reading
01
Masked Email API
Add product-native aliases and forwarding addresses to protect user inboxes.
Read more02
Inbound Email API
Process incoming messages as signed webhooks with parsed metadata and attachment links.
Read more03
EU-hosted email API GDPR comparison
The DPA, subprocessor, and transfer-safeguard questions teams should ask email providers.
Read more04
Why masked emails are the future of online privacy
The case for masked addresses as a product feature rather than an inbox-only consumer tool.
Read more05
Data Processing Agreement
Review Postscale's standard GDPR DPA for vendor assessment and procurement.
Read more06
Subprocessors
Review the documented service providers used to operate Postscale.
Read moreFrequently asked questions
What is privacy-focused email infrastructure?
It is an email platform design that treats addresses, message metadata, inbound content, attachments, suppressions, and authentication signals as sensitive product data, not just delivery logs.
Does Postscale replace a consumer mailbox?
No. Postscale is application email infrastructure for sending, receiving, forwarding, and processing product email. It is not a Gmail, Outlook, or Proton Mail replacement.
How do masked email aliases improve privacy?
A masked alias lets your product communicate with a user while hiding the user's real inbox. If an alias is leaked, abused, or no longer needed, it can be disabled without changing the user's real address.
Where should legal teams start?
Start with the DPA, subprocessors page, privacy policy, and the EU email API GDPR comparison. Engineering should review retention, webhook signing, suppressions, and domain authentication at the same time.
Build the email workflow your product needs.
The free tier includes everything required to evaluate the API. No credit card required.
Create a free account