Skip to content

Privacy policy

Last updated: 2026-10-29.

Who we are. colding.app is operated by OpenWings Automação Comercial Ltda., CNPJ 63.852.648/0001-06 ("colding", "we"). Our data protection contact, encarregado under the LGPD and data protection officer under the GDPR, is Gustavo Salomé Silva, at [email protected].

1. What colding does

colding gives people and their agents tools to send and read email from connected mailboxes. It checks addresses, runs campaigns, exchanges warmup mail and brings replies into one inbox. Your app can also send transactional email, such as a receipt or sign-in link, through a connected mailbox or a sending service's SMTP login. Your providers handle delivery. Hosted inboxes and sending from domains hosted by us are not open to customers today.

You choose which external agent or app gets access through an API key or an approved sign-in. It can read and change workspace data within the permissions and limits you grant. Data it reads goes to that app, under its operator's terms. colding does not run a language model for you or use your mail to train one. Our own account emails go through Amazon SES, as section 8 explains.

2. Whose data we handle

  • Customers: people with an account who use the console or connect an app to the service.
  • Contacts: people in a customer's lists and people who receive the customer's app email.
  • Correspondents: people who write to a connected mailbox whose mail appears in the inbox.
  • Warmup partners: participating mailboxes that exchange warmup email, and their owners.

We are the controller for customer account data: we decide how to use it to run the service. For contacts and correspondents, the customer decides why to hold and use the data. We are their processor and act on their instructions under the Data processing agreement.

3. Customer data we collect

  • Account details: your email address, display name, language, workspace memberships and roles, and each workspace's time zone. Continuing with Google also gives us your Google account ID, name, email address and profile-photo link.
  • Mailbox details: the address, provider, settings and stored login of each connection. A login may be a password, app password or access token from Microsoft or Google. We encrypt it with a key our email-link service does not hold. We also keep where reading reached, errors and warmup status. A warmup hold belongs to the mailbox address and follows it if it is connected in another workspace.
  • Activity: each send's recipient, subject, final message, Message-ID and outcome; API request kinds, IDs and times; API-key hashes; webhook addresses and delivery records; and the audit log of who changed what.
  • Plan and billing: the plan, usage counts and Stripe's customer, subscription and checkout IDs. Stripe collects card details on its own payment page. Card numbers do not pass through our systems.
  • Request and sign-in logs: IP addresses and user agents, which identify the browser or program making the request. We use them to protect accounts and investigate problems.

We use this data to run the service, enforce limits, prevent abuse, help you and send alerts. We do not sell it or use it to train models.

4. Signing in and connecting a mailbox

We open accounts by hand today. Ask for access at [email protected]. Your account uses an email address and password.

You can continue with Google instead. That asks for your name, email and profile photo (openid, email and profile), then opens the existing colding account with that address. It does not read email or connect a mailbox. An address with no existing account is refused while sign-up is closed. To remove this access, remove colding at https://myaccount.google.com/permissions. This does not disable your account password.

Connecting a mailbox is separate. You choose the mailboxes, or a key you gave setup permission chooses them in your name. SMTP sends email and IMAP reads it. Gmail and Google Workspace can use an app password; other providers, such as Zoho, use their SMTP and IMAP logins. We use those logins to send, read and file mail. Warmup mail goes in its own folder. Read marks and moves you make in our inbox are applied at the provider too.

A sending service can connect with SMTP alone. We can send through it but cannot read its inbox. Replies arrive wherever that address receives mail, and later bounce or complaint reports reach us only when the service's report connection is set up.

Microsoft 365 and personal Microsoft accounts (Outlook.com, Hotmail, Live or MSN) connect through Microsoft's sign-in, with the same permissions:

  • openid, email and profile: your sign-in identity.
  • User.Read: your name and mailbox address, to connect the right mailbox.
  • offline_access: to keep access after you close the tab, until you disconnect.
  • Mail.Send: to send email from that mailbox.
  • Mail.ReadWrite: to read mail, apply read marks and moves, and file warmup mail.

This access covers only the mailbox you connect, not other mailboxes, your calendar, contacts or files. Some organizations require admin approval first. For a work or school account, remove colding at https://myapps.microsoft.com. An admin who approved it for the organization must remove that approval in Enterprise applications in the Microsoft Entra admin center. For a personal account, remove consent at https://account.live.com/consent/Manage. Disconnecting a Microsoft mailbox deletes our stored token and ends our access. Microsoft still lists your consent until you remove it on the page for your account type.

