Privacy policy

Foi Enviado! is operated by Leonardo de Oliveira, registered under CNPJ 53.961.037/0001-42, based in Barueri, São Paulo, Brazil. Under Brazil's General Data Protection Law (Law 13.709/2018), this is the data controller.

Contact for any matter in this policy, including exercising your rights: contato@foienviado.com.

We collect the data you provide and the data received from the integrations you connect. Messages, events and metrics may be received or updated automatically while the integration is active.

• Registration. Email and password. The password is never stored as text: what stays in the database is the result of a hash function, and not even we can read it.
• Profile. Name, profile type, content goal, desired posting frequency, your Instagram @ and profile picture. It is what you answer at the start and can edit later.
• Content you create. Images, titles, captions and the text of your pieces, published or not.
• Instagram connection. An access token issued by Meta, your professional account identifier and your @. The token is what authorizes publishing on your behalf.
• WhatsApp connection. A token issued by Meta, your WhatsApp Business account identifier and your number's identifier. This is what authorizes sending and receiving messages on your behalf. The token is encrypted the same way as the Instagram one.
• Telegram connection. The identifier of your conversation with the bot, when you turn on this channel. It lets the bot know who it is talking to.
• Conversations and attachments. Documents, images, videos and audio sent during customer service, and messages exchanged on Instagram Direct and WhatsApp: the text, date, direction and the original response Meta sends. Stored with them are the phone number and identifier of the person who wrote. All of this is explained in the section about who talks to you.
• Your conversation with the assistant. What you write on the Assistant screen and what it answers, with the date and the account in which each request was made. It is stored so the conversation can continue where it left off, and you can delete all of it there with the clear button.
• The workspace's AI key. The API key of the artificial intelligence provider that the owner or an administrator connects so the assistant can work, along with the chosen provider and model, the last 4 characters of the key, its status (working, refused or out of credit) and who registered it. The key is encrypted, and the section on its protection explains how.
• Sending lists. When you send a campaign through WhatsApp, the chosen numbers and the status of each send are stored.
• Post metrics. Reach, likes, comments, saves and shares, read from the Instagram API, along with Meta's original response and the date of the reading.
• Subscription and billing. Details of the plan purchased, subscription status, customer and subscription identifiers, and billing records. When paying through Stripe, card details are entered in Stripe's fields; the app does not receive the full card number.
• Schedules. The queue of what is set to publish, the chosen time and the record of each attempt, including failed ones.

We store invitations, member identification, roles, channels, departments, declared presence and conversation assignment records. This data allows us to organize service and control access.

The owner and administrators manage the team. Supervisors and operators access channels and conversations according to their permissions. Private service attachments follow the conversation's permissions. Whoever manages the workspace must review access and remove it when it is no longer needed.

If you turn on notifications, we store the device subscription, the delivery address, technical keys and your preferences. Sending goes through the browser's or operating system's notification service.

Depending on your preferences, the alert may show the contact's name and a preview of the message, including on the lock screen. You can turn off notifications in the app or in your device settings.

Subscription and billing data is used to carry out the purchase and manage access to the service. No data is collected for resale, advertising profiling or training third-party artificial intelligence models. The Assistant screen sends part of your content to the AI provider the workspace connected so the model can answer, and this has its own section below.

• Registration and profile exist so you can log in to your account and so the app knows who it is writing for. The legal basis is the performance of the contract between you and Foi Enviado!
• Content exists because it is the product: without storing the piece, there is nothing to publish or reopen later.
• The token exists to publish and read metrics on your behalf. Without it, Meta's API refuses any call.
• Metrics exist to show how each post did. They come from Meta and are not calculated by us.
• Conversations exist because the inbox is the product: without storing the message, there is nothing to answer and no history to understand what was discussed.

Everything above is about you. This section is about someone else: the person who sends a message to your Instagram or WhatsApp. They never created an account here and never read this policy, and even so their data passes through this system.

What is stored about that person: the text they wrote, the phone number in the case of WhatsApp, the identifier Meta uses for them, the display name when Meta sends it, the date of each message, and Meta's original response as it arrived.

You are responsible for this data. The conversation is between you and your audience, and Foi Enviado! is the tool that stores and displays it. In the terms of Brazil's General Data Protection Law (LGPD), you are the controller of this conversation and Foi Enviado! is the processor. In practice, this means three things:

