Last updated: October 16, 2026
Saiphix is operated by Saiphix.com. For user account data, we are the data controller. For the data a community owner uploads in order to check joining conditions, the community owner is the controller and we process that data on their behalf and on their instructions.
We never ask for or store your passwords, API keys or any security key you hold with another service. Only the identifiers necessary for the check are used.
Data is used only to determine whether you meet the conditions for joining and for staying that the community owner has set, to grant and revoke access to the private group, to send related notification emails, and to operate and secure the service. We do not sell user data to third parties.
Data is stored on Supabase Postgres (Singapore region) and Cloudflare R2. The data you upload is valid only for a short time window (60 minutes by default), after which it is no longer used to assess conditions. Account data is kept for as long as you use the service and for a reasonable period afterwards to meet record-keeping obligations.
A member’s UID or customer ID at an exchange reaches the system by three routes only: the member enters it themselves; the community owner uploads a file that contains it; or the community owner connects a reporting key from their own partner programme at an exchange and the system reads that report. There is no other route.
That identifier is used for one purpose: to check whether the member signed up through that community owner’s referral link, and to check the conditions for joining and for staying that the same community owner has set. It is not used for anything else, it is not sold, and it is not disclosed to another community owner.
We do not scrape data from any exchange, and we never ask a member for an API key, a password or any security key. A community owner who connects an exchange may use only a read-only partner key of their own account: that key is encrypted before it is stored, is never displayed again — not even in part — and is never sent to a browser.
How long it is kept: an uploaded file is valid only for the short window described in section 5 and is not used to assess conditions once that window has passed. A member’s UID stays in the records of that one community for as long as the community owner keeps the community. Where a community administrator removes a member’s identifier from the community’s records, we no longer need that identifier in raw form: 30 days after the removal, the UID held for that community is replaced by a one-way hashed value, and the verification and trading-volume records attached to it are deleted. The hashed value cannot be reversed back to the original UID, and the same person in a different community produces a different value. We do not use that value to identify anyone; it is kept only so that a disputed case can still be checked afterwards. This replacement is carried out by a scheduled job that processes a limited number of records per run, so it takes place later than day 30 rather than on that day. A member leaving the chat group does not by itself start this 30-day period: the identifier is anonymised only once an administrator has removed it from the community’s records.
When a community is deleted there is a 7-day waiting period in which the owner can restore it; after that the community is purged. The owner may also choose to purge the community straight away, without the 7-day wait. A purge permanently deletes the community’s database records — including the member UIDs held in those records, together with any stored exchange key — and, in the same purge run, also deletes the uploaded files belonging to that community from our file storage. If such a file cannot be deleted during that run, the database purge still completes and the file is not retried automatically; we delete it when we become aware of it. An audit log of administrative actions is retained for record-keeping, is not affected by a purge, and may record the email address of an administrator. The system never writes a member’s exchange UID into that log by itself; where an administrator gives a reason for an action, that reason is stored as they wrote it, so it may contain whatever they chose to type. You may ask us to delete your identifier at any time under section 8.
You have the right to access, correct, export or request deletion of your personal data, and to withdraw your consent at any time. Send your request to the email address below; we respond within the time limits set by law. Where the data was uploaded by a community owner, we may forward your request to that community owner.
Email: hello@saiphix.com