Data security notice
This notice focuses on data sources, authorization boundaries, security controls, retention, and incident response.
1. Data sources and authorization boundaries
We process only user-authorized data sources. We do not access connected data stores or third-party accounts outside the scope the user explicitly authorizes. Tenants retain ownership of data they upload or authorize.
2. Transmission security
All HTTP traffic between user agents and platform services is encrypted in transit using TLS 1.2 or higher. HSTS is enabled on production domains. Certificate validity is monitored.
3. At-rest encryption
Persistent storage (databases, object storage, backups) uses server-side encryption with industry-standard algorithms (AES-256 or equivalent). Key material is managed by the infrastructure provider's managed KMS; application-layer code does not handle raw key material.
4. Authentication and access control
- Role-based access control (RBAC) limits platform operations to users holding the matching role.
- Authentication supports account/password and may require multi-factor authentication for sensitive roles.
- Sessions expire after a period of inactivity; long-lived sessions are revocable.
- Operator access to production systems is limited to explicitly authorized personnel and governed by the principle of least privilege.
5. Tenant isolation
- Each tenant's data is logically isolated; cross-tenant queries are blocked unless the asset owner has explicitly published it to the marketplace.
- Sensitivity classifications (Public / Internal / Confidential / Restricted) govern cross-tenant exposure. Internal and higher-sensitivity assets require explicit owner action plus row-level isolation tags before they can be published.
- Virtual views and derived datasets inherit the highest sensitivity of their source tables; they cannot bypass isolation by wrapping a sensitive asset.
- Row-level security is enforced at the query layer; filter conditions based on tenant identity are injected before the query reaches the execution engine.
6. Audit logging
- Access to sensitive operations (authentication events, permission changes, data exports, marketplace publish/subscribe actions) is logged.
- Audit logs are retained for a period aligned with regulatory and business requirements, and are stored separately from application data.
- Log tampering is mitigated by append-only storage and periodic integrity review.
7. Data retention and deletion
User-uploaded data is retained while the associated account and subscription remain active. On account deletion or subscription termination, data is scheduled for deletion within 30 days unless a longer period is required by law. Aggregated, anonymized operational telemetry may be retained for longer for reliability and security purposes.
8. Incident response
- If a security incident materially affects user data or rights, we commit to notifying affected users and relevant authorities without undue delay and, where feasible, within 72 hours of confirmation of the incident.
- Incident review includes root-cause analysis and, where relevant, changes to code, configuration, and operational procedure.
- Users may report suspected security issues to Larry@lg-data.cn.
9. Data subject rights
Users have the right to access, correct, delete, export, or restrict processing of their personal information, consistent with the PRC Personal Information Protection Law. Requests are fulfilled within 15 working days of receipt where legally permitted; contact Larry@lg-data.cn.
10. Subprocessors
We use third-party infrastructure providers (cloud compute, managed databases, email delivery) strictly to provide the service. Subprocessors are bound to confidentiality and data-protection obligations no weaker than those in this notice. A current list is available on request by contacting Larry@lg-data.cn.
11. Compliance status
The platform has completed PRC ICP filing for its public domain. We are actively building operational practices aligned with widely adopted frameworks (e.g., SOC 2, ISO 27001) but do not currently hold third-party certification under those frameworks. This section will be updated as certification milestones are reached.
12. Security contact
Please report security issues to Larry@lg-data.cn. We aim to acknowledge reports within 2 working days.