Personal Data Protection Policy
Version / Versão 1.0 · 15/11/2026
Data protection requirements and public summary of the internal policy. Retention and deletion procedures are being implemented and verified. This is not a certification or a replacement for the complete privacy notice, whose full legal identity and legal review remain pending.
1. Accountability and scope
Management of Conecta In Marketing owns implementation and review for Órbita Seller. The policy covers accounts, business relationships, campaigns and creator data processed for authorized purposes. The organization currently has a sole operator. Controller and processor roles must be determined per activity and contract. This page does not appoint a DPO.
2. Purpose, minimization and records
Maintain internal records of data, individuals, purposes, sources, assessed lawful grounds, recipients, countries, retention and ownership. Collect only necessary data. Do not routinely require identity documents for simple requests. Public creator data also requires a purpose and lawful-ground assessment. Consent and legitimate interests are not blanket justifications. Assess new processing before it begins.
3. Security and access
Apply least privilege by role and company, individual accounts, MFA, server and database authorization, access reviews and secret protection. Follow the published Information Security Policy. Restrict exports and unauthorized secondary uses, including unnecessary disclosure to AI tools.
4. Suppliers and transfers
Known services are Supabase, Vercel and Upstash, with known processing in Brazil and the United States. Additional regions, subprocessors and backups remain under inventory review. Assess contracts, applicable transfer safeguards, necessity and deletion before new processing. The TikTok integration is being prepared; real shop data is not represented as already connected.
5. Approved retention requirements
- Leads: 90 days without interaction.
- Operational data: up to 30 days after termination for export, followed by deletion or effective anonymization, subject to documented exceptions.
- Minimal request records: 24 months after closure.
- Backups: intended maximum cycle of 30 days, subject to supplier capabilities still being verified.
These are approved administrative periods, not universal legal periods or proof of automated deletion. Tax documents, contracts, legal duties, controller instructions and preservation for legal claims require specific assessment and a record of grounds, minimum scope and reassessment date.
6. Deletion and restoration
Review necessity and deletion candidates monthly. Record decisions, authorization, affected systems and minimal execution evidence. Address controlled exports and copies. Pseudonymization is not anonymization. Immutable copies follow the approved cycle, with suppression instructions reapplied before restored data returns to use. Operational validation of this procedure remains pending.
7. Individual requests
Approved contact: alinesabiiinopenha@gmail.com. The owner must check the channel on business days and manually track requests with internal case numbers, proportionately verify identity, locate data, assess role and deadline, respond and record closure. As processor, refer requests to the controller and track instructions. The application form only prepares an email; it does not automatically send or register requests. Access, correction, information and deletion requests are assessed under applicable rights and exceptions. For confirmation and access, observe LGPD Article 19; do not apply one deadline indiscriminately to every right.
8. Incidents and review
Follow the published incident procedure and assess applicable legal and contractual notifications. Review this policy annually and after incidents or material changes, preserving version, decisions and reviewer. First review is due by November 15, 2027. No prior review history is represented.
9. Approval and implementation status
The owner approved the periods, contact and publication in this conversation on November 15, 2026. Detailed inventories, case records and evidence remain private. Request-handling and deletion tests have not been demonstrated, and supplier retention has not been fully verified. Policy approval does not establish full program execution.
Notificação de incidentes / Incident notification
Procedimento em português · Data Breach Notification Process — English