Privacy Policy
How we handle website and application data.
Updated November 1, 2026
Responsible party and contact
64.509.369 SAMUEL PANTANO DE ALMEIDA - ME (trading as Manualess), CNPJ 64.509.369/0001-07, with a physical address at Rua Tupinambas, 719, Valentim Gentil, SP, Brazil, is responsible for data processed to administer accounts, security, and platform support. For operational data received through integrations, controller and processor roles depend on the purpose, decisions made, and who determines the processing. To exercise your rights or ask about processing, email manualess.atendimento@gmail.com; requests may require proportionate identity verification.
Data, purposes and legal bases
We process account, device, permission, commerce, connection and technical-log data to authenticate, provide and protect the service, answer requests and meet legal obligations. The legal basis depends on each purpose under Articles 6 and 7 of the LGPD, including contract performance, legal or regulatory obligations and consent where applicable. API/OAuth credentials and tokens required for authorized operations are encrypted on the server and accessed only by the backend; platform browser sessions remain in the app's encrypted vault.
Sharing and providers
Infrastructure and transactional email use Oracle Cloud Infrastructure. Cloudflare helps deliver and protect the website and, when enabled, provides Turnstile anti-abuse verification. Sign-in may use Google or GitHub; when you connect a platform, necessary data is exchanged with the provider you select, such as Mercado Livre, Shopee, Meta/Instagram, TikTok, or Discord. Support emails are received through Gmail. After permission for site analytics, Google Analytics 4 measures visits and pages viewed on the public website, as described in the Cookie Policy. Each provider also applies its own terms and privacy notices. Because some operate internationally, data transfers will follow Articles 33–36 of the LGPD and ANPD Resolution No. 19/2024, as applicable. Optional advertising is described in the Cookie Policy.
Data subject rights
Under Article 18 of the LGPD, you may request confirmation and access, correction, anonymization, blocking or deletion where applicable, portability under legal conditions, information about sharing and withdrawal of consent. Requests are handled within the timeframes and forms set out in Article 19 after proportionate identity verification. Withdrawal does not invalidate prior lawful processing; legal obligations may limit immediate deletion.
Retention and security
We retain data as needed for stated purposes and the grounds in Articles 15 and 16 of the LGPD. Specific periods may apply to access logs and security incidents under the laws and rules listed on the Legislation and Scope page. Deletion may be limited where a legal duty or the exercise of rights requires retention. We apply technical and administrative safeguards under Article 46; no transmission or storage method removes all risk.
Spreadsheet contents
Sheets edited on the website are stored by Manualess and access depends on authentication, permissions and the selected business. In the app, content is saved in the device's encrypted vault. An older server sheet may be copied into the app on first open, without automatically deleting the source copy.
Advertising
When enabled and authorized, Google advertising may use cookies, identifiers, web beacons, IP addresses, or similar technologies to serve ads. Information about previous visits to this and other websites may be used to personalize ads, subject to the user's preferences and applicable consent. Manualess loads ads only after advertising-cookie consent; rejecting or withdrawing that choice prevents new ad loads.
Google Ads Settings · How Google uses data on partner sites and apps
Integrations and spreadsheets
When you connect an API, Manualess processes data needed for authorized features, which may include commerce and support information from platforms. API/OAuth tokens and secrets are encrypted on the server and used by the backend for authorized calls, webhooks, and continuous jobs; passwords and cookies from WebView sessions remain in the app's encrypted vault. Website spreadsheets are stored by the service; app spreadsheets remain in the local vault. Access depends on the account, permissions, and selected business.
Error reports and diagnostics
On the website, unhandled JavaScript errors may automatically send the technical message, error source, and page path (up to three events per page load); the backend records the matched route, source, and a cryptographic fingerprint, not browsing history. In the app, automatic diagnostics are optional and sent only after consent; on error they include the code, type, filtered technical message, file/line, time, environment, and up to 20 general recent actions kept only in memory for up to five minutes. The message is filtered for common sensitive-data patterns, but this cannot guarantee removal of all personal data. Typed text, commands, customer content, and sessions are not sent; revoke consent in settings.
Request deletion
The dashboard does not provide automatic account deletion. To request account closure and deletion of personal data, contact support at the address above; the request will be verified and reviewed under Articles 18 and 19 of the LGPD. Data subject to a legal obligation, exercise of rights, or another Article 16 basis may be retained for the applicable period. The request does not remove sessions held directly by third-party services; revoke those with the providers as well.
Acceptance record
When an account confirms the Terms of Use and this Policy, we record the account login identifier, server date and time, language, and versions of both documents. We also retain the exact content of each version linked to the record. This information documents the acceptance, with restricted access, and is kept as needed for legal obligations and the exercise of rights. We do not collect an IP address for this record. It documents an action under an authenticated account; by itself, it does not identify who operated the device.