01Introduction
Trexure (“we,” “us”) is a privacy-preserving treasury API for Stellar, operated by Artisam Labs. We are committed to safeguarding your privacy. This policy explains what information we handle when you visit our website, open the app, or use our APIs to shield, reconcile, and receipt payments.
By using Trexure, you agree to the practices described here. If you do not agree, please do not use the service.
02Information we handle
We collect only what is required to operate a multi-tenant treasury product, and we minimize personal data wherever possible.
- Account information: username and tenant name you provide at sign-up. We do not offer social login or email magic links.
- Authentication data: an argon2id hash of your password (never the plaintext) and a hashed session token in a cookie.
- Payment metadata: corridors (e.g. USD→PHP), amounts, a shared intent id used for reconciliation, and opaque recipient references. We minimize PII — we never store raw recipient identity on-chain.
- Shielded payloads: ZK-encrypted payment blobs and proof hashes. These are opaque ciphertext; we cannot read them without your view key.
- Usage & log data: pages and API endpoints accessed, audit events (login, view-key decrypt, key creation), IP, and user-agent. Logs redact tokens and secrets.
- Cookies: small device files used for essential session handling and, if you accept, analytics.
03How we use your information
- To authenticate sessions, scope every query to your tenant, and run the reconciliation worker.
- To generate the unified, accounting-ready receipt for your payments.
- To respond to support inquiries and provide tenant administration.
- To maintain an audit trail of sensitive actions (view-key decryption, key rotation, admin operations).
- To improve the product, monitor health, and detect fraud or abuse.
- To fulfill legal and regulatory obligations.
04Shielded payments & view keys
The privacy model: payments are ZK-shielded on-chain. The public Stellar ledger sees only a proof hash — no sender, no recipient, no amount. Your tenant holds a view key that decrypts the shielded payload server-side, on demand. The view key itself is stored encrypted at rest (AES-256-GCM) and is never returned to the client or written to logs.
Decryption is audit-logged. You may disclose a decrypted payload to a regulator you choose; we do not disclose it on your behalf.
05Sharing your information
We do not sell or rent personal information. Sharing is limited to:
- Service providers: infrastructure vendors (e.g. hosting, database, queue, object storage) bound by confidentiality agreements. Secrets never leave server-side code paths.
- Fiat anchors / payout providers: only the opaque references needed to settle a payout, under your anchor configuration.
- Legal authorities: where disclosure is required by law, and only to the extent required.
06Data retention
We retain information as long as needed to fulfill the purposes here or as required by law. Payment and receipt records are retained for the period needed for accounting and compliance. Audit logs are retained on a defined schedule. You may request deletion of your data, subject to legal retention duties.
07Data security
We apply technical and organizational safeguards: validated input, encrypted secrets at rest, HMAC-verified webhooks, tenant isolation enforced in every query, strict security headers, and rate-limited auth and API routes. No method of internet transmission is completely secure, but we treat your data with institutional-grade care.
08Cookies
We use three kinds:
- Essential cookies — required for authentication and session handling.
- Analytics cookies — visitor behavior, only if you accept.
- Preference cookies — remembering your settings, such as your cookie choice.
You can manage cookies through your browser controls. Our consent prompt lets you accept or decline non-essential cookies.
09Your rights
You may access, correct, or delete your data, withdraw consent, and opt out of marketing communications by contacting trexure@artisam.xyz. Where applicable, you also have rights to portability and objection to processing.
10Third-party links
Our site may link to external websites (for example, Artisam Labs or our app). We are not responsible for the privacy practices of those external sites and encourage you to read their policies.
11Changes to this policy
We may update this policy from time to time. We will post the revised version on this page with an updated date. Continued use of the service after a change signifies acceptance of the updated policy.
Questions about this policy? Reach the Trexure team:
