Privacy

Sharvora is designed for machine-to-machine API use with minimal account data. Paid API calls do not require a Sharvora customer account.

Data we process

We may process request metadata, endpoint/path, timing, HTTP status, settlement/delivery state, operational logs, and data that a caller submits to a requested service. Some services, such as Decision Journal, intentionally persist the supplied record so a later audit can reference it.

Wallet and payment data

Sharvora does not request wallet seed phrases or private keys. The analytics layer is designed to store a salted hash for repeat-payer measurement rather than a raw payer address. Raw payment signatures are not intentionally retained by Sharvora analytics. Blockchain settlement itself is public by nature.

Infrastructure

Hosting, database, blockchain, facilitator, and network providers may process technical logs or transaction data under their own terms. External providers linked from Sharvora are separate services.

Use of data

Operational data is used to deliver requested services, prevent abuse, troubleshoot failures, measure reliability, understand paid usage, and improve products. Sharvora does not sell personal information to advertisers.

Retention

Retention varies by data type and operational need. Deterministic one-shot inputs are not intentionally persisted unless a product explicitly requires persistence; infrastructure logs and durable decision records can remain longer.

This page describes Sharvora's current launch policy. It may be updated as the service, company structure, or applicable requirements evolve.