MyCreations — Privacy Policy

Controller: IFM Hub Serviços LTDA · Last updated: November 21, 2026

1. Who the controller is

IFM Hub Serviços LTDA, Brazilian company registration (CNPJ) 66.191.755/0001-29, registered office at R. Angelo Leite de Campos, 87, Jardim Residencial Villa Olympia, Sorocaba/SP, Brazil, ZIP 18.087-287, e-mail contact@myifmhub.com.

For any request concerning your personal data, use the Data subject channel described in Section 13.

2. Definitions

For the purposes of this Policy: Data subject: you, the MyCreations User; Personal data: any information that identifies or may identify a natural person (art. 5, I, Brazilian General Data Protection Law — LGPD); Controller: IFM Hub (which decides on the processing); Processor: third parties that process data on behalf of IFM Hub.

3. Data we collect and legal bases

DataPurposeLegal basis (LGPD)
Name and e-mailAccount creation, billing, communicationArt. 7, V — performance of a contract
Password (hash)Secure authenticationArt. 7, V — performance of a contract
OAuth tokens (social networks)Publishing on the User's behalfArt. 7, V + Art. 7, I — consent
Generated content (text, image, video, audio), except images of people and voice samples, covered in the rows belowProduction and publishingArt. 7, V — performance of a contract
Face photograph of the User, uploaded by the User (sensitive personal data — biometric data)To generate the avatar, images and videos bearing the User's likeness, through the providers listed in Section 5Art. 11, I — specific and prominent consent, obtained on the upload screen and revocable at any time by deleting the photograph; revocation applies to subsequent processing and does not undo what has already been generated
Voice recording of the User, uploaded by the User (sensitive personal data — biometric data)To create the User's synthetic voice through the provider listed in Section 5; the recording is not stored by usArt. 11, I — specific and prominent consent, obtained on the upload screen and revocable at any time by deleting the voice — a deletion we carry out at the provider and verify; revocation applies to subsequent processing and does not undo what has already been generated
Image in which a person other than the User appears (sensitive personal data — biometric)To generate the asset the User requests from the image the User uploadsArt. 11, I — consent of the person depicted, obtained by the User and declared by the User to IFM Hub in the uploads where the Platform asks for that declaration. IFM Hub does not verify that authorisation and records the declaration with its date and the version of the text declared
Record of the image and voice consent — version of the text consented to, date and time, language, providers and destination country disclosed, account identifier, the account's e-mail address where present, and IP addressTo evidence the specific consent for sensitive dataArt. 11, I, with art. 8, §§ 1 and 2 — the controller's burden of proof
Network metrics and statisticsReporting to the UserArt. 7, V — performance of a contract
Payment data (via Stripe)BillingArt. 7, V — performance of a contract
Card identifier (the fingerprint received from the payment processor, not the card number) and customer identifier at the payment processorTo confirm the place in the launch offer, to limit one account per card, and to process the subscriptionArt. 7, V — performance of a contract, while an account exists; and Art. 7, IX — legitimate interest, for the retention after cancellation described in Section 7
Record of acceptance on sign-up to the Launch Plan queue — version of the text, date and time, language, IP address and browser identifierTo evidence acceptance of the terms presented at sign-up and, where given, consent to receive news and offersArt. 8, §§ 1 and 2 — the controller's burden of proof
Status of the sign-up (pending, place granted or declined), reason for the decline, and the date the trial period endsTo administer the places in the launch offer and the transition to the subscriptionArt. 7, V — performance of a contract
Customer and subscription identifiers at the payment processorTo link the sign-up to the subscription and to process billingArt. 7, V — performance of a contract
IP address and access logsSecurity, fraud prevention and incident investigationArt. 7, IX: legitimate interest
Application access record: IP address, date and time, account and the "session started" event (one line per account, IP and day)Comply with the access-record retention duty of the Marco Civil da Internet and allow identification under a court orderArt. 7, II: legal obligation (Law No. 12,965/2014, Art. 15)
Account action trail (inviting, changing role, deleting a user, publishing, deleting a publication, changing scope): who did what, when and on which resource, with the IP addressSecurity, evidence and fraud preventionArt. 7, IX: legitimate interest
Cookies and Meta Pixel (website)Marketing and audience measurementArt. 7, I — consent (opt-in)
Record of your cookie choice (date, time, text version and choice)Evidencing consentArt. 8, §§ 1 and 2 — burden of proof on the controller
Record of the User's declaration about images of people in an asset — identifier of the account and of the organisation it belongs to, date and time, option chosen, the asset it refers to, the version of the text declared, the language, and the date on which the asset was deleted, used only to count the period in Section 7To record that the User declared having authorisation from the people depicted, in order to demonstrate compliance with this PolicyArt. 7, V — performance of the contract, for the purpose of accountability (art. 6, X)
Record of the User's declaration about the use of an avatar in automatic publications — identifier of the account and of the organisation it belongs to, date and time, option chosen, the module and the identifier of the set of avatars it refers to (a technical fingerprint, without the images), the version of the text declared, the language, and the date on which the declaration ceased to have effect, used only to count the period in Section 7To record that the User declared having authorisation from the people depicted, in order to demonstrate compliance with this PolicyArt. 7, V — performance of the contract, for the purpose of accountability (art. 6, X)
Contact from a Meta ad form. The name and email the person sends in the form of a MyCreations ad on Meta (for example, the Black November one). We also keep the record of who received the reminder and, for whoever asked not to receive messages anymore, only a protected version of the email, just to respect the request and to prove what was sent. Whoever activates an account moves to the account data rules.Send the offer information and a single reminder to complete the activation. We do not use the contact for any other offer. If you do not want more messages from us, reply SAIR ("leave", in Portuguese) to the email or write to contact@myifmhub.com, and we stop sending.Art. 7, V (at the request of the person, preliminary procedure) and IX
Messages to Maia and the account information she uses. What the User types to Maia (the AI assistant), her replies and the account information she uses to reply: the name or, if there is none, the email; the brands (name, way of speaking and whether they publish without review); the connected social network accounts (network and account name); the number of campaigns; the last campaign created (title and date); the last action done with Maia; the progress of the first steps; and, when the User asks about the plan, the plan and its use. The User may write business data in the messages and, without meaning to, data about other people; for that reason we ask the User not to write other people's data unless needed, nor health, religion or similar information. To reply, the messages and this information go to Anthropic (Sections 5 and 6). We do not save the text of the messages on our servers, except the data of the actions the User confirms, described in the trail line; it stays only in the memory of the open page and disappears when the page is reloaded or the User changes screens.Answer what the User asks or requests from MaiaArt. 7, V: performance of a contract
Trail of the actions confirmed to Maia. The actions the User confirms to Maia are kept in the account's action trail, with the IP address and the data of the action (for example, a campaign brief or the fields of a brand).Record who did what, for security and evidenceArt. 7, IX: security and evidence
Messages to support. The name and email address of whoever writes to our support, the content of the messages, whatever the person attaches and the replies we give. We ask the person not to write other people's data unless needed, nor health, religion or similar information. If a message to support is a request about your personal data, we treat it as a data subject request (Section 8), on the same business day we read it.Reply to the person and keep the history of the support, to prove what was asked and what was answeredArt. 7, V, VI and IX

