Emailble Privacy Policy

Who we are

This Privacy Policy is for Emailble, the email-marketing application at emailble.com. It explains what we collect, how we use it, and how you can delete or disconnect it.

Questions: [email protected].

What Emailble does

Emailble helps a business find contacts already connected to that business, create a campaign with guided AI, send through email providers the business connects, and keep useful history with each person.

Emailble is not a consumer social app. It is used by people who sign up for a workspace to run email campaigns.

Information you give us

When you create an account we store your name, email address, password or session credentials, and workspace name.

If you subscribe or top up the wallet we store billing records from Stripe, such as customer id, subscription status, and payment amounts. We do not store full card numbers.

You may add contacts yourself, import a CSV or Excel file, or connect a business source. We store the contact fields you provide or that the source returns, such as email, name, company, phone, language, and subscription status.

You may save sending-provider credentials, API keys, and similar secrets so Emailble can send on your behalf. Those secrets are encrypted before they are stored.

Google user data we access

If you choose Connect Gmail, Emailble asks Google for the gmail.readonly scope. This is optional. The rest of Emailble works without it.

With that permission Emailble can read your Gmail profile email address and the From, To, Reply-To, and Date headers of messages in Inbox and Sent. We request message metadata only. We do not request drafts, spam, or trash. We do not store Gmail message bodies, attachments, or full email content.

We use that Google user data only to find names and email addresses already present in your own mail, show them for your review, and save the contacts you keep in your Emailble workspace. That is Contact Discovery.

We store an encrypted Google refresh token so we can sync again until you disconnect. We also store the Gmail address you connected and the last sync time.

How we use Google user data

We use Google user data only to provide and improve this Contact Discovery feature for your workspace.

We do not sell Google user data. We do not use it for advertising, retargeting, credit decisions, or lending. We do not give it to data brokers or information resellers.

We do not use Google Workspace APIs or Gmail data to develop, improve, or train generalized or non-personalized AI or machine-learning models.

How we share, transfer, or disclose Google user data

We do not transfer or disclose Google user data to third parties except as needed to run Emailble for you, to follow the law, or to protect the service.

Infrastructure that may process workspace data, including extracted contacts after you save them, includes our database host, object storage for images you upload, and the email providers or verification services you connect. Those parties receive only what that feature needs. They do not receive your Gmail refresh token or raw Gmail headers for their own use.

Campaign AI uses text you type or approve in Emailble. It does not send Gmail message bodies to an AI provider, because we do not store those bodies.

Other Google services

Emailble may call Google Cloud Translation to translate product interface strings. That is separate from Gmail. It does not read your inbox.

Cookies, sessions, and campaign tracking

We use a session cookie so you stay signed in, and a language cookie if you change the site language.

When you send a campaign, Emailble may record opens, clicks, and unsubscribes so you can see what happened with each recipient. Some mail apps block open tracking. A missing open is not treated as proof that delivery failed.

How we protect data

Traffic to Emailble uses HTTPS. Gmail tokens and other provider secrets are encrypted at rest. Access to a workspace is limited to signed-in members of that workspace.

No method of transmission or storage is perfectly secure. If we become aware of a breach that affects you, we will contact you at the email on your account where the law requires it.

How long we keep data, and how you delete it

We keep account, contact, campaign, and billing records while your workspace is active, and for a limited time afterwards if we must keep invoices or security logs.

You can disconnect Gmail in Emailble. That deletes the stored refresh token and stops further Gmail access. You should also revoke Emailble at https://myaccount.google.com/permissions.

You can delete individual contacts in Emailble. To delete your account and remaining workspace data, email [email protected] from the address on the account. We will delete or irreversibly de-identify personal data unless a longer period is required or permitted by law.

When a retention period ends for a given record, we delete or destroy it.

Your choices

You do not have to connect Gmail. You can import contacts or add them by hand instead.

You can stop a Gmail sync, change the blocked-sender list, or disconnect the inbox at any time.

Children

Emailble is not directed at children under 16. We do not knowingly collect personal information from children.

Changes

If we change how Emailble uses Google user data, we will update this page before the new use begins. The date at the top is the last update.

Contact

Emailble — https://emailble.com

Privacy requests: [email protected]