Terms of Use

1. Parties, acceptance, language and who may use the Service

1.1. These Terms of Use (the "Terms") govern the use of The Social Media App (the "Service"): the web app, the public API and the MCP server. The Service is operated by Rocha Code, registered under CNPJ 41.095.655/0001-78, with its seat at Rua Rio Grande do Norte, 100, Santa Maria, Uberaba/MG, Brazil ("Rocha Code", "we").

1.2. By creating an account, you declare that you have read and accept these Terms and the Privacy Policy. Without this acceptance, the account is not created.

1.3. We record every acceptance: the version of the text, the language shown, the date and time, the IP address, the browser and the approximate country. This record serves as proof of the acceptance.

1.4. Language. The Portuguese text governs for users in Brazil. The English text governs for users outside Brazil. The other interface languages display the English text as a courtesy only.

1.5. The Service is intended for persons aged 18 or over. It is made for businesses and for professionals working on their own account.

1.6. If you accept these Terms on behalf of a company or another organization, you declare that you have authority to bind it. In that case, "you" includes that organization.

2. The Service

2.1. The Service lets you create, schedule and publish content on social networks. It also lets you follow the results of your publications and control costs.

2.2. You can use the Service through the web app, through the public API with API keys, or through MCP clients (for example, artificial intelligence assistants) that you connect to your account.

2.3. We publish only through the official APIs of each network and only with the authorization of the connected account. We never use scraping, cookie automation or reverse-engineered APIs.

2.4. Each integration with a network (a "connector") has a stage: research, approved, beta or generally available. A connector in research cannot be connected. A connector in beta works, but may change or have limits.

2.5. What each connector allows depends on the account, the format and the action. Availability also depends on each network, which may change its rules, limits or APIs at any time.

3. Accounts and security

3.1. Each account belongs to a single person. Do not share your password or your session.

3.2. You are responsible for keeping your credentials secure and for everything done with them. Tell us immediately at [email protected] if you suspect misuse.

3.3. API keys are credentials of the organization. A key can only do what the current role of its creator allows in that organization. If that role is reduced, the key loses the corresponding powers. We show the key only once and store only a cryptographic digest of it.

3.4. We may block an account to protect the Service, other users or third parties, for example when an account is compromised or used abusively. A blocked account cannot sign in, its sessions are ended, and the API keys and MCP access linked to it stop working.

3.5. We may also end all sessions of an account without blocking it, for example when a device is lost. In that case, you will need to sign in again.

4. Organizations, members and roles

4.1. Work in the Service happens inside organizations. Each organization can have several members, and each member has a role: owner, admin, publisher, editor or viewer.

4.2. Each organization has exactly one owner. The owner is responsible for the organization, for the members they invite, for the connected network accounts and for the costs incurred in it.

4.3. Only the owner can delete the organization. Ownership can be transferred to another member.

4.4. Invitations are single-use links, valid for 7 days and revocable. Nobody is invited directly as owner.

4.5. The organization can require team approval: in that case, content last edited by an editor is published only after approval by another person with permission to approve.

5. Connected social accounts

5.1. When you connect a social network account, you authorize Rocha Code to act on behalf of that account, through the network's official API, within the permissions you granted.

5.2. We store the networks' tokens and app passwords encrypted. They never reach the browser or artificial intelligence models.

5.3. You must comply with the terms and policies of each network you connect. If a network restricts or suspends your account, that decision is the network's.

5.4. YouTube. The Service uses YouTube API Services. By using the YouTube features of the Service, you agree to be bound by the YouTube Terms of Service. Google's processing of your data follows the Google Privacy Policy.

5.5. Instagram (Meta). When you use the Instagram features of the Service, you must comply with the Instagram Terms of Use, the Instagram Community Guidelines and the Meta Platform Terms. Only professional accounts can be connected.

5.6. TikTok. When you use the TikTok features of the Service, you must comply with the TikTok Terms of Service, the TikTok Content Sharing Guidelines, the TikTok Community Guidelines and, where applicable, TikTok's Music Usage Confirmation and Branded Content Policy, which the Service displays before each post.

5.7. Bluesky. The connection with Bluesky uses an app password that you create in Bluesky. When you remove the connection, we delete the stored password; you should also revoke it in your Bluesky settings.

5.8. You can disconnect an account at any time. When you disconnect, we revoke the authorization with the network, where the network allows it, and delete the stored credentials.

6. Content

6.1. You own the content you create, upload or publish through the Service and you are responsible for it.

6.2. You grant us a limited, non-exclusive, royalty-free, worldwide licence to store, process, adapt to each network's format and transmit that content, only to operate the Service for you. This licence ends when the content is deleted from the Service, except for what the law requires us to keep.

6.3. You declare that you hold all the rights needed over the content, including music, images, video, trademarks and the likeness of people who appear in it. The scheduling tool does not grant those rights.

6.4. You may not use the Service to publish content that is illegal, infringes third-party rights, amounts to harassment, hate speech, exploitation of minors, spam or fraud, or breaks the rules of the destination network.

6.5. Labels and disclosures required by the destination network are your responsibility. This includes labels for content generated by artificial intelligence, disclosures of commercial or branded content, and the choice of audience and privacy of the post.

6.6. We do not use your content or your metrics to train artificial intelligence models.

6.7. We may remove content or stop publishing it when the law, an order of an authority or these Terms require it.

7. Automation, API and MCP

7.1. MCP clients and API-key integrations can create drafts, validate and estimate publications. For an MCP client, scheduling or publishing always requires a human approval in the web app. For an API-key integration, scheduling or publishing requires that approval when the organization requires team approval (section 4.5) or when the destination network requires consent before each post (section 7.3).

7.2. Consent to publish is a verifiable authorization (authorization_reference) created by a person in the web app. An "approved" answer from an artificial intelligence model is not consent.

7.3. Some networks require the person's consent before each post. In those cases, the Service publishes only after that consent, and any change to the content requires a new consent.

7.4. The Service applies usage limits per account, per organization, per network and per credential. We may defer a publication to respect these limits or the network's limits.

7.5. On the public API, you must: use only your own credentials; not try to circumvent limits, scopes or approvals; not overload the Service; and not resell access to the networks as if it were yours. The public API offers the features of our software and grants no right to resell access to, or data of, any network.

7.6. You are responsible for the actions of the MCP clients and integrations you connect to your account. You can revoke an MCP client at any time in Settings, Connected apps.

8. Plans, prices and billing

8.1. Some operations may carry a cost charged by third parties, such as a network or a supplier (the "external eligible cost"). When such a cost exists, it will be passed on to you plus a 10 % commission calculated only on the external eligible cost.

8.2. Before publishing, the Service shows a cost estimate. An estimate is not an invoice. You can set budget caps to limit spending.

8.3. At the end of each month, the Service produces a statement per workspace and per currency. The statement shows the external cost, the commission and the total, but it is not an invoice or a tax document.

8.4. Plans. A plan belongs to the person who holds the account, and the organizations you own follow your plan. Each plan sets how many organizations you can own and how many social network accounts each of them can connect. The free plan allows 1 organization with up to 3 connected accounts. Members invited to an organization do not use anyone's plan.

8.5. Prices and payment. The paid plans, their limits and their prices, in the applicable currency and billing period (monthly or yearly), are shown on the plans page and on the payment page before you subscribe. Payment is processed by Stripe, our payment processor, on Stripe's own pages. Card details are given directly to Stripe and are neither received nor stored by us. The subscription renews automatically at the end of each period until it is cancelled.

