Who we are
Email Template Examples runs the website https://emailtemplateexamples.com/. In this policy, "we" means Email Template Examples.
You can reach us about privacy at info@emailtemplateexamples.com.
What the site does
- Template library. 258 free HTML email templates. You can preview them and copy their HTML without an account.
- Free account. Adds the editor, saved templates, custom templates, image uploads, a wishlist, .html and .zip exports and share links.
- Blog and contact form. The blog has no comment form.
The site does not send email for you. You copy or download the HTML and use it in your own email tool.
Sign-in and the shared Firebase project
We use Google Firebase Authentication for sign-in. You can use Google or an email address and a password.
This Firebase project is shared. It is also used by EmailFinderOnline (emailfinderonline.com). The project name is "emailfinderonline", and you may see that name in the Google sign-in window. This means:
- Your login record at Firebase sits in that shared project. It holds your email address, your name, a Firebase user ID, your sign-in method and, for email sign-ups, your password. Firebase holds the password. We do not.
- The same Firebase login can sign in on both sites.
- Firebase sends the emails that confirm your address and reset your password.
- Your templates, wishlist, exports and plan are stored in the database of this site only. Signing up here does not create an account in the EmailFinderOnline database. That happens only if you also sign in there.
Data we collect
When you have an account
Sign-in creates a WordPress user in our database. For each user we store:
- Your email address and your name.
- A random login name and a random password. Neither is built from your details, and you never use them.
- Your Firebase user ID, your sign-in method (Google or password), if your email is confirmed and when, the date you signed up and your last login time.
- Google sign-in: the web address of your Google profile photo. We store the address, not the image. Your browser loads the image from Google when it shows your avatar.
- Your plan.
- How many exports you used this month, and a log of exports of your own templates: which template, the format and the time.
- Your saved and custom templates: the title, the content, the library template it came from, the dates, and the share setting with its link code.
- Your wishlist: which templates and when you added them.
- Images you upload: the file, its size, its width and height, and the date. When we save a JPG, PNG or WebP file we make a new copy, so details such as camera data or location do not stay in it. GIF files stay as you uploaded them.
- Images you upload: the file, its size, its width and height, and the date. When we save a JPG, PNG or WebP file we make a new copy, so details such as camera data or location do not stay in it. GIF files stay as you uploaded them.
In your browser
The editor can keep an unsaved draft in your browser storage. It stays on your device. See the Cookie Policy.
When you write to us
The contact form asks for your name, your email address, a topic and your message. We save the message as a private record in the site admin area, then email a copy to our team mailbox. The record also holds your user ID if you are logged in, a keyed hash of your IP address for abuse checks (not the address itself) and whether the email copy went out.
When you visit any page
- Server logs: your IP address, the time, the page address, the answer code, the size of the answer, the page you came from and the browser you use.
- Rate limits: to slow down abuse of sign-up, sign-in and contact, we count attempts per IP address. The count is stored under a hash of the IP address. The editor counts your actions under your user ID.
- Google Analytics: see Why we use it and the Cookie Policy.
- Google Fonts: many template previews load fonts from Google. See Who receives data.
When someone opens an email built from our HTML
Copied HTML and .html exports load their images from our server. When a person opens that email, their mail app may ask our server for those images, and our server log records that request like any other visit. Images you uploaded work the same way: they are stored on our server and have public web addresses, so email apps can load them. Anyone who has the address of an image can open it. The addresses are long and random and we do not list them anywhere. Images you uploaded work the same way: they are stored on our server and have public web addresses, so email apps can load them. Anyone who has the address of an image can open it. The addresses are long and random and we do not list them anywhere. Many templates also link to Google Fonts. A .zip export includes the images, so you can host them yourself.
Payments
Payments are not open. Pro and Studio show "Coming soon". We take no payment and hold no payment data.
Why we use it
- To run your account and the tools you ask for. The legal basis under GDPR and UK GDPR is our contract with you.
- To keep the site safe and stop abuse (logs, rate limits, hashes). The legal basis is our legitimate interest in keeping the service safe.
- To count visits and improve the site (Google Analytics). It runs on every page for every visitor and sets the Analytics cookies listed in the Cookie Policy.
- To answer your messages. The legal basis is our legitimate interest in replying to you, or our contract with you.
We do not send marketing emails. We do not use your data for automated decisions that have a legal effect on you.
Where data is stored
The site runs on a DigitalOcean server in Frankfurt, Germany. Google may process data in other countries, including the United States. Its own policies explain the safeguards it uses for transfers.
How long we keep data
- Account, plan, wishlist, export log: until the account is deleted.
- Uploaded images: until you delete them in Your images or the account is deleted. If you delete an image, emails you already sent lose it.
- Saved and custom templates: until you delete them or the account is deleted. A deleted template stays in Recently deleted for 30 days, so you can restore it. A daily job then removes it.
- Server logs: 14 days.
- Rate limit counters: up to 1 day.
- Google Analytics: Google Analytics keeps this data for the period set in our Analytics account, which Google limits to 2 or 14 months.
- Contact messages: we have no fixed period, and they are not removed when an account is deleted. Ask us to delete yours.
- Database copies: we copy the database by hand before big changes. The copies have no fixed deletion date, so deleted data can stay in a copy for longer than the periods above.
Deleting your account
Deleting an account is by request today. There is no self-service button. The Delete account button on your Account page leads to our contact form, or you can email info@emailtemplateexamples.com. Our team then deletes the account by hand.
Deleting the account removes your WordPress user, your saved and custom templates, your uploaded images, your wishlist and your export log. It also deletes your login record at Firebase. Because that project is shared, the same login then stops working on EmailFinderOnline too.
Your rights
Under GDPR and UK GDPR, you can ask to see your data, get a copy, correct it, delete it, limit how we use it, or object to our use of it. You can also complain to your data protection authority.
Under US state privacy laws such as those of California, you may have the right to know what we hold, to delete it, to correct it, and to opt out of any sale or sharing of it. We do not sell your data.
How to use these rights: email info@emailtemplateexamples.com from the address of your account. There is no self-service export on the site.
On your Account page you can see your name, email, sign-in method, plan and usage.
Security
The site runs over HTTPS. We check every sign-in token on our server. Other users cannot open your private templates, and share links use long random codes. Firebase holds passwords. No system is fully secure, so we cannot promise that data will never be exposed.
Children
The site is made for people who build emails. It is not made for children and we do not knowingly collect their data. We do not check age at sign-up. If you think a child has given us data, write to us and we will delete it.
Changes to this policy
If what we do with data changes, we update this page. The date at the top shows the last change.