Where Google sign-in for mailboxes is offered, a Google Workspace mailbox can connect with gmail.modify, permission to read, send and organize its mail. We use it for the messages you or your authorized tools send, inbox reading, read marks and moves. Section 13 applies. Warmup never uses the Gmail API: a Google mailbox can warm only through an app-password connection. Remove access at https://myaccount.google.com/permissions.

Use Disconnect on the mailbox's console page to remove a connection. We delete its stored logins at once, hide its messages and delete them at the next hourly cleanup. For a Google sign-in connection, we also ask Google to revoke our access. You can revoke an app password at your provider too.

Section 13 sets the extra rules for data from Google APIs.

5. Email, contacts and files we store

  • Contacts: the email addresses, names, companies and custom fields the customer adds; which campaign steps went out; replies, bounces, spam reports and opt-outs; and suppression records that stop further mail.
  • Open and click tracking, when the customer turns it on: the time, email or link and kind of program making the request. We store the requesting IP as a keyed hash, using only the network part for IPv6. The readable IP appears in request logs, not tracking records. An open is recorded at most once an hour for the same email, IP and program kind; a click has the same bound for each link. We keep each tracked link's destination and judge whether a person or a program made the request. A send keeps the first human open and click, their counts and the first program open. This judgment is not proof that someone read the mail.
  • Transactional email: the recipient, message, sending deadline if set and outcome. We do not track opens or clicks. Bounces, spam reports and requests to stop can leave suppression records under the rules below.
  • Address checks: the address, result (valid, risky, invalid or could not tell), reason, answering service and time. Each contact also keeps its latest result.
  • Received mail: headers, text and HTML up to 512 KB per part, and the thread. We do not store incoming attachments from connected mailboxes. On download we fetch the file from the provider and pass it to you.
  • Outgoing files you upload: the file, name, type, size, uploader and SHA-256 hash, a code calculated from its contents to check that the file arrived unchanged. We do not inspect the file's contents.
  • Warmup: the exchanged messages and signals such as where they landed and whether the partner replied.

For customer account data, our legal basis is the contract with you (LGPD art. 7, V; GDPR art. 6(1)(b)). You choose the basis for your contacts and correspondents, which may be legitimate interest in business correspondence (LGPD art. 7, IX; GDPR art. 6(1)(f)). Our safeguards include suppression checks before sending, an opt-out line on by default in campaigns, unsubscribe headers on campaigns and new direct outreach, and the Acceptable use policy, which requires a way to stop campaign mail. Transactional email follows your relationship with its recipient, usually your contract with them. It has no opt-out line. An outreach opt-out stops outreach, not requested app email; a bounce or a stop request that covers app email can stop that too.

