1. Who these terms are with
These terms are between Md Shaiyad and Hardil Singh, trading as Posthaste (“we”, “us”), reachable at [email protected] — and the individual or organisation using it (“you”). By creating an account or sending a message through the API, you accept them.
If you are accepting on behalf of an organisation, you confirm you are authorised to bind it.
2. What we provide
A transactional email API. We accept messages you submit, sign them with a DKIM key associated with a domain you have verified, deliver them directly to recipient mail servers from infrastructure we operate, and make the resulting delivery records available to you.
We do not guarantee that any particular message will be accepted by a receiving server or placed in an inbox. Inbox placement is decided by the receiving provider and is outside our control. We are responsible for delivering correctly and telling you truthfully what happened — not for another operator’s filtering decision.
3. Your account
You are responsible for keeping API keys secret, for all activity carried out with them, and for revoking any key you believe has been exposed. Keys are shown once at creation and stored only as a hash, so we cannot recover one for you.
You must give us an accurate contact address and keep it current. We use it for service notices, including anything urgent about your sending.
4. Acceptable use
Your use of the service is subject to the Acceptable Use Policy, which forms part of these terms. In summary: transactional mail to recipients who asked for it, operational announcements only to your own users with a recorded consent source, no marketing, no purchased or scraped lists, nothing unlawful or deceptive.
Sending on shared infrastructure means your behaviour affects other customers. That is why this is a contractual term rather than guidance.
5. Sending limits
Accounts have a daily sending cap that adjusts automatically based on recent sending behaviour, described on the deliverability page. The cap is a deliverability control, and we may adjust it — including downward — where sending patterns put the reputation of our infrastructure at risk.
6. Suspension
We may suspend sending, immediately and without notice, where:
- the Acceptable Use Policy is being breached;
- your sending is materially damaging the deliverability of our infrastructure;
- we are required to by law or by an upstream network operator; or
- an account appears compromised.
Where we suspend, we will tell you why and what would need to change, and we will restore service once it has. Suspension for suspected compromise is a protective measure, not a penalty.
7. Fees
Plans and prices are on the pricing page. Paid plans are billed in advance for the period stated. Fees are exclusive of any tax that applies, which is added where required.
Every payment produces an invoice, issued to the name and country you give at checkout, emailed to you and available in the dashboard. An invoice cannot be altered once issued and is kept as a tax record rather than on a deletion clock — see the privacy policy.
The free tier is provided at no charge and requires no card. We will give at least 30 days’ notice by email before any price increase takes effect for an existing account.
8. Your content
The content of the messages you send remains yours. You grant us only the rights needed to provide the service: to store, process, transmit and sign your messages, and to retain delivery records.
Message bodies are retained on a shorter clock than delivery records — 30 days on every plan — and the full set of retention periods is in the privacy policy.
While we hold them, message bodies are encrypted at rest, and a member of our staff cannot open one without giving a written reason that is recorded and emailed to the account owner verbatim. That is a term of this agreement, not a feature we may quietly withdraw; the detail is in section 3 of the data processing addendum and on the security page.
9. Availability
We aim for continuous availability but do not currently offer a contractual uptime commitment, and we will not pretend otherwise: a service level agreement will be offered when we can stand behind one rather than as a line in a contract.
A message accepted by the API is durably recorded before we acknowledge it, so a subsequent outage delays delivery rather than losing the message.
10. Liability
Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be limited.
Subject to that, our total liability arising out of or in connection with these terms is limited to the fees you paid us in the 12 months before the event giving rise to the claim, or US$100 where no fees were paid. We are not liable for loss of profit, loss of business, loss of goodwill or indirect or consequential loss.
We are specifically not liable for the consequences of a receiving mail server refusing, filtering or delaying a message, where we delivered it correctly and recorded the outcome.
11. Termination
You may close your account at any time. We may terminate on 30 days’ notice, or immediately for a material breach of these terms or the Acceptable Use Policy.
On termination you may export your delivery records for 30 days, after which we delete account data on the schedule in the privacy policy.
12. Changes
We may update these terms. For material changes we will give at least 30 days’ notice by email, and continuing to use the service after they take effect means you accept them. If you do not, you may close your account and we will refund any unused prepaid fees.
13. Governing law
These terms are governed by the laws of India, and the courts of that jurisdiction have exclusive jurisdiction over any dispute.
14. Contact
Questions about these terms: [email protected].