Privacy Policy

Sendpository handles data in two distinct roles, and the difference matters for your rights and ours:

• Your account data - the details you give us to run your account. Here we are the controller.
• The email you send - recipients and message content that you pass to the API. Here we are a processor acting on your instructions. You decide who is contacted and why; we deliver it.

Account data. Your name, email address, a hash of your password, and your billing details - legal name, address, GSTIN and PAN where you provide them. Payments are handled by PhonePe; card, UPI and bank details go to them directly and never reach our servers.

Sending data. For each message: sender, recipients, subject, size, delivery status and timestamps, plus the events a mailbox provider reports back - delivered, bounced, complained. The message body is stored too, so that you can read back what was actually sent when you are debugging. Attachment contents are never stored - they are passed to the mail servers and discarded, and only the filename, type and size are kept.

Open and click tracking. Both are off unless you turn them on, for your account or for a single message. When they are on and a recipient opens the message or follows a tracked link, we record the time, the link followed, and the IP address and user agent (browser or mail app) of whatever made the request. These belong to your recipient, not to you, and are kept as part of the delivery log for the period below. If you turn tracking on, telling your recipients about it is yours to do.

Technical data. IP addresses, user agents and timestamps for logins and API requests. We keep these to detect abuse, enforce rate limits and investigate security incidents - the same records that let us tell your traffic from an attacker’s.

Website and app analytics. Google Analytics 4 runs across the site and signed-in app to measure page views and general usage, including a small number of onboarding actions. It may use first-party cookies and collect pseudonymous usage, browser, device, and approximate location information. Google Ads measurement is also configured on selected public pages. Vercel Web Analytics runs on the homepage and provides aggregate, anonymous traffic statistics. We do not intentionally send email contents, recipients, or API keys as analytics events.

Session replay. Microsoft Clarity runs across the site and signed-in app. It records how a page was used - pointer movement, clicks, scrolling, and the structure of the page as it changed - so that we can see where the product confuses people, together with the same pseudonymous browser, device and approximate location information as above. Signed-in sessions are labelled with your account identifier and plan name, not with your email address. Message bodies, the mail you receive, and API keys are masked before anything leaves your browser, and text typed into form fields is never recorded.

Mail you receive. If you set up a receiving address, the messages sent to it: sender, recipients, subject, headers, the text and HTML bodies, and the name, type and size of each attachment. Attachment contents are not stored. This is mail other people wrote to you, held for you to read and passed to the webhook endpoints you configure - we do not use it for anything else.

Developer Rewards. If you take part, the Developer Rewards email you give us (which can differ from your account email), whether you confirmed it, and a record of each step towards a reward - integration, payment, validation, and the reward sent. We use it only to run the campaign, send the reward, and prevent it being claimed improperly; that includes comparing sign-in addresses and billing details between participating accounts. We do not use it for marketing.

• To provide the service - delivering your email is the contract we have with you.
• To bill you and issue the tax invoices Indian law requires.
• To keep the platform secure: rate limiting, abuse detection, and investigating incidents.
• To understand general site and app usage and measure the performance of our marketing.
• To tell you things you need to know about your account - service notices, security alerts, billing.
• To meet legal obligations, including retaining tax records.

We do not sell your data. We do not use the contents of your messages for advertising, and we do not use them to train machine-learning models.

We share data only with providers who help us run the service:

• Neon - managed PostgreSQL hosting for the application database.
• PhonePe - payment processing. They receive the payment amount and order reference, and handle payment instruments under their own privacy policy.
• Our mail infrastructure - the servers that put your messages on the wire and receive delivery reports back.
• Google - website analytics and advertising measurement tags on our site and app. Google processes data under its own privacy terms.
• Vercel - anonymous, aggregate website analytics on the homepage.
• Microsoft - session replay and heatmaps (Clarity) on our site and app. Microsoft processes data under its own privacy terms.

We may also disclose data where the law requires it, or to establish or defend a legal claim. We will tell you when we are permitted to.

• Message bodies: 30 days, then erased from the delivery record. The record itself survives, so your history stays auditable after the content has gone.
• Delivery logs and metadata - recipients, subject, status, events, and the IP address and user agent recorded by open and click tracking: 90 days, then deleted outright.
• Mail you receive: bodies and attachment details for 30 days, then the message itself for 90 days, on the same windows as mail you send.
• Attachment contents: never stored. Only the filename, type and size are kept, alongside the message.
• Account and billing records: kept while your account is open, and afterwards for as long as tax and accounting law requires.
• Security logs: kept for a limited period for abuse and incident investigation.
• Website analytics: retained by Google and Vercel under their own retention settings and policies; these analytics are not part of the email delivery log.
• Session recordings and heatmaps: retained by Microsoft under Clarity's own periods - currently 30 days for recordings, 13 months for heatmaps and for any recording kept as a favourite - and then deleted by them, backups included.
• Developer Rewards records: kept for the campaign and afterwards for as long as tax and accounting law requires for the rewards given, since a gift card is a business expense we must be able to account for.

When you close your account, sending stops immediately and your data is deleted at the end of these periods, except where we are legally required to keep it.

• Everything travels over TLS, and the API is HTTPS-only.
• Passwords are stored as one-way hashes; we cannot read them.
• API keys are stored only as hashes - the key is shown once, at creation, and never again.
• DKIM private keys are encrypted at rest with AES-256-GCM, and are never exposed to the browser.
• Access to production data is restricted to those who need it to operate the service.

No system is perfectly secure. If a breach affects your data, we will notify you and the relevant authorities as the law requires.

We use a single essential cookie to keep you signed in. It is HTTP-only, and it is not used for tracking or advertising. Google Analytics may set first-party analytics cookies to distinguish browsers and sessions. Google Ads measurement is configured on selected public pages and may use advertising cookies. Vercel Web Analytics does not use third-party cookies or store cross-site visitor identifiers. Microsoft Clarity sets its own cookies to recognise a returning browser across visits; in the EEA, the UK and Switzerland it waits for a consent signal before setting any, and without one it counts each page view separately and stores nothing. You can manage or clear cookies through your browser; blocking analytics cookies can limit the analytics we receive.

You may ask us to give you a copy of your account data, correct it, or delete it. You may also object to processing or ask us to restrict it. Much of this you can do yourself: your billing details are editable in Settings, your sending history exports to CSV, and closing your account from Settings → Billing stops processing and starts the deletion clock above. For anything else, write to billing@sendpository.com and we will respond within 30 days.

If your request concerns email you received from a Sendpository customer, we are the processor, not the controller - contact the sender, whose address is on the message. We will pass such requests on where we can identify the customer.

Data is stored on infrastructure that may be located outside India. Where data crosses a border, we rely on our providers’ contractual safeguards to keep the protection equivalent.

Sendpository is a developer tool for businesses. It is not directed at children, and we do not knowingly collect data from anyone under 18.

We will post any change to this policy here and update the date above. Material changes are notified by email. Questions, or a request about your data, go to billing@sendpository.com - see also Contact Us.