Skip to content
Arara Code

Arara Code

Privacy Policy

Controller, Data Protection Officer, and scope

G R T — Gabriel Rodrigues Torres is the controller responsible for the processing of personal data across the Arara Code ecosystem under Brazil's General Data Protection Law (LGPD — Law No. 13,709/2018), also serving as the contact channel for the Data Protection Officer (DPO) at contato@code.app.br. This policy covers the institutional website, account dashboard, mobile application (/app), API services, Arara Code IDE, Arara Vibes, and Arara Desktop. Local applications such as Arara Vibes and Arara Desktop operate directly on the user's device without transmitting local histories, files, or screen captures to our servers. Third-party assistants, extensions, and services are governed exclusively by their own policies.

Privacy contact: contato@code.app.br

Account and authentication

We process name, email, phone number (when provided during registration or in the dashboard), password submitted for authentication, account identifier, external Google sign-in identifier (when used), creation and email confirmation dates, record of acceptance of the Terms of Use and this Policy, plan, administrative role, eventual suspension, and preferences. Passwords are stored exclusively in encrypted form, never in plain text. Temporary tokens and codes enable sign-in, session renewal, email confirmation, password reset, and application authorization, and are protected by encryption. We send transactional communications strictly necessary for account management, security, and billing. If you fill in the home page form, we retain your name, email, language, and campaign parameters (UTM) to streamline registration and enable contact if account creation is not completed. Legal bases: performance of a contract or preliminary procedures at the data subject's request (Art. 7, V, LGPD) and legitimate interest in security and fraud prevention (Art. 7, IX, LGPD).

Code, local automation, and artificial intelligence

We have no partnership, affiliation, or control over external artificial intelligence providers (such as OpenAI, Anthropic, Google, AWS, or others). When you use built-in or external assistants with your own accounts, keys, or CLIs, all message content — both from the user and from the AI — travels directly between your device and the chosen provider, without passing through our servers and without us having access to it. Arara Vibes conversation history and Arara Desktop accessibility readings, on-demand captures, and inputs remain exclusively on your local machine, never being sent to the Arara Code backend. In turn, proprietary features of the Arara service (such as autocomplete, commit generation, and terminal utilities) transmit only the necessary technical context (snippet around the cursor, language, paths, diagnostics, diffs, or recent output) to the API and inference gateway, without recording in permanent conversation history or application inference logs; autocomplete requests ephemeral 300-second caching from the provider, and temporary notes ("By the way") expire in 1 hour. External providers process and retain data exclusively in accordance with their own policies and terms.

Quotas, activity, and usage time

We store account, installation, and request identifiers, platform, day, message counts, accepted suggestions, calls, and tokens to enforce quotas and present statistics. These counters do not contain message text or code. Time tracking records session identifier, start, last heartbeat, duration, and daily aggregates. It is enabled by default and can be disabled in Arara Settings, Account, Track usage time. This stops future time reports from the IDE, without deleting previous data or disabling counters necessary for quotas. Authorized administrators may consult account, usage, session, payment, and statistical data to operate the service and provide support.

Payments and emails

Mercado Pago processes Pix payments and card subscriptions. We send email, first name when needed for Pix, amount, reference and, for cards, a payment token and method. The payment provider's secure fields receive full card details; our server receives only the token and does not store the full number or security code. We store identifiers, amounts, statuses, Pix QR codes and links, method, dates, cancellations, paid periods, and notification records. Signed notifications update these statuses. The transactional email service receives name, email, and transactional message contents, including confirmation and reset links and paid-period information.

Website version tests and browser data

To compare versions of the home page and of the sign-in and sign-up screens, the browser stores locally which version you got, one letter per test, and which actions were already counted. There is no identifier. The server receives only the test, the version, and the type of action, such as viewing the page, submitting the form, or clicking create account, and adds up daily totals, without storing IP, cookie, or user-agent. When you create an account, the version you saw is recorded on it to measure sign-up and email confirmation. Do Not Track and Global Privacy Control disable participation. Clearing site data ends participation in this browser. The browser also stores the chosen language; the access token remains in memory and the refresh token in localStorage. We also store the first access in this browser for up to 180 days: date, landing page path, referring site origin, and UTM parameters. Upon creating an account or signing in, including via Google and when restoring a session, this origin and available test versions are associated with the account if it does not yet have an origin. Subsequent visits do not replace it. We do not store IP address, browser identifier, full referrer URL, or other URL parameters with this origin. Do Not Track and Global Privacy Control disable capture and association and remove the local origin; clearing site data also removes it. Origin already associated with the account follows the account retention period.

Site access metrics

To understand the reach of public pages, the server that delivers the site records each access to pages, their Markdown versions, and llms.txt files: path, date and time, user-agent, referrer, and UTM parameters in the address. The user-agent classifies the access as a browser, an AI agent, or another robot. For browsers, the IP address and user-agent are combined with a secret key into a hash that identifies visits and sessions without storing the IP. On public pages, the browser also sends the time with the tab visible, scroll depth, and clicks on download, installer, registration, and external links. This measurement uses no cookies or browser storage and includes no code, conversations, or account data. When the browser sends Do Not Track or Global Privacy Control, the access only enters per-page totals, without hash, session, or time measurement. Individual records expire in 180 days; hourly totals by page and agent do not identify individuals and have no automatic deletion period. The legal basis is the legitimate interest in operating and improving the site.

Advertising measurement with OpenAI, Meta, and Google

