This Privacy Policy explains what information InboxPilot (the “Service”) collects, how we use it, and the choices you have. It covers two distinct roles: InboxPilot as the controller of your account data, and InboxPilot as a processor of the recipient data you send through the platform on your behalf.
When you create a workspace we collect your organization name, physical mailing address, your name, work email and a securely hashed password. We also store operational data such as your sending domains, connected sending accounts (with secrets stored server-side and masked in the UI), API keys (hashed), billing status and audit logs of key actions.
To send your campaigns, the Service stores the contact lists, consent status/source/timestamp, templates and message content you provide, plus per-message delivery events (sent, delivered, bounced, complained, opened, unsubscribed). This data belongs to you; we process it only to operate the Service and never sell it or use it to send our own marketing.
We use account and recipient data to render and deliver your email, enforce compliance controls (consent checks, mandatory unsubscribe, bounce/complaint suppression, domain authentication), meter usage against your plan, provide the deliverability dashboard, secure the platform, and meet legal obligations.
If enabled, the Service may include a transparent tracking pixel and/or link wrapping to record opens and clicks. You are responsible for disclosing tracking to your recipients where required by law.
We use a single, essential session cookie to keep you signed in. We do not use third-party advertising cookies in the application.
We rely on a small number of providers to run the Service, including cloud hosting and database infrastructure, and payment processing by Stripe, Inc. (card details are handled by Stripe and never stored by us). These providers process data only as needed to provide their service to us.
We retain account and message data for as long as your workspace is active and as needed to provide the Service, comply with legal obligations, resolve disputes and enforce agreements. Suppression records (unsubscribes, complaints, hard bounces) are retained to protect recipients even after other data is deleted.
Passwords are hashed, API keys are stored only as hashes, sending-account secrets are stored server-side and masked, and traffic is served over HTTPS. No system is perfectly secure, but we apply reasonable technical and organizational measures to protect your data.
Depending on your jurisdiction, you (and the recipients whose data you control) may have rights to access, correct, export or delete personal data. Because recipient data is controlled by you, requests from your recipients should be directed to you as the sender; we will assist you as your processor. You can delete your account data by contacting us through your workspace administrator.
Your data may be processed in the countries where we and our providers operate. Where required, we rely on appropriate safeguards for cross-border transfers.
We may update this Privacy Policy from time to time. Material changes will be reflected on this page with an updated date.
The Service is operated by InboxPilot. Privacy questions, or requests to access, correct, export or delete your account data, can be sent to [email protected] or raised through your workspace administrator.