Data Breach Notification Process
Version / Versão 1.0 · 15/11/2026
Prepared at the owner's request on November15,2026. Notifications are performed manually by management; automated delivery is not claimed. Incident records and customer contacts remain private. A documentary exercise does not demonstrate message delivery, continuous staffing or TikTok approval.
1. Owner, scope and activation
Management of Conecta In Marketing coordinates assessment, containment, notification and follow-up for Órbita Seller. Reports are received at alinesabiiinopenha@gmail.com. Plausible suspected or identified unauthorized access, disclosure, loss, alteration or destruction involving data, credentials or systems must be recorded and promptly assessed. Clearly distinguish suspicion from confirmation. Incomplete root-cause or impact information must not prevent preliminary notices to appropriate recipients.
The organization has a sole operator and does not claim24/7 human coverage. Check the channel on business days and activate the procedure upon awareness. Maintain follow-up during active incidents. If unavailability prevents a safe response, restrict or suspend affected processing/integrations where feasible and seek technical support; do not invent a substitute. Assess this limitation before expanding operations.
2. Recipients and channels
- TikTok Shop: where TikTok data, credentials, integrations or services are or may be involved, notify through the security/incident channel specified by the applicable agreement or Partner Center instructions. If no dedicated channel has been identified, promptly use authenticated Partner Center support, clearly identify a security incident and request escalation to the responsible team. Record the ticket and confirm the dedicated channel without delaying the initial report.
- Affected or potentially affected sellers: individually notify the pre-registered security contact or authorized representative in the contract/onboarding record. Verify the recipient. If receipt is unconfirmed, use an available authorized alternative and record attempts.
- Involved suppliers: contact the relevant Supabase, Vercel, Upstash or other provider support for containment and evidence, sharing only necessary information.
- Controller, individuals and ANPD: identify Órbita's role. As processor, inform the controller without undue delay and provide relevant assistance. As controller, assess whether a confirmed personal data incident may cause relevant risk or harm and make legally required notifications. Do not wait for customer approval to satisfy the organization's own legal duties.
Before integrating a shop, record the primary and alternative contacts, role, agreement and applicable TikTok reporting channel. The public security email is the organization's intake channel, not TikTok's reporting address. Do not guess reporting addresses.
3. Timing and updates
Notify relevant TikTok and seller recipients without undue delay following awareness of a plausible suspected or identified incident involving their data or services. Follow the shortest applicable deadline actually required by agreement, current platform instruction or law. Record awareness time, triggering event and due time. Submit an initial notice when details are incomplete and supplement it; do not wait for the final investigation.
The account-specific numeric TikTok deadline has not been verified because the review link did not display its full contents. Confirm and record it from the agreement/Partner Center before using the integration and resubmitting the assessment. This procedure does not represent24,48 or72 hours as TikTok's contractual deadline.
Under the general Brazilian rule, when mandatory-notification criteria are met, the controller notifies ANPD and individuals within three business days of knowing that personal data was affected, subject to specific applicable rules. This is separate from platform deadlines; do not presume eligibility for special small-entity treatment. Use legally applicable preliminary and supplemental notification mechanisms when information is incomplete. Provide material updates and state the next update time in the initial notice.
4. Execution workflow
- Log: create a restricted INC-YYYY-NNNN record with UTC and local timezone, source and minimal summary.
- Assess and contain: distinguish facts from hypotheses, identify potentially affected shops/systems, restrict access or revoke compromised credentials through authorized means and preserve evidence. Do not put exposed data in public reports.
- Select recipients: identify legal role, duties and verified channels. Record notification/non-notification decisions, reasoning and reassessment time; escalate suspicions involving TikTok/sellers as required.
- Notify: manually send a safe initial notice without waiting for final cause or impact. Record time, verified recipient, channel, ticket and receipt where available.
- Follow up: seek acknowledgement through an appropriate channel, update scope and mitigation, correct inaccurate statements and address follow-up requests. Record failures and alternatives.
- Close: document containment, known cause, communications, remediation, outstanding tasks and procedure review. Closure does not remove notification or preservation duties.
5. Minimum notice information
Organization and app identification; incident reference; suspected/confirmed status; awareness and occurrence time if known; factual description; data categories, systems and shops involved; known or pending impact assessment; actions taken/planned; recommended recipient actions; responsible contact; next update time. Do not include passwords, tokens, unnecessary individual data or exploitable details. Use verified secure channels for sensitive evidence.
6. Records and safeguards
Keep decision records, notices, ticket IDs, acknowledgements, updates and closure evidence in restricted internal storage. Publish only the procedure, never live incidents or customer contacts. For incident records subject to ANPD's regulation, observe the minimum five-year retention in Article10 of Resolution15/2024. This does not authorize retention of the entire exposed dataset. Assess other obligations according to purpose.
7. Exercises, review and status
Review annually and after incidents or changes to integrations, contacts or obligations; next review by November15,2027. The assistant completed a fictional documentary exercise on November15,2026. No real incident, message sending or delivery verification occurred. The owner must still verify channels, complete the TikTok contractual contact/deadline and walk through the procedure. No completed end-to-end test is claimed.
References
TikTok security and privacy review · ANPD incident notification guidance · ANPD Resolution15/2024