Vaultfire Protocol · Privacy & Data

Vaultfire Protocol privacy & data

Read from Vaultfire Protocol's own page on 2026-11-10. 25 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Role

The page states nothing on this.

Data categories

category: identifying
Wallet address. When you connect a wallet, we see the public address.
Read from Vaultfire Protocol's own page on 2026-11-10
category: contact
Email address (optional). Only if you contact us, opt into updates, or use a feature that explicitly asks for it.
Read from Vaultfire Protocol's own page on 2026-11-10
category: device
Server logs. Standard logs may record IP, user agent, request path, timestamp, and response code.
Read from Vaultfire Protocol's own page on 2026-11-10
category: communication
Content you submit. Anything you publish through the Service (agent metadata, dispute claims, profile fields).
Read from Vaultfire Protocol's own page on 2026-11-10

Purposes

purpose: Operate, maintain, and improve the Service
Operate, maintain, and improve the Service
Read from Vaultfire Protocol's own page on 2026-11-10
purpose: Respond to inquiries and provide support
Respond to your inquiries and provide support
Read from Vaultfire Protocol's own page on 2026-11-10
purpose: Security, fraud and abuse prevention
Detect, prevent, and address security incidents, fraud, and abuse
Read from Vaultfire Protocol's own page on 2026-11-10
purpose: Legal compliance
Comply with legal obligations
Read from Vaultfire Protocol's own page on 2026-11-10
purpose: Enforce Terms of Service
Enforce our Terms of Service
Read from Vaultfire Protocol's own page on 2026-11-10

Retention

scope: Server logsperiod: ~30 days
Server logs: ~30 days
Read from Vaultfire Protocol's own page on 2026-11-10
scope: Email correspondence
Email correspondence: Retained as long as needed for support, then deleted on request
Read from Vaultfire Protocol's own page on 2026-11-10
scope: On-chain dataperiod: Permanent
On-chain data: Permanent — we cannot delete data from public blockchains
Read from Vaultfire Protocol's own page on 2026-11-10
scope: Off-chain account data
Off-chain account data (if any): Retained as long as your account is active; deletable on request
Read from Vaultfire Protocol's own page on 2026-11-10

Residency

region: United States
If you access the Service from outside the United States, your information may be transferred to, stored, and processed in the U.S.
Read from Vaultfire Protocol's own page on 2026-11-10

International transfers

mechanism: SCC
We rely on appropriate safeguards (such as Standard Contractual Clauses where required) for international transfers from the EEA/UK.
Read from Vaultfire Protocol's own page on 2026-11-10

Subprocessors

Data processing agreement

Deletion

route: Email ghostkey316@proton.me
To exercise these rights, email ghostkey316@proton.me .
Read from Vaultfire Protocol's own page on 2026-11-10

Data subject rights

right: Access
Access your personal data
Read from Vaultfire Protocol's own page on 2026-11-10
right: Rectify
Rectify inaccurate data
Read from Vaultfire Protocol's own page on 2026-11-10
right: Erase
Erase your personal data — subject to legal exceptions and the immutable nature of public blockchains
Read from Vaultfire Protocol's own page on 2026-11-10
right: Restrict processing
Restrict processing
Read from Vaultfire Protocol's own page on 2026-11-10
right: Object to processing
Object to processing
Read from Vaultfire Protocol's own page on 2026-11-10
right: Data portability
Data portability
Read from Vaultfire Protocol's own page on 2026-11-10
right: Withdraw consent
Withdraw consent at any time
Read from Vaultfire Protocol's own page on 2026-11-10
right: Lodge complaint
Lodge a complaint with your supervisory authority
Read from Vaultfire Protocol's own page on 2026-11-10

Sale or sharing

stance: prohibited
We do not sell your personal information.
Read from Vaultfire Protocol's own page on 2026-11-10

Document

Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page