• A request for access or deletion from someone who wrote to you comes to you, not to us. If you need technical help to handle it, write to contato@foienviado.com.
• Foi Enviado! uses the content of these conversations only to show it to you and let you reply. There is no sale, no profiling and no artificial intelligence model training. They are also not sent to the AI model on the Assistant screen: it has no access to your inbox.
• WhatsApp Business rules apply above everything else: free-form messages can only be sent within 24 hours of the person's last message, and outside that window only Meta-approved templates. Anyone who asks to stop receiving messages must stop receiving them.

The database and files are on Supabase, on servers in the São Paulo region, in Brazil. The application is hosted by Vercel.

Communication with Meta goes through its infrastructure, which is international. This means that when you connect Instagram and publish, there is an international transfer of data to Meta Platforms. AI, payment, email and notification features may also involve processing outside Brazil, depending on the infrastructure of the suppliers used.

The token deserves its own paragraph because it is the most sensitive data here: whoever has it can publish on your profile.

• It is encrypted with AES-256-GCM before entering the database. Anyone looking at the table would see scrambled text.
• The key that decrypts it is not in the database or in the browser. It lives only in the server environment.
• The table that stores it has row-level security turned on and no read rule. In practice, no browser can read it, not even yours. Only the server process that publishes can.
• The screens never receive the token. What they read is a view that says only whether the account is connected and what the @ is.

Whoever has the AI key can spend the credit in your provider account. That is why it gets the same protection as the Instagram token, and a bit more.

• It is encrypted with AES-256-GCM before entering the database, using its own encryption key, separate from the one used for social network tokens. The key that decrypts it lives only in the server environment.
• No browser reads or writes the key directly in the database. Only the server writes it, after confirming that the requester is the owner or an administrator of the workspace and testing the key with the provider.
• Once saved, the key never appears on screen again, not even to whoever registered it. What you see are the last 4 characters, the provider and the model.
• The key test uses only the model list query, which spends no credit, and talks only to the official addresses of the listed providers. There is a limit on attempts per hour.
• The key is not written to error logs. When the provider refuses the key, we keep only the response code and an excerpt of the stated reason, with any part that looks like a key hidden.

Data is shared with the suppliers needed to operate the service:

• Meta Platforms. Receives the content you ask to publish and returns the metrics. It is Instagram itself, and also WhatsApp Business: the messages you send and receive pass through it.
• Supabase. Stores the database, files and authentication.
• Vercel. Hosts the application and records technical access data, such as IP address, in the normal operation of a server.
• Stripe. Processes payments and manages subscriptions purchased this way. It receives the email, the workspace name and the data needed for payment and billing.
• The AI provider chosen by the workspace. It runs the model behind the Assistant screen, using the workspace's own API key: Claude (Anthropic), ChatGPT (OpenAI), Gemini (Google), OpenRouter, DeepSeek, Mistral, Grok (xAI) or Groq, depending on the providers available on the screen. It receives what it needs to answer, and the next section lists each item.
• Anthropic. Provides the artificial intelligence model for the AI mode of the Telegram bot, contracted by Foi Enviado!.

When you use the Telegram bot, Telegram also receives the messages in that conversation, because it is what carries them.

Authentication, invitation and notice emails are sent through Resend, which receives the recipient and the content needed for delivery. WhatsApp group features use an infrastructure with the Evolution API for connection, participants and sending messages.

When you turn on notifications, there is also communication with your browser's or operating system's push service.

Beyond these uses necessary for operation, your data is not sold or traded. If the law or a court order requires handing it over, this will be complied with, and you will be notified whenever notification is permitted.

The Assistant screen works with the model of the AI provider the workspace connected, using the workspace's own API key. Without a connected key, the assistant is unavailable. The AI mode of the Telegram bot works with an Anthropic model. This means that part of what is in your app leaves here and goes to the provider's servers, with each message you send on that screen.

The list below was read from the code, not estimated. This is exactly what is sent:

• Your entire brand profile: what you sell, who you talk to, the core message, the tone of voice, what the product does not do and the words you have banned.
• The name of the workspace and the @ of the account you are working in.
• What you write in the conversation, and its last 24 messages, so the assistant remembers what has already been agreed.
• The result of what it looks up at your request: the title and time of what is scheduled, and reach and like numbers when you ask how something did. Workspace operating data and the structure of the automations consulted may also be sent, including flow texts, conditions and settings.