8.6. Changing plans. When you move to a larger plan, the difference for the time left in the period is charged at once; if the payment is declined, the change is not made and your current plan continues. When you move to a smaller plan or a shorter billing period, the change applies from the next renewal: until then your current plan continues, and the period already paid is not refunded or credited. At the renewal you are charged the price of the plan you chose.

8.7. Cancellation. You can cancel the subscription at any time in the billing portal. The cancellation takes effect at the end of the period already paid: until then your plan continues; afterwards the account returns to the free plan. The current period is not refunded, except where the law requires it.

8.8. Plan limits. When you reach a limit of your plan, the Service does not let you create another organization or connect another account, and it shows the limit and how to change plans. What already exists keeps working.

8.9. Payment pending. If a charge fails, Stripe tries again for some days and the Service shows a notice. If the attempts end without payment, the organizations you own become read-only until the payment is settled or you choose a plan that fits what you hold: content can be read and exported, but you cannot create or change content, connect accounts or publish, and scheduled posts wait. The same applies when what you hold exceeds the limits of your plan, for example after a cancellation or a move to a smaller plan.

8.10. Nothing is deleted because of a plan. To move to a smaller plan, you choose which organizations and, in each of them, which connected accounts stay active. The other organizations are archived and the other accounts are suspended: nothing is deleted, the connections are kept and you can reactivate them when your plan has room. A plan, a pending payment or a cancellation never causes the deletion of your organizations, your content or your connected accounts; deletion happens only when you ask for it (section 10).

8.11. Taxes on the amounts charged will be handled under the applicable law.

8.12. No refunds. Amounts paid are not refunded, except where the law requires it (section 12.2). A temporary failure of the Service is handled under section 9.5.

9. Availability and changes to the Service

9.1. We work to keep the Service available, but it may be unavailable because of maintenance, failures, attacks or reasons beyond our control.

9.2. We may change, suspend or discontinue features, including pausing a connector temporarily to protect users or to meet a network's requirements.

9.3. Beta features are offered as they are and may change or cease to exist.

9.4. We do not guarantee the behaviour of the social networks. A network may refuse, delay, change, limit or remove a post, and may change its APIs or its prices.

9.5. If the Service has a temporary failure, Rocha Code may, at its discretion, grant you extra usage time on the platform. This extra time is not converted into money or credit and does not limit the rights described in section 12.2.

10. Suspension and termination

10.1. You may stop using the Service at any time. The owner of an organization can delete it in the app: the deletion stays pending for 7 days, during which it can be cancelled, and is then carried out.

10.2. You may ask for the deletion of your account by e-mail to [email protected], as described in the Privacy Policy.

10.3. We may suspend or end your access, in whole or in part, if you breach these Terms, if the law or an authority requires it, or if a network requires it. Where possible and permitted, we will tell you beforehand and explain why.

10.4. The clauses that by their nature must survive termination remain in force, including those on content (to the extent needed), fees already due, intellectual property, warranties and liability, governing law and forum.

11. Intellectual property

11.1. The Service, its software, its brand and its materials belong to Rocha Code or its licensors. These Terms transfer none of these rights to you.

11.2. You may not copy, modify, decompile or exploit the Service beyond what these Terms allow, except where the law allows it.

11.3. If you send us suggestions or feedback, we may use them freely, without any obligation to pay or to give attribution.

12. Warranties and liability

12.1. To the extent permitted by law, the Service is provided "as is" and "as available".

12.2. Nothing in these Terms excludes or limits the rights that the Brazilian Consumer Protection Code (CDC) or another mandatory law guarantees to consumers.

12.3. For users who use the Service as a business or professional, and to the extent permitted by law: we are not liable for lost profits, loss of opportunity or indirect damages; and our total liability is limited to the amount you paid us in the 12 months before the event that gave rise to the claim.

12.4. These limitations do not apply to damage caused by wilful misconduct or gross negligence, nor to other cases in which the law does not allow a limitation.

13. Mobile apps

