This policy explains how e-Com GOD operates, the choices available to customers, and how to contact the grievance team.
Tenant separation
Workspace and shop identifiers scope tenant records. Server authorization and PostgreSQL row level security enforce membership; shop data is not intentionally exposed across workspaces.
Credentials and payments
Connector credentials are encrypted before storage and are not returned through customer APIs. Razorpay processes payment credentials. Secrets are kept out of client bundles and operational interfaces.
Integrity and monitoring
Provider event IDs, business keys, idempotent jobs and transactional aggregate rebuilds reduce duplicate counting. Sync cursors, errors, retry counts, stale source indicators and reconciliation variance remain visible to authorized operators.
Access and response
Access by role limits workspace actions. Administrative actions are audited and do not expose connector secrets. Suspected vulnerabilities or incidents should be reported to hello@dkntechnologies.com with enough detail to investigate safely.
- Do not test against another customer's workspace.
- Avoid including live credentials or unnecessary personal data in reports.
- We do not claim a security certification that has not been independently completed.