Campaign measurement. When you reach our site through one of our ads, the page address carries four tags that we define ourselves (source, medium, campaign and ad content). The server keeps them together with the technical record described above (network address, date and time, and page), and we use them to count how many people arrived through each campaign. What we look at are numbers per day, page and campaign, without the network address and without identifying anyone. We do not keep Meta or Google click identifiers, we do not link this measurement to your registration, and we do not use it to build advertising lists. Basis: legitimate interest (LGPD, Art. 7, IX).

4. Cookies and tracking technologies

The website uses essential cookies for the operation of the service (authenticated session and browsing preferences), which do not require consent because they are indispensable to the contracted service.

It also uses, only with your prior and express consent, the Meta Pixel — a third-party technology (Meta Platforms, Inc.) that records browsing events such as page views, interest in plans, and clicks on the sign-up, contact and purchase buttons. The purpose is to measure the performance of our advertising campaigns and to show ads to similar audiences. Consent is collected through the cookie banner displayed on first access.

You may decline in the banner itself, with no impact whatsoever on your use of the Platform, and withdraw at any time through the Cookie preferences link in the website footer. Until you accept, the pixel is not loaded. We record your choice together with the date, the time and the version of the text you read, without your IP address and without any identification of your browser. Our code does not send Meta your e-mail, phone number or name (advanced matching is turned off). On-device measurement, which is turned on in our account, compares on your device information you have already given us, such as your e-mail, with temporary device data; according to Meta, that information stays on the device and Meta learns only that a purchase happened and which campaign should receive the credit. This is a statement by the provider, not a verification carried out by us.

Two features of the pixel call for an explanation. First, in addition to the events our code sends, Meta's technology automatically identifies and sends details of the page visited, such as its title, description, prices and ratings displayed on it. Second, the feature is turned on in our account, with measurement starting November 12, 2026, on a gradual rollout (according to a Meta notice to advertisers dated October 18, 2026 and the Events Manager screen, read on November 8, 2026): part of the conversion measurement may be processed on your own device.