6. How long we keep things

  • Sends: kept while the workspace exists, with no age limit yet, except warmup's (below). Each mailbox's count of what it sent each day, warmup or not, goes after 120 days.
  • Messages: kept while their mailbox is connected. Disconnecting a mailbox hides its messages at once, and the next hourly clean-up deletes them.
  • Warmup: each warmup email as it was sent, where it landed and what the other mailbox did with it: 120 days, then pruned. A few stay longer. One that landed in spam stays until the sender's warmup is stopped, because it still slows that mailbox's warmup. One the other mailbox still has to move to its warmup folder stays until it does, while that mailbox keeps checking for mail at least once every 7 days. One we may still find in a mailbox that stopped checking for mail, the other mailbox's copy or the sender's own copy in its Sent folder, stays until that mailbox checks again or is disconnected. Every copy stored in a connected mailbox, the sender's Sent copy and the partner's, is that mailbox's mail, kept as messages are.
  • Contacts: until the customer deletes them or the workspace. A suppression record outlives the contact, because it is the only way to keep honouring an opt-out. It holds the address, how and when it was added, any note and end date the customer gave it, and which campaign, email or reply it came from, nothing else. When the workspace is erased, a recipient's own opt-out stays as a hash, as the Workspaces item says.
  • Opens: 90 days after the open, then pruned. The first open and first click a person made, their counts, and when a program first opened it are part of the send and go with it.
  • Clicks: 90 days after the click, then pruned. Tracked links: 365 days after the email was sent, then pruned with any clicks still on them; after that the link no longer leads to its page.
  • Address checks: 30 days after the check finishes, then pruned, with the batches that ran them. A contact keeps its latest result while the contact exists. How many checks a workspace used each month, a count with no addresses in it, is kept 13 months.
  • Audit log: 90 days. Event stream: 24 hours.
  • Webhook delivery logs: 30 days.
  • What our mail servers' log says about an email: when an email leaves through a mail server of ours, the log of that server says what the receiving server answered, with the recipient's address. We keep that 40 days in our database and 14 days on the mail server, then it is pruned.
  • A campaign's history (what happened to it, such as a pause or a lead left out): 90 days. Alerts, read or not: 90 days.
  • Alerts to our staff: the daily list of people who started using colding, with each one's email address, is kept 2 days. Other staff alerts keep only the latest one about each thing.
  • Repeated API requests: when a request carries an Idempotency-Key, we keep its answer 24 hours, so a retry gets the same answer.
  • Contact imports: the file and its cells are deleted once its contacts are added, or 24 hours after the upload if they never are. The counts of what it did are kept 7 days.
  • Files you upload to attach to an email: kept while an unsent draft or a scheduled or waiting email uses the file. Once no unsent draft or waiting email uses it, it can no longer be used 7 days after it was uploaded or last used, and the next hourly clean-up deletes it. You can delete an unpinned file sooner. Opening or listing it doesn't keep it longer. Each send's record keeps the file's name, type, size and hash, without the file itself, and says when the stored file is gone. Its upload link works 15 minutes. A deleted file stays in the backups below until the last copy that holds it expires.
  • Contact exports: the file is made while it downloads and never stored. Its link works 10 minutes and is deleted within the hour after.
  • Files of mailboxes: each row's passwords are deleted once that mailbox is connected or fails. The rest of the file is deleted 7 days after it was sent.
  • Mailbox confirmation codes: a code works 30 minutes, then is deleted. The request without its code is kept 7 days, to look into mail that never arrived.
  • Unsubscribe links: a link works 365 days after the latest email that carried it, and is deleted 30 days after that.
  • Stripe's messages about subscriptions. For each one we keep its id and kind, the subscription it is about, when Stripe sent it and what we did with it. We keep them 90 days. Some stay longer: the ones from about a day before a workspace's latest checkout opened, and every one after. They stay until that workspace's subscription starts or it opens another checkout.
  • Bounce and complaint reports from a sending service, for a send-only mailbox whose owner turned them on. For each one we keep what kind it was, what we did with it, the email it matched and when it came in, never the service's words or an address. We keep them 30 days.
  • Workspaces: the owner can request deletion in Settings, under Delete workspace. New sending stops at once: campaigns and warmup pause, scheduled mail is canceled, and keys and pending invitations are revoked. An email already being sent can still go out. Incoming mail and the owner's export remain available. Erasure starts after 30 days. The owner can cancel during that waiting period; canceling does not restart sending or restore revoked access. Erasure deletes connections, logins, contacts, campaigns, messages, sends, drafts, uploaded files, checks, webhooks, keys, members, invitations, download links and the audit log. It runs in steps, then checks again for anything that arrived meanwhile, until a check finds nothing. Exports stop once erasure starts. The requester gets an email when it finishes, and their account is not deleted by this request. Only these limited records remain: keyed hashes of recipients' own opt-outs for 3 years; mailbox warmup holds and decided appeals until their term ends, or 1 year for a block or rest with no end; and workspace restrictions for 2 years. These hashes have no readable address or workspace link. They let us honor the same opt-out, hold or restriction when an address or owner returns. The workspace record retains its ID, dates, plan, Stripe customer and subscription IDs and accepted AUP version, without its name or readable address. Warmup evidence gathered by other workspaces about this workspace is deleted. Evidence this workspace gathered about other workspaces stays without a link to the erased workspace.
  • Your account: request deletion in Settings, under Delete your account, by typing your sign-in email. First transfer ownership of your workspaces or request their deletion. Account deletion waits until you own no remaining workspace, including any awaiting erasure. You can cancel before it starts. The worker removes your memberships, revokes your keys and invitations, and deletes your sign-in, name, email, alert preferences and alerts. Your work in another workspace stays there without your name. If your address was banned, a keyed hash of it remains for 2 years to enforce the ban if you return. We send one completion email; the account no longer holds your readable address. The request keeps your account ID, not your address, and is deleted 30 days after completion or cancellation.
  • Request logs, which hold each request's IP address and user agent: 180 days.
  • Sign-ins: to protect accounts from stolen passwords, the sign-in service keeps the IP address and user agent of each sign-in with its session, until you sign out or the account is deleted. It also keeps the IP address of each sign-in in its sign-in history, and of each request made to it in its own log. Neither has a time limit yet.
  • Backups: a copy of the database every night. New copies are kept up to 8 days on our server and up to 31 days in a private Cloudflare R2 bucket. We do not encrypt new backup files before uploading them. Cloudflare encrypts the files in storage. We also keep a full copy of the database each night, plus every change made since, in the same bucket. Those changes reach the bucket within minutes. New copies of this kind are kept for up to 8 days. Copies past these limits are deleted only after a new backup succeeds, so when a backup fails they stay longer. Older encrypted copies and the database changes needed to restore them are not deleted automatically. Data deleted from the service can remain in those older copies until we remove them.

