Last updated July 25, 2026. Questions: hello@inbin.dev.
Inbin receives email on your behalf and turns it into structured data. That means we process the content of emails you route to us. This page says exactly what we collect, where it goes, and how long it lives.
Account data: your email address, used for sign-in (magic links) and operational notices. We do not store passwords.
Inbound email: the full content of emails sent to your Inbin inbox addresses, including headers, body, and sender information. This is the product working as intended. Route only mail you have the right to receive and process.
Extracted data: the structured JSON our extraction produces from those emails, shaped by the schema you define.
Operational logs: API request metadata (IP address, timestamps, key prefix), webhook delivery attempts, and an audit trail of mutating API calls.
We don’t sell your data. We don’t use your email content to train models. We don’t read your inboxes except when you ask us to debug something, or when required to investigate abuse.
Raw emails are kept 30 days, then deleted automatically. Extracted events are kept 90 days on the Free and Builder plans, 365 days on Growth and Scale. Audit logs are kept 90 days. Deleting an inbox stops new mail immediately; deleting your application removes its data on the same retention schedule.
Inbin runs on established cloud infrastructure in the United States. Email content is processed by an LLM provider solely to perform the extraction you configured. A current list of subprocessors is available on request at hello@inbin.dev. Traffic analytics are cookieless.
Email hello@inbin.devto access, export, or delete your data. We answer within a few days, usually faster. If you’re in a jurisdiction with statutory rights (GDPR, CCPA), those apply and we honor them.
If this policy changes materially, we’ll email account holders before the change takes effect.