SCALEON ERP — Information Security & Data Protection Program

Version 1.2 · Effective October 14, 2026

Download PDF (v1.2, current) Personal Information Protection Standard (SCL-PIPS-001 v1.0)

Previous version: v1.1 (effective October 1, 2026), PDF

OrganizationSCALEON ERP (scaleonerp.com.br) — multi-tenant SaaS ERP for e-commerce sellers
Legal entity59.770.797 NICOLAS GOMES LIMA — CNPJ 59.770.797/0001-59 (Brazil)
Document version1.2
Effective dateOctober 14, 2026
Review cadenceAt least annually, and after any security incident or material system change
Owner / approverGabriel Molina Teramoto — Founder, Security & Privacy Owner
Privacy / DPO contactprivacidade@scaleonerp.com.br
ScopeAll SCALEON systems, staff and contractors that access, process, store or transmit seller, buyer or TikTok Shop data
Related documentsPersonal Information Protection Standard (SCL-PIPS-001)

Contents: 1. Information Security Policy · 2. Network Security · 3. Endpoint Protection · 4. Security Baseline · 5. Access Control Policy · 6. Data Classification & Encryption · 7. Incident Response Policy · 8. Vulnerability Management · 9. Internal Personal Data Protection Policy (LGPD) · 10. Data Subject Requests, Retention & Deletion · 11. Breach Notification · Annex A — Data inventory & sub-processors

1. Information Security Policy

SCALEON is a small SaaS company. Security responsibilities are formally assigned and this program applies to every person and system that handles customer data. The Founder is accountable for the program, approves this document and reviews it at least annually.

RoleResponsibilities
Security & Privacy Owner (Founder)Approves policies; grants/revokes access; owns incident response and breach notification; LGPD data protection contact (encarregado).
Lead DeveloperImplements technical controls (encryption, secrets, network rules, logging); applies patches and dependency fixes; first responder for technical incidents.
All staff / contractorsFollow this program; use MFA; report suspected incidents immediately; access data only for assigned tasks.

Principles: data minimization (only the TikTok Shop API scopes required for order, product, inventory and fulfillment management are requested), least privilege, encryption by default, use of reputable managed cloud providers, and documented response to incidents.

2. Network Security & Segregation

3. Endpoint Protection

4. Security Baseline for Daily Operations

5. Access Control Policy

6. Data Classification & Encryption

ClassExamplesHandling
Confidential — PersonalBuyer name, shipping address, phone, order details received from TikTok ShopEncrypted in transit and at rest; least-privilege access; retained only while needed for fulfillment
Confidential — SecretsApp secret, OAuth access/refresh tokens, DB credentials, API keysStored only as encrypted environment secrets; never logged; rotated on suspicion of exposure
InternalProducts, SKUs, inventory, production orders, financial summariesAccess limited to the seller tenant and authorized staff
PublicMarketing site contentNo restrictions

7. Incident Response Policy

StepActionOwner / timing
1. ReportAnyone who suspects an incident reports immediately to the Security Owner (e-mail privacidade@scaleonerp.com.br / phone / WhatsApp).All staff — immediately
2. TriageAssess severity (data exposed? which tenants? ongoing?) and open an incident record.Security Owner + Lead Dev — within 4 h
3. ContainRevoke/rotate affected credentials and tokens, block access, disable affected features, preserve logs.Lead Dev — immediately after triage
4. NotifyIf personal data may be affected: notify TikTok Shop and affected sellers (Section 11) and, when required, the ANPD and data subjects under LGPD.Security Owner — within 24 h to TikTok Shop / sellers
5. RecoverFix root cause, restore from backup if needed, verify.Lead Dev
6. ReviewPost-incident review with root cause and preventive actions; update this program.Security Owner — within 10 business days

An incident response tabletop exercise is performed at least annually and documented.

8. Vulnerability & Threat Management

9. Internal Personal Data Protection Policy (LGPD)

SCALEON acts as a data processor (operador) on behalf of sellers (controllers) for buyer data obtained through TikTok Shop, and complies with the Brazilian General Data Protection Law (Lei 13.709/2018 — LGPD) and the TikTok Shop Developer Terms.

Public privacy policy: https://scaleonerp.com.br/privacidade

10. Data Subject Requests, Retention & Deletion

11. Data Breach Notification

If a breach affecting TikTok Shop or seller data is suspected or confirmed, the Security Owner notifies TikTok Shop (via Partner Center support ticket and partner@tiktokshop.com) and affected sellers (via e-mail) without undue delay and within 24 hours of confirmation, describing the nature of the incident, data and tenants involved, containment actions and contact point. Notifications to the ANPD and data subjects are made when required by LGPD.

Annex A — Data inventory & sub-processors

Sub-processorPurposeDataLocation
VercelHosting / serverless runtime; logsAll application data in transitUnited States (default region)
Vercel BlobFile storage and backupsShipping labels (buyer name, address, phone), spreadsheets, photos, attachments, backupsPer Blob store region
NeonManaged PostgreSQL databaseAll system data (orders, buyer shipping data, products, inventory)Brazil (São Paulo)
InngestBackground jobsJob identifiers and metadataUnited States
ResendTransactional e-mailRecipient name/e-mail, notice contentUnited States
LabelaryZPL label renderingLabel content incl. buyer dataUnited States
LalamoveProduction freightWorkshop contact names, phones, addresses (not buyers)Brazil
GitHub ActionsRuns weekly backup jobNo stored data (backup saved to Vercel Blob)United States
TikTok Shop Open APISource of seller/order dataOrders, products, logisticsTikTok Shop

Data flow: Seller authorizes SCALEON via TikTok Shop OAuth → SCALEON backend (Vercel) calls the TikTok Shop API over TLS → data stored in Neon (São Paulo) and labels in Vercel Blob → displayed only to the authorizing seller's users → labels auto-deleted after 10 days; remaining data deleted at contract end or on request.

Approved by: Gabriel Molina Teramoto, Founder — October 14, 2026