What is not sent, and this matters: your Direct and WhatsApp conversations. The assistant has no direct access to the Inbox history. If you copy messages or personal data into the assistant or into the texts of an automation it consults, that content may become part of the context sent. Credentials and tokens of connected accounts are not provided as context.

The AI providers on the list are companies outside Brazil, so using the assistant is an international transfer of data. Since the assistant uses your workspace's key, the provider's processing follows the contract between you and them, including what they do about retention and use of data to train models. Each provider has its own rules, which you can check in your account with them. On Foi Enviado!'s side, nothing you send is used to train models. In the AI mode of the Telegram bot, Anthropic states that it does not train its models on what it receives through the commercial route we use.

Using it is your choice. The whole app works without opening the Assistant screen: you can create in the studio, schedule, publish and answer messages without any of this reaching an AI provider through these flows. The AI mode of the Telegram bot also sends context to Anthropic when used.

Foi Enviado! does not use tracking cookies, advertising pixels or analytics tools. Nothing here measures your behavior for third parties.

Your login session is stored in your own browser's local storage, under the name publicador-sessao. This keeps you logged in when you reload the page. Clearing the site's data erases this session and logs you out.

Content, service and settings histories are kept to allow use of the service. Some categories have their own cleanup routines; there is no single period that applies to all data.

Conversations with no activity for more than 30 days are archived, not deleted. Archiving does not erase messages or attachments.

The AI key is stored while it is connected to the workspace. Removing the key, or deleting the workspace, erases the key from our database. Technical records of attempts to connect a key, used for the hourly limit, are erased after one day.

Deletion of a workspace is scheduled for 30 days after the request. Deleting the account, deleting the workspace and cancelling the subscription are different procedures.

The record of each sale and each charge (date, amount, currency, exchange rate, fees, invoice number and the tax details provided at payment, such as name, email, country and tax ID) is kept for the period required by tax and accounting law, even after the workspace or account is deleted. This record is not used for any other purpose.

Removing records from the database does not guarantee the simultaneous removal of all files. Legacy files, backups and records kept by suppliers require specific verification when handling the request. We do not promise instant deletion of all copies.

The LGPD gives you rights that apply regardless of what is written here. You may request, at any time:

• Confirmation that your data is being processed
• Access to the data we have about you
• Correction of incomplete, inaccurate or outdated data
• Anonymization, blocking or deletion of unnecessary data
• Portability of data to another supplier
• Information about who we share data with
• Withdrawal of consent and deletion of the account

You can correct your name, goal and frequency yourself on your account screen. For everything else, including access, portability and deletion, write to contato@foienviado.com. We may request information to confirm your identity. Requests for confirmation and access may be met by an immediate simplified statement or a full statement within 15 days, subject to the applicable rules. For other requests, we will inform you of the steps, applicable deadlines and any reasons preventing immediate fulfillment.

To request deletion of your account or personal data, write to contato@foienviado.com from your registered email. After verifying your identity and the scope of the request, we will inform you of the procedure, the data covered and any necessary retention. We do not promise immediate removal of all records and files.

The owner can request deletion of a workspace in Settings, confirming its name. The workspace is deactivated and its permanent deletion is scheduled for 30 days later. Until the end of that period, the request can be cancelled. The app prevents deleting the last active workspace; to close the whole account, use the contact above.

Cancelling the deletion request does not automatically turn channels, automations, schedules or team access back on. Removing a member also does not erase the workspace's service history.

To stop an integration without deleting the history, disconnect Instagram or WhatsApp in Settings. This removes the authorization stored for that connection.

To delete the AI key, go to Settings, AI Assistant, Remove. This erases the key from our database; in your provider account it continues to exist until you deactivate it there.

If the request comes from someone who talked to a customer of the platform, whoever is responsible for that conversation must guide and assist the data subject. We can provide technical help at contato@foienviado.com.

Deleting data here does not erase posts or messages already delivered on external platforms. Cancelling the subscription is also not the same as requesting data deletion.

Foi Enviado! is not intended for people under 18 and does not knowingly collect data from children and adolescents. If we identify such an account, it is removed.

When this policy changes, the effective date at the top changes with it. If the change significantly alters what is collected or who it is shared with, you will be notified by email before it takes effect.