Organic OS

Privacy Policy

Effective date: November 8, 2026

Organic OS (“we”, “us”) is a web application available at orbitaorganic.online that lets authorized operators manage content, publications, comment automations (including optional Messenger follow-ups to people who comment) and Messenger conversations (an inbox where the Page's team reads and answers messages) for Facebook Pages they administer. Organic OS is operated by 48.868.100 Patricia Carneiro Da Silva, the business responsible for the processing described here. Questions and requests: guilherm817@gmail.com.

1. Data we collect

Operator accounts. Name, email address, a hashed password, interface language, session records (including IP address and browser user agent) and an audit log of actions taken in the application.

Facebook Page connections. When an operator connects a Facebook Page through Facebook Login, we receive, through Meta's official APIs and only with the permissions the operator grants: the Page ID, name, category and profile picture, the granted permissions and Page tasks, and access tokens. Access tokens are stored encrypted in a dedicated secrets manager and are never shown in the interface. Of the Page's profile picture (the picture of the Page itself, not of the people who comment on it or write to it) we keep a small copy, refreshed about once a day while the Page is connected, and its main colors, used only to show the Page to operators in Organic OS.

Instagram accounts linked to connected Pages. When an operator connects, reconnects or checks a Facebook Page that has Instagram permissions, we read, through Meta's official APIs and with the Page's access token, the ID and username of the Instagram professional account linked to that Page, and keep them with the time of that read while the Page is connected, to show operators which account is linked, to answer comments on it and to publish on it the Reels that operators approve for it. Disconnecting the Page in Organic OS deletes them from the Page; the account's ID also stays in the records of the comments received on it (below), which are kept and deleted like the other comment records (sections 4 and 5), and the account's ID and username also stay in the records of the Reels approved for it, which are kept like the other publication records (section 4). While Instagram comments are not turned on, Organic OS may count Instagram notifications for testing, without acting on them: for each one we keep only which Instagram account it was for, its type, whether it came from that account itself or from someone else, and when it arrived, and these counts, and any copy of the linked account's ID and username made for that test, are deleted automatically within 30 days after they were last updated.

Content managed by operators. Videos, images, audio files, PDF files, captions, calls to action, offer destination links and other links, schedules, automation rules (including Messenger sequences) and ready-made inbox replies that operators create, plus the identifiers and links of the posts and Reels published through Organic OS. For Messenger, Organic OS also creates copies of videos and audio files in formats that Messenger can play. Files used in Messenger sequences are stored privately on our servers, not at a public web address; to send them in Messenger we upload them to Meta, which returns an attachment ID that we reuse for that Page. To publish a Reel that an operator approved for the Instagram account linked to a Page, we upload the approved video directly from our servers to Meta; we do not place it at a public web address. If that video does not meet Instagram's video requirements, an operator can have Organic OS create a copy of it in a format Instagram accepts, stored privately like the other files, and we upload that copy instead.

Comments on connected Pages. When comment notifications are enabled for a Page, Meta sends us new comments on that Page's content. We store the comment ID, the post ID, the commenter's app-scoped Facebook ID and the comment text. Meta may also include the commenter's name; we do not store or log it, and only count how often a name is included. Automation decision records keep at most the first 280 characters of the comment.

Comments on connected Instagram accounts. When Organic OS has Instagram comments turned on, Meta sends us new comments on the posts and Reels of each Instagram account linked to a connected Page. We store the comment ID, the post or Reel ID, the commenter's Instagram-scoped ID and the comment text, and keep and delete them as we do Facebook comments (sections 4 and 5). Meta also includes the commenter's Instagram username; we use it only to recognize the account's own comments, and we do not store or log it. We do not store the account's own comments or replies to comments. Its automation decision record keeps at most the first 280 characters of the comment.

Private replies in Instagram Direct. When such a comment matches a comment rule that the operator set to answer on Instagram, the person who commented receives one private message in Instagram Direct, at most one per comment and only within 7 days of the comment, and, if the operator chose one, a public reply under the comment. The private message is a short text that may include a button that opens an offer link that is the commenter's own: a click on it is recorded like the other offer clicks (below), and for up to 180 days after the click we also record which comment it came from, so a sale reported for that click is linked to that comment too. The ID and delivery status of these replies are kept with the comment record. Apart from the commenter's Instagram-scoped ID that we keep with the comment (above), we keep no other identifier of the person from the private message. We do not store the person's replies or other messages to that account in Instagram Direct (Meta does not currently send them to us), and Organic OS does not continue the conversation there. To have this data deleted, follow section 5 and include a link to your Instagram comment, or a link to the post or Reel with the date, approximate time and text of your comment.

Messenger conversations started from a comment. When a Page operator turns on the optional Messenger sequence of a comment rule, the person who commented receives one private reply with up to three buttons, and Meta sends us notifications about the Page's Messenger conversations.

When the private reply has buttons that continue the sequence, for every person who receives it we store a record linked to their comment: their app-scoped Facebook ID, the status of the reply and of the sequence, and the Page-scoped ID (PSID, assigned by Meta for that Page) that Meta returns when it accepts the reply, even if the person never taps or writes back. The ID and delivery status of every private reply are kept with the comment record. For every other private reply we also keep, for up to 180 days, the Page-scoped ID that Meta returns, only so that a deletion request also finds that person's conversation and offer clicks.

We keep more only about people who interact with that sequence, who ask the Page to stop automated messages or who write to a Page whose inbox is turned on (below): the time of their latest message or tap, needed to respect Messenger's 24-hour window; which buttons or quick replies they tapped at each step of the sequence; whether a message asked to stop or to resume automated messages, and the date and source of a stop request; when someone from the Page replied manually; and the IDs and delivery status of the messages the Page sent.

On Pages whose inbox is turned off, notifications about other conversations are discarded without storing anything about the person, unless the person asks the Page to stop automated messages: from then on we keep the request and the records described above, as explained in section 4. We also store Meta policy notices about the Page.

On those Pages we do not store the text of the messages people write or the files they send: each message is only classified (for example, as a request to stop, or as an operator's one-time test code), its words are counted and the type of any attachment is noted, and the text is then discarded. We do not collect or store people's Facebook names or profile pictures. Meta does not tell us whether people open a link, play an audio or a video, or open a file. When someone taps an offer button in a sequence, the link first passes through Organic OS, which records the click as described below.

Messenger inbox. An operator can turn on the inbox for a connected Page. From then on, and only for that Page, we store the Messenger conversations of everyone who writes to the Page or taps one of its buttons: the text of their messages and the titles of the buttons they tap; for any image, audio, video, file or sticker they send, its type, its name when Meta provides one and the link Meta provides to show it (we do not download or keep copies of these files); the time of each message; and the text of the Page's replies, including replies its team writes in Organic OS and replies sent through Meta's own tools, such as Meta Business Suite. We also keep which team member wrote each reply sent from Organic OS, who a conversation is assigned to, when it was marked as done, which team members have read it, and when automated messages were paused or resumed for that person. Messages sent before the inbox was turned on are not imported, and the inbox never stores one-time test codes or the conversations of an operator testing a sequence in their own Messenger.

Messages sent from the inbox are written by people on the Page operator's team; Organic OS does not write them. Organic OS can suggest one of the team's own ready-made replies, chosen by fixed rules (for example, words in the person's last message or the offer of the sequence they received), and sends it only if a team member chooses to send it. Messages from the inbox are sent only within Meta's 24-hour window, and never to someone who asked the Page to stop automated messages unless that person wrote to the Page again afterwards. In Organic OS, conversations are shown only to members of the operator's organization with the owner, administrator or editor role.

Clicks on offer links. Offer buttons in Messenger sequences open a link of Organic OS that immediately forwards to the offer's website. For each visit we record the date and time, the Page, the automation rule, the button and the offer, the post or Reel the conversation started from, and whether the visit came from a phone, a tablet or a computer, together with a random click code that we add to the offer's web address. When the person already has a Messenger conversation with the Page, the offer link in a message sent to them is their own, so for up to 180 days after a click we also record which person's conversation it came from; this lets the Page's team see in the inbox that the person opened the offer and whether a sale followed. The offer link in the first private reply to a comment is also the commenter's own: for up to 180 days after a click we record which comment it came from, so the click can also appear in the inbox once that person's conversation is linked to their comment. Offer links in tests and in messages sent before this feature are shared by everyone who received them and are not linked to a person. We do not record the person's IP address or browser user agent with the click. To limit abuse, the network address is used only for one minute, as a keyed hash in a temporary counter, and is not stored. Automated link previews are not counted. Offer links that the Page's team sends from the inbox work the same way; for them we record the Page and the offer instead of a rule, button, post or Reel.

Sales notifications from affiliate networks. When an operator connects an affiliate network (H&W Hub), the network notifies us of sales made after a click on an offer link: the click code, the order number, the commission, the currency, the product name, and the type, status and dates of the sale. We do not receive or keep the buyer's name, email address, phone number, address or other personal data; if a notification includes them, we discard them without storing or logging them. While a click is linked to a person's conversation or comment (above), a sale reported for that click is linked to it too, and the Page's team can see in the inbox the product, the type of sale, the commission and the date; we never tell the affiliate network who the person is.

Operators testing a sequence in their own Messenger. An operator can ask Organic OS for a one-time code and send it to the Page in Messenger, so that a test of a saved sequence is sent only to them. We store which Organic OS account and Page the code was created for, keeping the code itself only as a keyed hash (it is valid for 10 minutes and works once); the link between the operator's account and their Page-scoped ID on that Page, with when it was confirmed and when and why it ended; and the test conversations, with the same kind of records described above, marked as tests, sent only to the linked operator and never counted in reports.

2. How we use data

We do not sell personal data, we do not use data received from Meta for advertising or profiling, and we do not share it with data brokers.

We use the text of Messenger conversations only to show it to the Page's team in the inbox and to choose which ready-made replies to suggest. We do not sell it, we do not use it for advertising and we do not use it to train artificial intelligence models.

3. Sharing

Data received from Meta is used only as described in this policy and in accordance with Meta's Platform Terms and Developer Policies.

4. Retention

We keep data while the operator account or the Page connection is active and as needed for the purposes above. Operators can disconnect a Page at any time.

The copy of a Page's profile picture and its main colors (section 1) are deleted when an operator disconnects the Page in Organic OS, and in any case within 30 days after it is disconnected; backups made before then are deleted as described below.

Server backups are kept privately, only for recovery: a backup is made every day and each one is normally deleted after 30 days; if the backups or their cleanup stop working, older backups are kept until it is fixed, and the last seven are always kept. A copy of each daily backup is also stored with Amazon Web Services in the United States, encrypted on our server with a key that only we hold, and is deleted automatically within 30 days. Our hosting provider may also keep copies of the whole server for disaster recovery, under its own retention. When we delete data at your request, it remains only in the backups made before the deletion, isolated and unused, until those backups are deleted, normally within 30 days; if we restore one of our daily backups, we delete that data again.

Click records and sales notifications are kept while the operator account is active, for the operator's sales reports, and deleted when the operator asks us to delete them or deletes the account. The link between a click (and its sale) and a person's conversation or comment is deleted in the daily cleanup 180 days after the click, or earlier if that person's data is deleted, and a person's own offer link stops being linked to them 180 days after it was sent (it still opens the offer). From then on the click and the sale remain only in the totals per Page, post, sequence and offer, with no personal data of the person who clicked or bought.

Messenger conversation records (the Page-scoped ID, taps, stop and resume messages, and the IDs and delivery status of the sequence's messages) are deleted in a daily cleanup once 180 days have passed since the sequence ended and since the person's last message to the Page. The ID and delivery status of the private reply are kept with the comment record (section 1).

Inbox texts (the messages people send, the titles of the buttons they tap, the replies, and the type, name and link of attachments) are deleted in the daily cleanup once 180 days have passed since each message was sent or received. The other inbox records of a conversation (who it is assigned to, whether it is done, which team members have read it, and pause or resume times) are deleted once 180 days have passed since its last message, or earlier together with the person's Messenger record. Turning off the inbox or disconnecting the Page stops storing new texts; texts already stored follow the same 180-day rule. Texts and links between people and their clicks or sales that are deleted by the cleanup or on request may remain in the backups described above until those backups are deleted, normally within 30 days; if we restore one of our daily backups, we delete them again.

The daily cleanup never deletes a stop request: it is kept until you reply VOLTAR or ask us to delete it, or until the Page's operator explicitly asks us to delete all of that Page's data, stop requests included. A stop request applies to that Page in the Organic OS organization that received it. While the Page is connected, it is kept whole: the person's Messenger record on that Page (their Page-scoped ID, the date and how the request was made, and the times recorded for that conversation, such as their latest message) and, if they commented, their app-scoped Facebook ID and the record that links the request to their comment.

A Page whose access was revoked on Facebook, for example by removing Organic OS from its business integrations, still counts as connected until an operator disconnects it in Organic OS.

After the Page is disconnected, the stop request itself is reduced to a minimal record: the Page-scoped ID, a keyed hash of their app-scoped Facebook ID when we know it, the date and how the request was made, so that we keep honoring it if the Page is connected again. Apart from the copy of the Page's profile picture and its main colors (above) and the ID and username of the Instagram account linked to the Page (section 1), disconnecting deletes nothing else: the record that linked the request to their comment (with their app-scoped Facebook ID and Page-scoped ID) follows the 180-day rule above, and the comment records of section 1 stay until a deletion request (section 5).

The aggregate numbers shown to operators are calculated from these records and are not kept separately.

Test runs sent to an operator's own Messenger, with their messages, are deleted in the daily cleanup once they are 7 days old; the other records of the operator's own Messenger from testing (that their code message arrived, their taps and their conversation state) follow the 180-day rule above, and a stop request sent while testing is kept like any other.

The link between an operator and their Page-scoped ID ends when the operator removes it or links again, loses editing access, or the Page is disconnected, or 90 days after it was confirmed, and it is deleted 7 days after it ends. One-time codes are deleted 7 days after they expire.

5. Data deletion instructions

You can request deletion of your data in any of these ways:

  1. Email guilherm817@gmail.com with the subject “Data deletion request”. Include your Facebook Page name or the email of your Organic OS account. If you commented on a Page that uses Organic OS, include a link to the comment. If you received automated Messenger messages from such a Page, include the Page name and a link to the comment that started the conversation. If you wrote to such a Page in Messenger without commenting, include the Page name and the date and approximate time of one of your messages.
  2. Operators: disconnect the Page in Organic OS (Pages → the Page → Disconnect locally) and send the email in item 1 asking us to delete the related content and records. Apart from the copy of the Page's profile picture and its main colors (section 4) and the ID and username of the Instagram account linked to the Page (section 1), disconnecting alone does not delete them; we delete them on request.
  3. On Facebook, remove Organic OS from your business integrations (Settings → Business integrations). This revokes our access but does not delete your data; to delete it, also send the email in item 1.
  4. In Messenger, reply PARAR or STOP (or tap the stop button, when the sequence shows one) to stop automated messages from that Page at once. This does not delete your data; to delete it, also send the email in item 1.
  5. Operators who linked their own Messenger for tests: choose “Unlink my Messenger” (“Desligar meu Messenger”) in the “Test in my Messenger” window of a saved sequence that uses that Page, or send the email in item 1. The link stops working at once and is deleted 7 days later; it also ends on its own 90 days after it was confirmed.

We confirm the request and delete the data, except records we must keep by law, which we retain only for that purpose. Deleting a person's data on a Page also deletes their inbox conversation there, with its texts and replies, and the link between them and their clicks and sales, which then remain only in the totals. After a deletion we keep only internal records without the deleted content: internal IDs, counts and keyed hashes of the IDs involved, which cannot be read back without our key, used to recognize a repeated notification from Meta (for 180 days) and to delete the data again if we restore one of our daily backups (while a backup made before the deletion exists, and at least 45 days; the encrypted copies of our backups described in section 4 also hold them for up to 30 days after each copy). Replies that other people wrote to your comments stay, without their text.

6. Security

Traffic is encrypted with HTTPS, access tokens are encrypted at rest, access to data is restricted by role and tenant, and sensitive actions are logged. No system is completely secure; we will notify affected users of a data breach as required by law.

7. Your rights

Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict its processing, and to withdraw consent. Contact us at guilherm817@gmail.com; we respond within the period required by applicable law.

8. Cookies

Organic OS uses only the cookies needed to keep operators signed in and to remember the last Page opened, the interface language and the light/dark display preference. For the last Page opened, the cookie holds only that Page's internal Organic OS ID, used by the Page selector in the side menu to show it as the current Page. The funnel editor also keeps, only in the operator's browser, display preferences such as whether numbers are shown on the blocks and where blocks were moved on the canvas; they are not sent to us. The Pages screen likewise keeps, only in the operator's browser, whether Pages are shown as cards or as a table, and the Reel batch editor keeps which repeated-content warnings the operator chose to keep as they are. We do not use advertising or tracking cookies. Offer links do not set cookies.

9. Children

Organic OS is intended for businesses and is not directed to children.

10. Changes

We may update this policy. The effective date above shows the latest version; material changes will be communicated to operators.

Organic OS sign-in