Advertising measurement is enabled by default. The OpenAI Measurement Pixel records account creation and successful sign-in as leads, and Supporter payment confirmations received while the payment screen is open as purchases, with the amount in BRL. It uses OpenAI attribution and browser cookies (__oppref, up to 30 days, and __obref, up to 365 days). The SDK sends technical connection metadata and site origin to OpenAI; this integration does not explicitly send names, email addresses, passwords, card details, code, or conversations. Payment event identifiers are hashed. Refusal, Do Not Track, and Global Privacy Control prevent loading this integration. The cookie notice has only an Ok button, which dismisses the message and does not alter previously saved preferences. Blocked events are not replayed. Browser restrictions or ad blockers may prevent delivery. Payments completed after closing the screen are not measured by this browser integration. Meta uses the same permission for its Pixel, with Lead on registration/sign-in and Purchase on confirmed payment, in BRL. CompleteRegistration remains on registration. Meta may receive the page URL, technical connection metadata, and its attribution cookies (_fbp and _fbc). Previous refusals remain valid. No integration loads when there is a refusal or a browser privacy signal; we do not use a noscript pixel. Google Ads uses the same permission for the Google tag, with a sign-up conversion upon submission of the registration form, account creation by email, and the first sign-in with Google; signing in to an existing account does not count. Google may receive the page URL, technical connection metadata, and its attribution cookies (_gcl_au and the click identifier). Ad personalization and Google Analytics remain disabled in this integration.

P2P sharing

Signaling processes account identifiers, name, email, platform, offer-code hash, public keys, addresses and ports, decisions, statuses, and dates. Name and email are presented to the other participant and connection data is shared after acceptance. IP and account limit invalid code attempts. Offers and requests remain in memory with ten-minute validity; accepted sessions last up to one hour on Free and, when either account is a Supporter, until sharing is terminated. Cleanup depends on service activity. When relayed via the API, encrypted frames remain in memory until receipt confirmation, closure, or idle cleanup; the server does not receive the connection's private keys. Requests, context, and results may be processed on the lender's computer and by the AI provider. Encryption does not hide content from authorized endpoints.

Catalog, versions, and downloads

Administrators publish agent descriptions, instructions, and files for authenticated users. Files are stored in cloud storage and may be delivered via temporary signed links or public distribution, depending on configuration; they must not contain confidential data. Version queries receive the current version, when provided. Downloads receive platform and architecture and redirect to official distribution packages. External services receive technical connection metadata when you access them.

Legal bases, international data transfers, and third parties

We process personal data exclusively under the legal bases of the LGPD: performance of a contract or preliminary procedures (Art. 7, V) for account management, authentication, requested features, and payments; compliance with a legal or regulatory obligation (Art. 7, II) for tax and accounting records and mandatory retention under the Brazilian Internet Bill of Rights (Law No. 12,965/2014); regular exercise of rights in judicial or administrative proceedings (Art. 7, VI); and legitimate interest (Art. 7, IX) for security, fraud prevention, support, and essential metrics, respecting the rights of the data subject. There is strictly necessary sharing for operations with cloud infrastructure and network providers, file storage, transactional email delivery, payment processing (Mercado Pago), inference providers and gateways, package distribution, and P2P participants authorized by you. Such providers may operate on servers located outside Brazil; in such cases, international transfers comply with the requirements of Art. 33 of the LGPD and applicable contractual safeguards. We may also disclose data pursuant to a court order or formal requisition by a competent authority.

Retention and deletion

Detailed usage-time sessions and home page form data expire after 180 days; IDE authorization codes in 1 minute; temporary notes in 1 hour; password reset links in 1 hour; email confirmations in 24 hours; and quota windows at the end of the period. Application access logs may be maintained for the statutory minimum period of 6 months (Art. 15 of the Brazilian Internet Bill of Rights), and tax, financial, and billing data are retained for applicable statutory periods (up to 5 years or as long as necessary to prove payments, prevent chargebacks, comply with legal obligations, and regularly exercise rights). Cancelling a subscription or disabling usage time tracking does not automatically delete historical records required by law or contract. To request permanent account deletion or the elimination of data not subject to mandatory retention, write to contato@code.app.br; we will respond within statutory LGPD deadlines (up to 15 days for confirmations and complete statements). Files, local histories from Arara Vibes/Desktop, and data held with external providers must be managed directly within those environments.

Security

We adopt proportionate technical and administrative measures to protect data under our custody, including encryption in transit, encrypted password storage, rotating tokens, single-use temporary codes, role-based access control, request rate limiting, and end-to-end encryption in P2P sharing. No internet-connected system is entirely immune to risks; therefore, protect your credentials, review local permissions, and avoid entering passwords, private keys, or unnecessary sensitive personal data into prompts or published files.

Minimum age

Arara Code is intended for individuals aged 18 or older. Creating an account requires confirming this age. We do not knowingly collect data from children or adolescents; if you believe a minor has created an account, write to the contact above and we will delete it.

Your rights (LGPD)

Pursuant to Art. 18 of the LGPD, you may request at any time: confirmation of the existence of processing; access to data; correction of incomplete, inaccurate, or outdated data; anonymization, blocking, or elimination of unnecessary, excessive, or unlawfully processed data; data portability, where applicable; information regarding public and private entities with which data has been shared; information on the possibility of denying consent and the consequences thereof; revocation of consent; and review of decisions taken solely on the basis of automated processing, where applicable. For the security of the data subject, we may require proportionate identity verification prior to fulfilling requests. Requests must be sent to contato@code.app.br, without prejudice to the right to petition the National Data Protection Authority (ANPD).

Changes to this policy

This Privacy Policy may be updated periodically to reflect changes in products, services, or applicable legislation, always indicating the update date at the top of the page. Material changes will be communicated through appropriate channels and, when requiring new consent, such consent will be requested prominently.

Read as Markdown