AutoMailed platform
Privacy policy
How AutoMailed handles account, workspace and connected-service information, and how to contact us about your data.
Last updated:
Who operates AutoMailed
AutoMailed is operated by LLC Swish, registration number 40203501541, Anninmuizas bulvaris 2B, Riga, LV-1067, Latvia. Contact info@automailed.com for privacy questions and requests.
This policy covers the AutoMailed platform. A business using AutoMailed to run its own website, store or communications is responsible for its own customer privacy information. For data that business puts in its workspace, contact the business as well as us when appropriate.
Information used by the platform
Account and workspace information includes names, email addresses, company details, team roles, preferences, sign-in information and security records. Workspace content can include contacts, messages, attachments, business tasks, approvals, execution results, files, website content, code and prompts that users provide or authorize us to obtain.
Connecting a mailbox can provide account identity, messages, recipients and attachments. Depending on the permissions you grant, AutoMailed can read, send and update mailbox content to provide the features you use. Google sign-in and Google mailbox access are separate connection purposes.
Connecting Google Ads or Meta Ads provides profile identity, authorized advertising accounts, permissions, account currency and time zone, and related campaign information. Meta connections can also provide authorized Facebook Pages and advertising image assets. We store connection credentials to make authorized requests; we do not ask you to give AutoMailed your provider password.
Payment and commerce features can process connected-account identifiers, transaction and order information, amounts and payment status. Stripe and the other connected payment services handle payment processing under their own terms. Technical records can include request and error information, IP addresses, device or browser details and action timestamps.
Why information is used
We use information to provide accounts and workspaces, synchronize connected services, deliver requested AI assistance, prepare and execute authorized tasks, publish requested content, provide payment reporting, support users, and investigate failures or abuse. Required account details support the service contract; optional connections require your authorization. Security and support serve legitimate operational interests; legal records support applicable obligations. Where processing requires consent, you can withdraw it.
Content supplied to AI features can be sent to the model or execution service used for that feature, including OpenAI for configured AI functionality. The relevant content can include your prompt and the workspace context or files used to carry out your request. Avoid supplying information you are not authorized to share.
Connected accounts and information sharing
Information is shared with the services needed to carry out a requested feature: for example, email recipients and a mailbox provider when sending email, Google or Meta when managing authorized advertising, Stripe when using connected payment features, and the hosting, storage or AI service handling the feature. Workspace members can access information according to their permissions. Publicly publishing content makes that content available to its audience.
Google API information, including information derived from it, is subject to Google's API Services User Data Policy and applicable Limited Use requirements. Connecting an advertising account does not grant permission to use Gmail information to serve advertisements or build advertising audiences.
Our service providers may process information outside the European Economic Area. Contact us for information about the providers and locations involved in your service and applicable transfer safeguards. We may also disclose information when legally required or necessary to investigate security incidents.
Storage, security and retention
The platform uses workspace access controls, security records and encryption for stored integration credentials. These measures do not remove the need to protect your own accounts and choose appropriate team permissions. Session and security cookies support sign-in, connection verification and request protection.
We retain information for the service purpose and applicable legal, security or dispute needs. Retention depends on the record and request; disconnecting an integration is not a request to delete all account history, tasks or backups. Ask us about deletion and any records that must remain.
Your choices and privacy requests
You can disconnect supported integrations and request access, correction, deletion, restriction or portability of personal data, or object to applicable processing. Rights depend on the circumstances. Contact info@automailed.com; we may verify identity and authority. You can complain to Latvia's Data State Inspectorate or another competent supervisory authority.
See the data-deletion instructions for the difference between disconnecting an account, removing provider permissions and requesting deletion of stored information. AI suggestions do not replace your review or establish a guarantee of business results.
Changes to this policy
We update this page when the platform's data practices change. A new connection or materially different use of connected data may require further notice and authorization. Contact us if you need an earlier version or an explanation of a change.