Privacy

1. Our role

Rezva operates a registry and resolution layer for payment identifiers. We process information needed to run those systems: accounts, applications, identifier mappings, destinations, complaints, operator actions, and service logs. Rezva does not receive, hold, or settle your crypto or fiat payments. Payment activity that occurs inside a third-party wallet is governed by that wallet’s privacy practices, not by this notice alone.

2. Information we process

Account and authentication data. Dashboard sign-in may use Privy or similar authentication. We may receive identifiers such as wallet addresses, email, session tokens, and account metadata needed to keep you signed in and authorize actions. Admin console access uses separate operator credentials.

Applications and evidence. Business and wallet-provider applications may include contact details, website, summaries, and supporting evidence. Evidence is stored for operator review. It is not published in public resolve responses.

Registry and resolution data. When identifiers are registered or updated, we store type, normalized value, controller references, destinations (network, asset, address or equivalent), status fields, timestamps, and related protocol metadata. Compatible clients may query the resolver to retrieve payment-ready mappings.

Complaints and reports. Dispute submissions may include subject, target identifier, summary, and evidence. This material is used for review and safety actions.

Technical and usage data. We may process API request metadata, rate-limit counters, health checks, error logs, IP addresses, device or browser information, and similar operational telemetry needed to secure and operate the Services.

3. Identifier privacy classifications

Identifier types carry a protocol privacy classification (for example NORMAL, SENSITIVE, or HIGH_SENSITIVITY). Sensitive types may require authentication for availability checks and may redact or withhold raw values on public resolve responses according to protocol rules. Exact behavior for each type is described in the protocol documentation and identifier-type definitions.

Even when a value is redacted in a public response, authorized parties (such as the controller, approved providers, or operators) may still access operational data needed to manage the mapping.

4. How we use information

We use information to:

(a) provide registry, resolve, dashboard, Free API, namespace, and operator features; (b) review applications and enforce eligibility; (c) detect abuse, fraud signals, rate-limit violations, and security incidents; (d) process complaints and take safety actions such as warn, suspend, revoke, or reclaim; (e) improve reliability and documentation; and (f) communicate about service changes or support when you contact us.

We do not sell personal information. We do not use registry evidence as advertising profiles.

5. What may be public or shared with integrators

Resolve responses are designed for wallet and payment-app lookup. Data returned to authenticated or public clients may include display information, payment readiness, destinations, and status fields needed to complete a send flow, subject to privacy classification rules.

If you register an identifier people can look up, you should assume associated payment metadata may be retrieved by compatible clients worldwide. Do not register identifiers or destinations you are not prepared to expose under the protocol’s rules.

6. Sharing with service providers and legal requests

We use infrastructure and vendors (such as hosting, databases, authentication, and email) to operate the Services. They process data only as needed to provide those functions.

We may disclose information if required by law, regulation, legal process, or to protect the rights, safety, and integrity of users, the protocol, or the public. Operator actions on identifiers are part of protocol governance and may be visible in status changes or audit logs available to authorized roles.

7. Retention

We retain account, registry, complaint, and log data for as long as needed to operate the Services, meet security and audit needs, resolve disputes, and comply with law. Removed or revoked identifiers may leave residual history, cooldown, or audit records as described in protocol documentation.

8. Security

We apply technical and organizational measures appropriate to a resolution service, including access controls for dashboard and operator roles, API key handling, and logging practices. No method of transmission or storage is fully secure. You are responsible for protecting your keys, sessions, and devices.

9. Your choices

You may update or remove identifiers you control through the dashboard or APIs, subject to protocol cooldowns and operator policy. You may stop using the Services and request account-related assistance via contact. Some registry history and safety records may be retained after deletion requests where needed for security, dispute handling, or legal compliance.

10. Children

The Services are not directed to children, and we do not knowingly collect personal information from children. If you believe a child has provided information, contact us so we can take appropriate steps.

11. International processing

Information may be processed in countries where we or our providers operate. By using the Services, you understand that your information may be transferred to jurisdictions with different data-protection rules than your own.

12. Changes

We may update this notice as the product evolves. The current version will be posted on this page. Material changes may also be called out in the dashboard or documentation when practical.

13. Contact

Privacy questions: contact. Related pages: Terms of use, About, Report / Dispute.