blinkpdf-io · Privacy & Data
blinkpdf-io privacy & data
Read from blinkpdf-io's own page on 2026-11-09. 21 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Role
value: controller
Blink PDF is operated by Diego Cesar Lerma Torres , an individual (“I”, “me”, or “my”).Read from blinkpdf-io's own page on 2026-11-09
Data categories
category: identifying
Name — your first name, last name, and a display name associated with your account.Read from blinkpdf-io's own page on 2026-11-09
category: contact
Email address — to identify your account, send transactional emails (email verification, password reset), and contact you about the Service.Read from blinkpdf-io's own page on 2026-11-09
category: device
the IP address and browser user-agent string associated with the sessionRead from blinkpdf-io's own page on 2026-11-09
category: financial
Subscription metadata — subscription ID, status, the price/plan you are on, the current period end dateRead from blinkpdf-io's own page on 2026-11-09
category: behavioral
Usage events (an append-only ledger): your user ID, the API key ID, the metric ( pdf_render ), the quantity of render units (1–16)Read from blinkpdf-io's own page on 2026-11-09
Purposes
purpose: Create and manage account
Create and manage your account.Read from blinkpdf-io's own page on 2026-11-09
purpose: Process payments and meter usage
Process payments and meter usage for billing.Read from blinkpdf-io's own page on 2026-11-09
purpose: Transactional emails
Send transactional emails (email verification, password reset).Read from blinkpdf-io's own page on 2026-11-09
purpose: Operate, secure, and debug
Operate, secure, and debug the Service, including abuse prevention and rate limiting.Read from blinkpdf-io's own page on 2026-11-09
Retention
scope: Account dataperiod: Until your account is deleted
Account data (name, email, hashed password) Until your account is deleted (see Section 8)Read from blinkpdf-io's own page on 2026-11-09
scope: MCP-hosted PDFsperiod: 24 hours
These files are stored for 24 hours , after which they are automatically removed.Read from blinkpdf-io's own page on 2026-11-09
scope: Direct API render contentperiod: Not stored
Direct API render content Not stored (held only briefly in memory; see Section 3)Read from blinkpdf-io's own page on 2026-11-09
scope: Usage and audit records
The Service does not currently apply an automatic purge to usage, aggregate, or audit records; they are retained for as long as needed for billing and audit.Read from blinkpdf-io's own page on 2026-11-09
Residency
region: United States (Virginia)
The Service is hosted in the United States (Virginia).Read from blinkpdf-io's own page on 2026-11-09
International transfers
mechanism: other
If you are located outside the United States, your data is transferred to and processed there, as well as by the sub-processors listed in Section 5.Read from blinkpdf-io's own page on 2026-11-09
Subprocessors
Data processing agreement
Deletion
route: Manual deletion on request by email to the privacy contact
There is no self-service data-export or account-deletion feature in the Service. To request access to or deletion of your data, contact me at [email protected] . Deletion is performed manuallyRead from blinkpdf-io's own page on 2026-11-09
Data subject rights
right: Access, correction, deletion, objection, restriction
Depending on your location, you may have rights to access, correct, or delete your personal data, and to object to or restrict certain processing.Read from blinkpdf-io's own page on 2026-11-09
right: GDPR and UK GDPR
EEA/UK residents may have rights under the GDPR and UK GDPR.Read from blinkpdf-io's own page on 2026-11-09
right: CCPA
California residents may have rights under the CCPA.Read from blinkpdf-io's own page on 2026-11-09
Sale or sharing
stance: prohibited
I do not sell or share personal data.Read from blinkpdf-io's own page on 2026-11-09
Document
Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page