Terms of service

1. Who this is between

This agreement is between the operator of EmailTimer.App ("we", "us"), and the person or company that opens an EmailTimer.App account ("you"). If you open an account for a company, you are confirming you may agree to this on its behalf.

You accept it by creating an account, or by putting an EmailTimer.App image URL into an email.

2. What the service does

We render images on request. You build a template, publish it, and put a signed image URL into your email. When a recipient's email client fetches that URL, we render an animated GIF countdown, a PNG with your merge values in the pixels, or both in one image.

Two things about email clients are outside our control and inside our documentation. Apple Mail pre-fetches images at about delivery time, and third-party testing reports it holds the copy for two to three days. Gmail's proxy caches per recipient, for a lifetime Google does not publish, so a re-open can be served from the cached copy. Outlook on Windows shows only the first frame of a GIF. We tell you this before you buy, we show you what each client will render in the editor, and we design the output so the first frame is always a correct image. What we cannot do is change another company's cache.

3. Your account

Keep your password and your API keys to yourself. You are responsible for what happens under your account, including what the people you invite do. Tell us at support@emailtimer.app if you think a key or a session has been taken.

You must be able to enter a contract, and you must not be someone we are barred from dealing with under applicable sanctions or export rules.

4. Plans and opens

Each plan includes a number of image fetches a month. A fetch is one request we answer with a rendered image, which is not the same as a human opening your email: a proxy may fetch once and show it many times, and a client may re-fetch. The counting rule is in the documentation and it is the same rule your invoice uses.

Going over the included amount does not interrupt anything. We email you at 80 percent and at 100 percent of the included fetches. Past 110 percent, new renders carry a small corner watermark until you move to a bigger plan. Delivered emails never break because of usage.

The free plan is limited to 3 published images at a time and the bundled fonts.

5. Payment, tax and invoices

Paid plans renew automatically, monthly or annually, until cancelled. Annual billing is charged as ten months for twelve.

Payments in dollars are taken by Stripe. Payments in rupees are taken by Razorpay, by UPI Autopay, net banking eMandate or an Indian card. A subscription cannot be moved between the two processors: it has to be cancelled and started again in the other currency. We never see or hold your card number or your UPI handle.

Prices are as published on the pricing page on the day you subscribe, exclusive of tax unless the page says otherwise. Tax is shown at checkout. If we change the price of your plan we email you at least 30 days before your next renewal, and you can cancel before it.

Overage above the included amount, where a plan charges for it, appears on the next cycle's invoice rather than as a separate charge.

6. Refunds

If a plan does not do what the pricing page says it does, tell us within 30 days of the charge and we refund it. We do not pro-rate unused opens on a cancellation, because the renders have already happened.

7. Cancellation

You can cancel from the dashboard at any time, in either currency. Cancelling takes effect at the end of the period you have paid for, and your images keep rendering until then. You can choose to end it immediately instead and give up the rest of the paid period.

When a paid subscription ends, the account goes back to the free plan and its limits.

8. Unpaid invoices

If a payment fails, the processor retries it and we email you. Your images keep rendering throughout. Nothing changes about what your recipients see while the retries are running.

When the retries are exhausted the workspace is suspended. A suspended workspace's images show a plain EmailTimer.App fallback image instead of your design, in emails that have already been delivered. This is the one state in the product that changes what a recipient sees, which is why it only happens for an unpaid balance after the retries ran out, or after an abuse review. It is never caused by going over your plan. Settle the balance or write to support and it is lifted.

9. Acceptable use

Do not use the service to render or deliver:

• content that is illegal where you or your recipients are, or that infringes someone's rights;
• deadlines you know to be false, or claims of scarcity you know to be untrue;
• anything designed to impersonate another company or to phish;
• anything aimed at children under 16;
• images for lists you have no permission to mail.

Do not attack the service: no attempt to read another tenant's data, no probing for holes outside your own workspace, no scraping the render endpoint, no reselling raw rendering capacity as your own product, and no circumventing quotas, rate limits or the signature on a URL. Testing your own workspace for security problems is welcome; see the security page for how to report what you find.

If you are a third party who believes a rendered image infringes your rights or is otherwise unlawful, write to support@emailtimer.app with the image URL, what the problem is, and how to reach you. We will look at it, and we can disable a specific image.

10. Who owns what

You own everything you bring: your images, fonts, Photoshop files, copy, templates and lists. You also own the rendered output we produce from them, including the GIFs and PNGs delivered to your recipients.

To provide the service, you give us permission to store, copy, render, cache and serve that material, and to keep it in backups, for as long as you have an account and for the retention periods in the privacy policy. That permission exists for no other purpose. We do not use your material to promote ourselves without asking you first, and we do not use it to train models.

We own the software, the templates in the gallery, the engine, the documentation and the EmailTimer.App name. Your subscription is permission to use the service, not a transfer of any of that.

You are responsible for having the right to use the fonts you upload. Font licences differ on whether a web service may render with them, and we cannot check that for you.

11. Availability

There is one commitment here that we hold ourselves to: an image request returns a valid image, never an error status. When something fails, the render falls back to your template's fallback image, then your workspace default, then a plain branded image, so a delivered email never shows a broken image icon.

Beyond that, the service is provided as it is. We do not offer an uptime percentage or service credits today. The status page says exactly what is monitored and what is not, and we would rather publish that than a number we cannot stand behind. Maintenance that we expect to interrupt anything is announced by email beforehand.

12. Data protection

The privacy policy says what we hold and for how long. Where you send us personal data about your subscribers, the data processing addendum applies and forms part of this agreement.

13. Suspension or termination by us

We can suspend or close an account for an unpaid balance after retries, for a breach of section 9, or where we must by law. Except where the law or an ongoing attack prevents it, we will tell you what the reason is and what would fix it.

You can stop using the service at any time. Either of us can end this agreement for a material breach the other has not fixed within 30 days of being told about it.

14. What happens to your data when it ends

Your usage data can be exported as a CSV from the analytics screen at any time while the account is open, and you should take a copy before you close it.

When you ask us to delete the account, we delete the records, the uploaded files and the published template documents within 30 days of the request, and the cached recipient records with them. Per-request rows age out with their daily partitions within 30 days. Database backups are kept for 30 days, so a deletion works its way out of the backups within 30 days of the deletion itself. The audit log entries about billing are kept where tax law requires them, and nothing else is.

Published URLs stop rendering your design once the account is deleted and fall back to a plain image. Delete an account with campaigns still in flight and that is what the recipients of those campaigns will see.

15. Changes to these terms

We can change these terms. If a change affects you, we email account owners at least 30 days before it takes effect and change the version and date at the top of this page. If you do not accept a change, cancel before it takes effect. Carrying on using the service after that date means you accept it.

16. Liability

Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot be limited by law.

Otherwise, neither of us is liable to the other for lost profits, lost revenue, lost data or indirect losses, and our total liability for any claim is limited to what you paid us in the 12 months before the claim.

You agree to cover us against a third-party claim that arises from what you rendered or who you sent it to, where the claim is about your content, your list, or your rights to use them.

17. General

If a clause is unenforceable, the rest still stands. Neither of us may transfer this agreement without the other's consent, except that we may transfer it to a company that acquires the business. Failing to enforce a clause once does not waive it. These terms, the privacy policy and the DPA are the whole agreement between us.

18. Contact

support@emailtimer.app for anything about the service, and privacy@emailtimer.app for data protection.

Change log