Privacy Policy

Privacy & Data Handling Policy

This policy explains how URAPIS handles account data, marketplace activity, API usage metadata, payment references, and security logs needed to run the platform.

Last updated: 12 May 2026

Data we process

URAPIS collects the minimum operational data needed for marketplace, billing, security, and support.

  • Account details such as name, email, profile metadata, authentication state, and role-related activity.
  • Marketplace data such as subscriptions, API keys, product interactions, price-change decisions, and wallet ledger entries.
  • Technical metadata such as request path, method, timestamps, status, usage count, and gateway request identifiers.
  • Payment references from payment processors; card or e-wallet credentials are handled by the payment provider unless explicitly stored through a compliant tokenized flow.

Why we use data

Data is used to operate URAPIS, protect users, process billing, and improve reliability.

  • Authenticate users, authorize API access, enforce subscriptions, calculate prepaid usage, and reconcile wallet top-ups.
  • Detect abuse, investigate security incidents, support disputes, and comply with lawful requests.
  • Notify consumers and providers about billing, price changes, product status, account events, and security issues.

Data sharing

URAPIS shares data only where required to deliver marketplace functionality.

  • Payment providers receive the payment information needed to process top-ups, recurring charges, or payment-method registration.
  • Providers may see product-level analytics and consumer activity required for support, not consumer secrets or full payment credentials.
  • URAPIS does not sell personal data. Legal disclosure may occur only when required by valid law or platform safety obligations.

Retention & rights

Operational records are kept only as long as needed for compliance, billing, security, and dispute handling.

  • Users may request account correction or deletion subject to transaction, audit, fraud-prevention, and legal retention requirements.
  • Security logs, wallet ledgers, invoices, and consent history may be retained to preserve billing integrity.

This information is provided for informational purposes only and does not constitute legal advice. Please consult a qualified legal professional for advice regarding your specific situation.