The description of on-device measurement is Meta's, not ours. According to the page "About conversion measurement on customers' devices" in the Meta Business Help Center (https://www.facebook.com/business/help/4237575203200036, read on November 8, 2026), this matching happens on the customer's device, no information identifying the customer is shared with Meta, and Meta receives only the confirmation that a purchase happened and which campaign it should be attributed to. This is a statement by the provider, and not a verification carried out by us. As for the automatic sending of page details, the statement above does not cover it and we have no way of verifying what Meta does with those details.

The pixel operates only after your acceptance and only on the public pages of the website: never on your account screens and never in the apps.

There is no advertising tracking whatsoever in the mobile apps (iOS and Android). The pixel and the cookie banner are not loaded inside the apps — they exist on the website only.

5. Sharing with third parties (processors)

IFM Hub shares only strictly necessary data with the providers that operate the Platform: infrastructure, database, authentication and storage; artificial intelligence providers for the generation of text, image, video and audio; social networks, for the publishing requested by the User; payment and subscription processing; message delivery; and audience measurement and advertising on the website, as set out in Section 4.

The complete and up-to-date list, with the purpose, the data processed and the country of each provider, is available at [Processors and sub-processors](https://myifmhub.com/Operadores). We maintain that page as the single source, so that the information is always accurate; a relevant change to that list is communicated as set out in Section 12.

We do not sell, rent, or trade your personal data with third parties.

Two clarifications specific to this service. Reference images uploaded by the User, including face photographs, are transmitted to the artificial-intelligence providers on each generation, by the User's own action, and are not stored by us at those providers. Voice samples are transmitted in the same way; when the User creates a voice from a sample, that voice remains at the audio provider for as long as it exists in the account, so that it can be reused in later assets, and it is deleted when the User deletes the voice or the account — a deletion we carry out at the provider and verify. Any processing each provider carries out on its own account, including any short-term technical retention, follows that provider's policy, which we identify on the Operators and sub-processors page. And the Platform queries public image archives (Openverse, Wikimedia Commons) sending only the search term, with no data identifying the User — which is why they are not sub-processors.

6. International transfer of data

Part of the processing takes place outside Brazil. The destinations are:

- Platform storage and processing — United States: the database, authentication and storage (Supabase) and the application server (Hostinger). - Artificial intelligence providers: Anthropic (text and visual-prompt generation — receives the content of the request and the reference images uploaded by the User, including photographs of a face), Google (image and video generation — receives, when the User so requests, reference images uploaded by the User) and ElevenLabs (audio and voice-over generation — receives, when the User so requests, voice samples provided by the User). The place of processing for each is the one set out in the contract or data processing agreement of the provider. Anthropic also receives the messages the User types to Maia and the account information she uses to reply: the name or, if there is none, the email; the brands (name, way of speaking and whether they publish without review); the connected social network accounts (network and account name); the number of campaigns; the last campaign created (title and date); the last action done with Maia; the progress of the first steps; and, when the User asks about the plan, the plan and its use, for the purpose of answering them. - Other sub-processors: in the countries indicated on the Processors and sub-processors page. The location of Supabase and Hostinger was measured by us; for the others, the place of processing is the one set out in the contract or data processing agreement of the provider.

Transfer instrument: IFM Hub adopts the standard contractual clauses approved by the Brazilian National Data Protection Authority (ANPD Resolution CD/ANPD no. 19 of 2024), pursuant to art. 33, II, "a", of the LGPD, with the providers that have already adopted them (Google, ElevenLabs) and, for the others, in the process of adoption, under the provider's own contractual safeguards, to ensure that processing carried out abroad observes the principles and rights set out in the LGPD.

A face photograph uploaded to create or use an avatar, and a voice sample uploaded to create a voice, are sensitive personal data — biometric data (art. 5, II, LGPD); in other images the User uploads, the image of a real person is likewise sensitive where it allows that person to be identified or reproduced. These data are processed on the basis of art. 11, I, LGPD — specific and highlighted consent. Where the data are the User's own, consent is collected from the User on the upload screen. Where the image is of another person, the consent is that of the person portrayed, obtained by the User before uploading and declared by the User on the screen, as described in Section 3. They are sent to the providers above by the User's own action, to perform the functionality the User requests; IFM Hub is the controller of this processing and is answerable for the choice of providers, the destination countries and the retention periods in Section 7. Reference images are transmitted on each generation and are not stored by us at the provider. The voice created from a sample, by contrast, remains stored at the audio provider, outside Brazil, for as long as it exists in the User's account — so that, in that case, the international transfer covers not only the transmission but also the storage. That storage is covered by the same transfer instrument identified in this section, and it ends when the User deletes the voice or the account.

7. Data retention and deletion

CategoryMaximum periodGrounds
Account dataUntil cancellation + 6 monthsArt. 16 LGPD + Art. 10 Brazilian Internet Act
Asset files, including those awaiting disposal30 days after the asset has been published to all the networks selected for it, and 30 days after the file ceases to be used by any asset, whichever comes firstArt. 15, I, and art. 16, LGPD — the purpose has been achieved and the data are no longer necessary
Library assets (logos, avatars)While the account is active and up to 6 months after cancellationPerformance of the contract
Voice created from a sample uploaded by the User, stored at the audio providerUntil the User deletes the voice or the account — a deletion we carry out at the provider and verify before closing the local recordWe are the controller of that data, even though it is held by a third party; erasure at the data subject's request and upon the end of the purpose
Record of the image and voice consentWith the asset or voice it refers toThe controller's burden of proof, with minimisation of what ceases to be necessary
Record of the declaration about an image uploaded to an asset3 years after the asset is deletedLimitation period for civil damages (Civil Code, art. 206, § 3, V)
Record of the declaration about the use of an avatar in automatic publications3 years after the declaration ceases to have effect — when the schedule is deactivated, the set of avatars is changed, or the module is deleted, whichever comes firstLimitation period for civil damages (Civil Code, art. 206, § 3, V)
Billing records5 yearsLegal and tax obligation
Account deletion record (subscription and customer identifiers at the payment processor, dates of the request, of the cancellation and of the erasure; no name, e-mail or IP)5 years after the erasureArt. 16, I, LGPD: proof that the deletion request was fulfilled, and tax obligations and defense in billing complaints
Card dataNot stored by us — retention as per StripeWe are not the controller of that data
Card identifier — the fingerprint received from the payment processor, not the card number — and customer identifier at the payment processorWhile the account exists and for up to 6 months after the account is deleted, to prevent a further place in the offer with the same card. On deletion of the account, the e-mail address, telephone number, IP address, browser identifier and record of the promotional consent are erased; the card identifier, the identifiers at the payment processor, the version of the text and the date of acceptance, and the remaining dates are kept, and at the end of the 6 months the whole record is erased. Evidence of acceptance is preserved in the account-deletion record, for the period stated in the corresponding row of this tablePerformance of a contract while an account exists (art. 7, V); legitimate interest for the retention thereafter (art. 7, IX)
Server access logs90 days from the record; then deletedSecurity and incident investigation: legitimate interest (LGPD, Art. 7, IX) and duty of security (Art. 46)
Application access record6 months from the record; then deleted. May be kept longer only under a court order or legal requestMarco Civil da Internet, Art. 15
Account action trail: IP address6 months from the action; then the IP is deletedSecurity and fraud prevention (Art. 7, IX)
Account action trail: record of the action5 years from the action. When the account is deleted, the author's name is replaced by a pseudonym (a code that remains personal data, because we keep the deletion record separately) and the organization's record is keptEvidence in a dispute over the account or a publication; period of Art. 27 of the Consumer Defense Code
Campaign measurement: lines with the ad tags90 days, together with the server technical record
Campaign measurement: numbers per day, page and campaign, without network address24 months
Marketing cookies (Meta Pixel)Up to 90 days, or until consent is withdrawn, whichever comes first — this is the term of the identifier stored in your browser, which is deleted upon withdrawal. Anything already sent to the provider before withdrawal is retained by it as described in Section 5; withdrawal stops further sending.Art. 7, I — consent
Record of cookie consent (date, time, text version and choice; without IP address and without browser identification)5 yearsArt. 8, §§ 1 and 2, LGPD — evidence of consent
BackupsDeleted in the next backup cycle, within 10 days at mostArt. 16 LGPD
Text and captions of the pieces created on the PlatformFor as long as the organisation the piece belongs to exists. When you delete your account, the pieces you created remain with the organisation if it has other members; if you are its only member, the organisation and the pieces are deleted together with the accountArt. 7, V, LGPD — performance of the contract with the organisation
Contact from a Meta ad form (name and email), reminder record and SAIR requestsIf the person does not activate the account, we delete within 90 days after the form was sent, including the record of the reminder sent. Of whoever asked not to receive messages anymore, we keep only a protected version of the email, with no fixed period, reviewed once a year. If they activate, the data become those of the account (periods in this Section).Art. 7, V and IX
Messages to MaiaThey disappear when the page is reloaded or the User changes screensMinimization (LGPD, Art. 6, III)
Trail of the actions confirmed to MaiaThose of the two "Account action trail" lines in this SectionArt. 7, IX
Messages to support (name, email, content, attachments and replies)Up to 12 months after the last message, whether or not the person has an account. If the person asks us to delete earlier, we delete, except what we must keep by legal obligation or for our defense in a claim or dispute in progress.Art. 7, V, VI and IX

About backups: when data is deleted from the active database, any backups still containing it are deleted in the next backup cycle, within 10 days at most. During that interval, the data is not used for any purpose.

8. Data subject rights (art. 18 LGPD)

The User may, at any time, exercise the following rights by request through the channel described in Section 13, at contact@myifmhub.com, with an immediate reply, in simplified form, for confirmation of the existence of processing and for access, and within 15 (fifteen) days for the complete declaration (art. 19, I and II, LGPD):

- Confirmation and access to the data processed; - Correction of incomplete, inaccurate or outdated data; - Deletion of data processed on the basis of consent or after the purpose has been fulfilled; - Portability — export in a structured format; - Withdrawal of consent, without prejudice to the lawfulness of prior processing; - Objection to processing based on legitimate interest, where applicable; - Information about data sharing.

A deletion request is recorded and the account data is erased from our systems within 30 (thirty) days, including for requests received through Meta's deauthorize and data-deletion webhooks. Any backups still containing it are deleted in the next backup cycle, within 10 (ten) days at most, as set out in Section 7, and are not used to restore data that has already been erased. The records described in Section 7 are kept (among them, the deletion record, the billing data and the messages to support), for the periods set out there.

Users outside Brazil: the rights listed above are granted to all Users, wherever they are located. If the law applicable in your country, state or province grants you additional rights regarding your personal data, you may exercise them through the same channel in Section 13, and we will respond in accordance with the applicable law.

9. Minors

MyCreations is intended for persons aged 18 (eighteen) or over. We do not knowingly collect data from minors; if we become aware of an account held by a minor, we will delete it immediately. The fact that the User produces content aimed at children and teenagers (e.g. Roblox, Minecraft) does not change this policy — the User is an adult and is responsible for the content they produce.

10. Google API — Limited Use

The use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including the Limited Use requirements. IFM Hub: does not sell or share data obtained from Google APIs with unauthorized third parties; does not use it for purposes unrelated to the publishing requested by the User; and does not transfer it to third parties without explicit consent, except where necessary to provide the Service.

11. Information security

We adopt technical and organizational measures: encryption at rest of OAuth tokens (AES-256-GCM); per-user data isolation (Row-Level Security in Supabase); encrypted traffic (HTTPS/TLS); role-based access control; and incident response procedures. In the event of a security incident involving relevant risk or harm, we will notify the ANPD and the affected Data subjects within the legal period (art. 48 LGPD).

12. Updates to this Policy

This Policy may be updated to reflect legal, regulatory, technical or operational changes. The most recent version will always be available on this page. Material changes will be communicated by e-mail.

On 02/11/2026 the wording of 13/10/2026 was restored in Sections 3, 6 and 7, with no change to any processing.

On 21/11/2026 Sections 3, 6, 7 and 8 were updated to include: the messages sent to support, kept for up to 12 months after the last message; the messages to Maia and the account information she uses, which go to Anthropic; the application access record and the account action trail, including the actions confirmed to Maia, with their retention periods; and what is kept when the account is deleted. The statement that data export was already implemented was also removed.

13. Data subject channel

To exercise any of the rights in Section 8, or for any question about this Policy, write to contact@myifmhub.com with the subject "Personal data — MyCreations". We will reply within the legal period of 15 (fifteen) days.

IFM Hub is a small-scale processing agent under the regulations of the Brazilian National Data Protection Authority and, in that capacity, maintains this communication channel with Data subjects. Even so, it has appointed a data protection officer (encarregado) under Article 41 of the LGPD: Edson Munhoz Castro, partner and legal representative, since November 20, 2026. The officer's contact is the same data subject channel: contact@myifmhub.com.

To object to the promotional use of your data, or to withdraw the promotional consent you gave when you signed up, write to contact@myifmhub.com. The request is free, requires no justification, and is handled by Edson Munhoz Castro, responsible for data subject requests at IFM Hub. The promotional consent record is switched off and the date of withdrawal is stored. You receive confirmation that it was done.

Please also see our Terms of Service.