P2Flux API · Privacy & Data

P2Flux API privacy & data

Read from P2Flux API's own page on 2026-11-10. 19 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
name; work email; company; website or product URL; product type
Read from P2Flux API's own page on 2026-11-10
category: financial
approximate monthly payment volume, if you provide it
Read from P2Flux API's own page on 2026-11-10
category: location
IP addresses and security logs
Read from P2Flux API's own page on 2026-11-10
category: device
the browser user agent
Read from P2Flux API's own page on 2026-11-10
category: communication
your message
Read from P2Flux API's own page on 2026-11-10
category: identifying
wallet addresses involved in processing a payment
Read from P2Flux API's own page on 2026-11-10

Purposes

purpose: evaluate and respond to integration enquiries
We use this information to evaluate the enquiry, understand the integration and respond to you.
Read from P2Flux API's own page on 2026-11-10
purpose: operate, secure, monitor and troubleshoot the Services
processed to provide, secure, monitor and troubleshoot the Services and to report transaction status back to the integrating system
Read from P2Flux API's own page on 2026-11-10
purpose: sanctions screening
it checks the wallet address paying and the merchant’s receiving wallet address against the public U.S. OFAC Specially Designated Nationals list
Read from P2Flux API's own page on 2026-11-10
purpose: admitting paying Telegram channel members
We process this to perform the service the channel owner and the subscriber asked for: admitting paying members and removing them when the subscription stops (contract).
Read from P2Flux API's own page on 2026-11-10

Retention

scope: web server logsperiod: 14 days
Those server logs are kept for 14 days and then deleted.
Read from P2Flux API's own page on 2026-11-10
scope: enquiry correspondenceperiod: up to 24 months after the last substantive communication
Enquiry correspondence is normally retained for up to 24 months after the last substantive communication.
Read from P2Flux API's own page on 2026-11-10
scope: encrypted backups of service configurationperiod: 90 days
Encrypted backups of service configuration are kept for 90 days.
Read from P2Flux API's own page on 2026-11-10
scope: subscription recordsperiod: 30 days after the subscription ended
A subscription record is deleted from P2Flux’s active systems 30 days after the subscription ended
Read from P2Flux API's own page on 2026-11-10

Residency

The page states nothing on this.

International transfers

The page states nothing on this.

Subprocessors

Today that means server hosting (Vultr), email delivery for the enquiry form and operational alerts (Resend), business email for the addresses shown on this site (Google Workspace), and encrypted off-site backups of service configuration (Backblaze B2).
Read from P2Flux API's own page on 2026-11-10

Data processing agreement

Deletion

route: contact contact@p2flux.com
To exercise a right, contact contact@p2flux.com .
Read from P2Flux API's own page on 2026-11-10

Data subject rights

right: access, correct, delete, restrict or object
applicable data-protection law may give you rights to access, correct, delete, restrict or object to certain processing of personal information we hold about you
Read from P2Flux API's own page on 2026-11-10
right: complain to supervisory authority
or to complain to a competent supervisory authority
Read from P2Flux API's own page on 2026-11-10

Sale or sharing

stance: prohibited
P2Flux does not sell personal information to advertisers.
Read from P2Flux API'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