تخطَّ إلى المحتوى

الثقة والمطابقة

ما نحتفظ به، وأين يقيم، ومن يستطيع الوصول إليه، وما يحدث إن رحلت. مكتوب بوضوح، لأن هذا هو ما يحدّد إن كان تسليمنا تطبيقك قرارًا سليمًا.

Who we are

Retoxy LLC.

Security reports: security@retoxy.com. Privacy questions: privacy@retoxy.com. We answer security reports from anybody, whether or not you are a client, and we will not threaten you for sending one.

Where your data lives

On servers we rent and administer ourselves, in Singapore. The database, the object storage, the mail queue and the application all run on our own infrastructure. We use no hyperscale cloud service — not for compute, not for storage, not for logging, not for analytics. The only outbound calls we make are to the stores and the payment provider, because that is the service.

No server, service or dependency in our infrastructure is hosted in India. That is a standing constraint on this platform and it is checked in our build, not left to memory.

What we hold, and who can reach it

  • Your app builds and listings. Readable by your own team and by the Retoxy reviewer handling your submission.
  • Your signing keys. Encrypted. No client-facing query can read the key material at all; an export goes through an audited path and tells you it happened.
  • Your store credentials. Encrypted, and readable only by the process that hands them to a store's API. No person on our side reads them in the normal course of work, and no client role can read them either.
  • Your verification documents. Readable by your own owners and admins, and by the reviewer deciding verification. Deleted when the retention period runs out.
  • Your revenue figures. Readable by your owners, admins and finance members. Not by your developers, unless you give them that role.
  • Your customers' payment details. We never hold these. They go to the payment provider directly and our software never sees them.

Those are not promises about how our code behaves. Every table in our database has row-level security with a policy, enforced by the database rather than remembered by a programmer, and a test refuses to pass if a table ever appears without one.

How we sign in

Passwords are hashed with scrypt at a cost that makes bulk cracking expensive. Two-factor authentication with an authenticator app and passkeys are both supported, and sensitive actions — exporting a signing key, requesting a payout, changing who is on your team — need a second factor again even on a session that is already signed in.

When a Retoxy operator views your account to help you, it is recorded with both identities, and that session cannot export your keys or move money however senior the operator is.

The audit log

Every action that changes anything is recorded: who did it, what they touched, from where. You can read your own organisation's entries. The log is append-only in the database — there is no way for our application to alter or delete an entry, because the permission to do so was never granted.

Backups

The database is backed up automatically and the backups are encrypted and kept off the machine that made them. Restores are tested, because a backup nobody has restored is a hope rather than a backup.

What happens if you leave

You take everything. Your store accounts were always in your name, so there is nothing to transfer: you remove our access and carry on. Your signing keys export in the standard formats. A full data export — apps, listings, assets, releases, ledger, invoices, tickets — is available on demand and is not something we charge for or slow down.

We deliberately built the exit before the lock-in, because a middleman who can hold your users hostage eventually will.

What we are not

  • We are not a bank, a payment institution or a money transmitter, and we do not hold client funds.
  • We are not your lawyer or your accountant. We can tell you what a store's rule says; whether your app is lawful where you sell it is yours to establish.
  • We are not certified to any security standard yet. When that changes we will say which standard, by whom, and on what date — not before.

This deployment is not finished

Some of the configuration above is still a placeholder on this deployment. Until it is set, treat this page as a statement of intent rather than of fact.