13.1. When we make mobile apps of the Service available, we grant you a personal, limited, revocable, non-exclusive and non-transferable licence to install and use them under these Terms.

13.2. App obtained from Apple's App Store. If you obtain the app from the App Store:

1. These Terms are concluded between you and Rocha Code, and not with Apple Inc. ("Apple"). Rocha Code, not Apple, is solely responsible for the app and its content.
2. The licence of the app is limited to use on Apple-branded products that you own or control, as permitted by the Usage Rules set forth in the App Store Terms of Service, except that the app may be accessed and used by other accounts associated with the purchaser via Family Sharing or volume purchasing.
3. Rocha Code is solely responsible for the maintenance and support of the app. Apple has no obligation whatsoever to furnish any maintenance or support services.
4. If the app fails to conform to any applicable warranty, you may notify Apple, and Apple will refund the purchase price of the app, if any. To the maximum extent permitted by law, Apple will have no other warranty obligation whatsoever with respect to the app. Any other claims, losses, liabilities, damages, costs or expenses attributable to any failure to conform to any warranty are Rocha Code's responsibility, to the extent they cannot be excluded by law.
5. Rocha Code, not Apple, is responsible for addressing any claims by you or any third party relating to the app or your possession and use of it, including: product liability claims; any claim that the app fails to conform to any applicable legal or regulatory requirement; and claims arising under consumer protection, privacy or similar legislation.
6. If a third party claims that the app, or your possession and use of it, infringes that third party's intellectual property rights, Rocha Code, not Apple, will be solely responsible for the investigation, defence, settlement and discharge of that claim.
7. You represent that you are not located in a country that is subject to a U.S. Government embargo, or that has been designated by the U.S. Government as a "terrorist supporting" country, and that you are not listed on any U.S. Government list of prohibited or restricted parties.
8. Questions, complaints or claims about the app must be sent to Rocha Code at the contacts in section 16 (address and e-mail).
9. When using the app, you must comply with applicable third-party terms, such as your wireless data service agreement.
10. Apple and Apple's subsidiaries are third-party beneficiaries of these Terms. Upon your acceptance of these Terms, Apple will have the right, and will be deemed to have accepted the right, to enforce these Terms against you as a third-party beneficiary.

13.3. App obtained from Google Play. If you obtain the app from Google Play, the Google Play Terms of Service also apply to the download and the use. Rocha Code, not Google, is responsible for the app.

14. Governing law and forum

14.1. These Terms are governed by the laws of the Federative Republic of Brazil.

14.2. Rocha Code and the Service are located in Brazil. The courts of the district of Uberaba/MG, Brazil, are chosen to settle any dispute relating to these Terms, subject to sections 14.3 to 14.5.

14.3. If you are a consumer in Brazil, you may bring the action in the courts of your domicile, as the Consumer Protection Code allows.

14.4. If you are outside Brazil, you keep the mandatory protections that the law of your country of residence guarantees and that cannot be set aside by contract.

14.5. Consumers in the European Union and the United Kingdom may turn to the alternative dispute resolution bodies and to the courts that the law of their country provides. Rocha Code is not obliged to take part in alternative dispute resolution proceedings before consumer arbitration bodies, except where the law requires it.

15. Changes to these Terms

15.1. We may change these Terms. Each version has a number and an effective date, and earlier versions remain available in the history on this page.

15.2. We announce a new version inside the Service before it takes effect.

15.3. When the change is relevant, you will have to accept the new version before you continue using the web app. Until you accept, your organization's API keys and MCP access keep working, but actions that depend on you in the web app wait.

15.4. If you do not agree with a new version, you may stop using the Service and ask for the deletion of your account.

16. Contact

• Rocha Code, CNPJ 41.095.655/0001-78
• Rua Rio Grande do Norte, 100, Santa Maria, Uberaba/MG, Brazil
• Contact, support and data protection officer (encarregado): [email protected] (24 hours a day; the first reply is automated)