7. Your rights (LGPD and GDPR)

You can ask whether we process your personal data, access or correct it, request deletion or anonymization, or ask for a portable copy. You can object to processing based on legitimate interest, withdraw consent when it was the basis and complain to your supervisory authority (in Brazil, the ANPD).

A workspace owner can download its data in Settings, under Your data. The file contains contacts, labels, segments, campaigns, sent and received messages, drafts, suppressions, saved replies, stored-file metadata, connection settings, key and webhook settings, members and the audit log. It excludes passwords, mailbox sign-in tokens, key hashes, webhook signing secrets and warmup partners' addresses. Warmup exports include daily counts and the owner's appeals. Uploaded files themselves are not included. Emails remain as sent, with working links where they have not expired, and the webhook address is included. Protect the export as carefully as your mailbox. You can generate 1 files a day, resetting at 00:00 UTC. Each download link works for 60 minutes and 3 downloads at most. The Contacts page also exports contacts as a spreadsheet. Section 6 explains account and workspace deletion. To request your own account data, write to [email protected].

If a customer's outreach reached you, use its unsubscribe link or reply asking to stop. You do not need an account. For other data requests, write to [email protected]. We pass the request to the customer who controls the data and help them answer it. We answer within 15 days.

8. Who else touches the data

For each company below that works for us, we say what its agreement states about moving data to another country. Where an agreement names no mechanism, we say that and name none. We read these agreements on 4 October 2026. On 7 October 2026 we read them again for what they say about the ANPD's clauses, and read Stripe's for the first time. On 21 October 2026 we read AWS's. The sub-processors page lists the same companies with what each receives and where it works, and the data processing agreement is our own with you.

  • Your mail providers (Google, Microsoft, Zoho or the SMTP host you chose): every message is sent and received through them, under their terms. They are your providers, not our processors.
  • Stripe: takes payment for paid plans. We send the workspace ID. You enter your email, card and billing details on Stripe's payment page. We receive billing references and payment status, not your card number. Its data processing agreement, last updated 28 September 2026, sends the data to Stripe, LLC in the United States, and to Stripe's affiliates and sub-processors in other countries, under its data transfers addendum, last updated 18 November 2025. The addendum names the Data Privacy Framework, the EU's standard contractual clauses, the UK's international data transfer addendum and a Swiss version of them. Its section 11 applies the ANPD's standard contractual clauses to data that goes from Brazil to a country with no adequacy decision from the ANPD: the exporter is the party to the agreement with Stripe, and the importer is Stripe, LLC. For part of its work Stripe decides the purposes on its own, and there it is a controller, not our processor.
  • Our own checking server: to check an address, a server of ours asks the mail server that receives mail for it whether the address exists, and hangs up before any message is sent. It never sends mail. It receives the address and the names of that domain's mail servers. It keeps no copy of the address and never writes it in its logs. Its logs name the mail server it asked and what that server answered, with any address taken out. The address's own mail server sees the question. For now we rent this server from netcup (netcup GmbH, Germany), and it sits in netcup's data center in the United States.
  • MillionVerifier (GBD Software as a Service Private Limited Company, Hungary): checks whether an email address can receive mail, for the addresses our own checking server can't answer. It receives the address only. Under its data processing agreement it keeps the address in its cache up to 7 days, and in its backups until they are replaced. We keep each check 30 days after it finishes. That agreement names no transfer mechanism. It says that where a transfer is subject to Chapter V of the GDPR, MillionVerifier will use a lawful transfer mechanism required for it, and that it signs no country-specific transfer agreement unless the law also requires one for its own processing. It does not mention the ANPD's clauses or the LGPD.
  • Amazon SES (Amazon Web Services, Inc., United States): delivers mail about your account (sign-in links, password resets, alerts, notices and the codes that confirm a mailbox's address) and receives your address, your name and the message itself. Campaign mail never goes through it. It works in AWS's us-east-1 region, in the United States. AWS's service terms let AWS, or companies it uses, store and scan each message to block spam, phishing and viruses. If our email to you bounces for good, or you mark it as spam, Amazon SES keeps your address on our account's list of addresses it sends nothing to, until we take it off. AWS's data processing addendum applies the EU's standard contractual clauses to data the GDPR covers that goes to a country outside the EEA with no adequacy decision from the European Commission, unless AWS has adopted binding corporate rules or another recognised standard for those transfers. AWS's service terms add a UK addendum and a Swiss one. None of these texts mentions the ANPD's clauses or the LGPD, and AWS's page on Brazil's law names no mechanism for data that leaves Brazil, so this policy names none for it.
  • Supabase (self-hosted on our own server): authentication and the database. Nothing leaves our server for this.
  • Cloudflare: DNS, the hosting of our web front-ends, and storage for the nightly backup copies (section 6). A security check on the pages where you sign in, create an account or ask for a new password (Cloudflare Turnstile) is built but not switched on yet. When it is switched on, your browser will load the check from Cloudflare, which will receive your IP address, your browser's user agent and the fingerprint of its encrypted connection, to tell a person from a program and to improve the check. Our sign-in service will then ask Cloudflare whether the check passed, sending your IP address with the question. Cloudflare receives nothing for this today. Its data processing addendum applies the EU's standard contractual clauses to a transfer from the EEA that needs them (Module Two, or Module Three when the customer is a processor), with the UK addendum and a Swiss version of them. It also says Cloudflare complies with the EU-U.S. Data Privacy Framework and holds Global CBPR and Global PRP certifications. It does not mention the ANPD's clauses or the LGPD.
  • netcup (netcup GmbH, Germany): the server that runs the service and holds its database, in the United States. Its data processing agreement names no transfer mechanism. It says the customer decides where the data is processed.

The ANPD's clauses and the EU's are annexes to our own data processing agreement, for the data of our customers' contacts. Of the companies above, only Stripe's addendum adopts the ANPD's clauses, and none of the others has signed them with us.

Our servers are in the United States, so what we hold about you is stored there, wherever you are.

Data we receive from Google follows the extra rules in section 13.

9. Security

We encrypt stored mailbox logins and keep that key out of the service that handles email links. We store API-key hashes, use short-lived session tokens and limit server access to the operator. The database requires a password for outside connections. Encrypted connections use TLS; a recipient's mail server that cannot encrypt an address-check request receives that question unencrypted. Incoming HTML appears in an isolated frame without scripts. If a data breach affects you, we notify you and the authority as the law requires.

10. Children

colding is not for people under 18, and we do not knowingly hold accounts for them.

11. Emails we send

About your account. We open each account by hand and answer your request from a person's address. Account email is part of the service and keeps coming while the account exists. It carries sign-in links and password resets, and the codes that confirm a mailbox's address go to that address. It also tells a workspace's owner and admins when the owner asks to delete it, 7 days and 24 hours before it is deleted, and if the owner cancels the request. When you delete your account, we send you one last email once that is done.

Alerts. Alerts show in the console's bell and on its Alerts page. You choose in the console which kinds also reach your inbox by email: "Mailbox trouble", "Campaign trouble", "A new reply" and "Requests for you". Alerts that come close together share one email: after an alert email about a workspace, the next one for that workspace waits 30 minutes. It groups the alerts and links to the console for the rest. You get at most 25 alert emails in any 24 hours, from all your workspaces together; past that, the alerts wait in the console.

News and tips. We send none today. If we ever start, only people who say yes to them will get them, and every email will carry an unsubscribe link.

We don't sell your email address.

12. Data processing agreement

For contacts and correspondents, the processing agreement between the customer (controller) and us (processor), as the LGPD and GDPR art. 28 require, is the data processing agreement. It applies to every workspace without a signature. The sub-processors page is part of it, and so are its two annexes: the standard contractual clauses of the ANPD and of the EU.

13. Google user data

This section covers information we receive from Google APIs: your Google account's name, email address and profile photo when you continue with Google, and the mail of a Google Workspace mailbox you connect by signing in with Google (both in section 4). A mailbox connected with an app password goes through Google's mail servers, not its APIs.

colding's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In practice:

  • We use it only to provide and improve the features you see in the console.
  • We pass it to another party only to provide those features, for security, or to comply with the law. In a merger or sale of the business, we pass it on only after you agree.
  • We never use it for advertising, never sell it, never use it to decide on credit or lending, and never use it to train AI models.
  • No person reads it unless you agree to it for specific messages, it is needed for security, the law requires it, or it has been combined and anonymized for our internal operations.

14. Changes

We will announce material changes by email to customers and by a dated note at the top of this page.