Privacy Policy

This Privacy Policy explains how Openly Email (“we”, “us”, or “our”) handles personal information when you use our visual email-building service, including our website, editor, and related features (the “Service”).

Openly Email is currently operated by Dilan Xeres, ABN 71 537 119 514, a sole trader in Victoria, Australia, trading as Openly Email. Contact us at support@openly.email.

Openly Email is an Australian software-as-a-service product currently offered as a free beta.

Openly Email lets you compose emails on a drag-and-drop canvas, apply brand styling, generate copy and images with AI features, store projects in a library, export HTML, and send test emails. You can create an account or, in limited cases, keep projects in your browser.

This policy applies to information we handle when you visit the public website, create an account, or use the Service.

Account information. When you sign up with email we collect your email address and password, and we send a verification email before you can sign in. If you continue with Google, we receive the email address and profile details Google shares with us for that sign-in. We do not see your password in usable form; it is handled by our authentication provider.

Project and library content. If you use the Service while signed in, we store the emails you build and related library items you save. That can include text and layout, uploaded images, brand-kit inputs (such as a website, logo, or colours), folders, tags, colour palettes, and draft wizard or one-shot sessions.

Local drafts. If you are signed out, project data may remain only in your browser’s local storage on that device until you import it to an account.

AI inputs and outputs. If you use AI features, we process the prompts and selections you submit and the copy or images the Service returns so we can provide those features. Openly does not use your prompts or outputs to train AI models. Prompts and outputs are processed by our AI providers only to provide the feature you requested, under their own business or API terms, which may differ. We do not control, and do not promise, how those providers use that data.

Communications. If you send a test email, we process the destination address and the compiled email content for that send. We also process email addresses used for account verification and password reset. If you contact support or send feedback, we process the message, optional screenshot, any contact email you provide, and basic technical context such as the page you were on, your viewport size, and your browser user agent.

Technical information needed to run the Service. This includes authentication session data, usage counters used to apply beta limits, and, when you are signed in, interface preferences such as colour theme. We do not operate a separate analytics or advertising product.

We use personal information to operate, secure, troubleshoot, and improve Openly Email. That includes creating and maintaining your account, storing and syncing your projects, running AI and media features you choose to use, sending account and test emails, applying usage limits, and communicating with you about the Service.

We do not sell your personal information. We do not use it for advertising. We do not send marketing emails unless you have consented.

We use other companies to help us run the Service. They only receive what is needed to perform their role for us.

Vercel hosts the application. Supabase provides authentication and stores account, project, library, usage, feedback, and related records. Cloudinary stores uploaded and generated media, including optional feedback screenshots. Resend delivers account emails, verification and password-reset messages, test emails you send, and support messages.

Vercel AI Gateway routes AI requests to model providers so we can return a result. Copy and support-chat features currently use OpenAI models by default. Image generation currently uses Black Forest Labs models by default. If you use stock image search, the search query is sent to Pexels when that feature is configured. If you sign in with Google, Google processes the information needed for that sign-in. If you choose a Google Font, your browser or a recipient’s email client may request that font from Google.

We may also disclose information if required by law, to protect the Service or our users, or as part of a restructure or sale of the business, where permitted.

Signed-in project and account data is stored on our hosting and database providers. Signed-out drafts may remain on your device.

Those providers process information in the countries described under Overseas disclosure.

We keep account content while your account is active, or for as long as we need it to provide the Service.

If you delete your account in Settings, or ask us to delete it, we remove active account data, associated projects, uploaded and generated media, and related records within 30 days where practicable. Encrypted backups may be retained for up to 90 days. We may keep information required for security, fraud prevention, legal compliance, or backups. Essential security and transactional records are kept only as long as reasonably necessary or legally required.

This is a beta. We may delete beta accounts or content if we modify or discontinue the beta. We will give reasonable notice where practicable.

If we hold personal information about you, you may request access to it, correction of it, or deletion of your account and associated content, subject to any legal exceptions.

You can delete your account and associated data yourself from Settings → Account. You can also email those requests to support@openly.email. We aim to respond within 30 days.

We use cookies that are necessary to keep you signed in. Those authentication session cookies are set by our authentication provider, Supabase.

If you are signed in and change interface theme or appearance, we store those preferences in cookies named email-builder-ui-theme and email-builder-ui-appearance so the next page load can match your choice. They are stored for up to one year.

Your browser may also store project drafts and related editor state in local storage when you are signed out, or as a short-lived cache while signed in.

These cookies and storage are used to operate the Service. We do not use advertising cookies, and we do not currently use a separate analytics cookie product.

Some of the infrastructure used to run Openly Email is located outside Australia. Personal information may be stored or accessed in those places when we use the providers named above.

Supabase stores our account, project, and library data in Singapore. Their public documentation indicates that Vercel’s primary processing is in the United States, Cloudinary’s default storage is in the United States, and Resend stores customer data in the United States. AI and stock-search APIs typically process requests in the United States and in other countries where those providers operate. Pexels states that it may store or process information in the United States, Australia, Singapore, the European Union, the United Kingdom, the Philippines, and New Zealand. We do not control those locations.

The Service is intended for business and professional use. You must be at least 18 years old to use it. Openly Email is not directed at children.

We take reasonable steps to protect personal information. If a data breach occurs that is likely to result in serious harm, we will notify affected individuals and the Office of the Australian Information Commissioner as required under the Notifiable Data Breaches scheme.

If you have a privacy concern, contact us first at support@openly.email.

If you are not satisfied with how we handle your complaint, you may be able to contact the Office of the Australian Information Commissioner (OAIC).

We may update this Privacy Policy as the Service develops. The “Last updated” date at the top of this page will change when we do.

If a change is material and affects your rights or how we use your data, we will also notify you by email or an in-product notice.