Data ownership
Customers retain ownership of operational data they provide. Satuangka does not claim ownership of customer sales, finance, marketing, product, or inventory records.
Data Security
A truthful security model starts by separating the demo from production data.
This page explains what the current public experience does today and which controls must be documented before Satuangka processes customer operational data.
Current status: the live dashboard uses fictional FMCG data. Contact and audit forms simulate submission locally and are not connected to a production customer database.
Encryption
The public site and demo are delivered over HTTPS by the hosting platform. The current demo has no customer-data backend. Production encryption at rest and key handling are documented for the selected infrastructure before customer data is loaded.
User permissions
Production workspaces are intended to use role-based, least-privilege access. Exact roles, administrators, and approval owners are agreed during implementation.
Retention and backups
The current demo persists only action status in the visitor’s browser. Production retention periods, backup frequency, recovery expectations, and deletion windows are written into the customer implementation scope.
Export options
A production implementation must define export formats and administrator access. The public demo export button is a transparent simulation and does not create a customer-data file.
Deletion process
A verified workspace administrator can request deletion through the agreed support contact. The production scope must document identity verification, deletion timing, backup expiry, and any legal retention exception.
Incident handling
The production agreement identifies the incident contact, assessment process, communication path, and applicable notification commitments. Satuangka does not claim certifications or response SLAs that have not been contracted.
Storage location and processors
The current public demo is hosted on OpenAI Sites and contains fictional data. No customer operational dataset is stored. For production, hosting region and third-party processors are disclosed and approved before go-live.
Security review before implementation
The data audit can include source access, user roles, retention needs, storage-region requirements, export and deletion expectations, incident contacts, and processor review. These are confirmed in writing before customer operational data is ingested.
Book a Free Data Audit