Inkle · Privacy & Data
Inkle privacy & data
Read from Inkle's own page on 2026-11-09. 23 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
identity data (name, date of birth, and, where required, government ID)Read from Inkle's own page on 2026-11-09
category: financial
financial and tax data (books, transactions, invoices, payroll, cap tables, tax IDs, prior returns)Read from Inkle's own page on 2026-11-09
category: device
device and connection data (including IP address, which is personal data under several laws)Read from Inkle's own page on 2026-11-09
category: behavioral
browser and usage/log data, and cookie dataRead from Inkle's own page on 2026-11-09
Purposes
purpose: provide services and make filings
We use personal information to provide the services and make filingsRead from Inkle's own page on 2026-11-09
purpose: security and fraud prevention
secure the platform and prevent fraudRead from Inkle's own page on 2026-11-09
purpose: legal and record-keeping compliance
comply with legal, tax, and record-keeping obligationsRead from Inkle's own page on 2026-11-09
purpose: analytics and improvement
analyze and improve our services (including benchmarking with de-identified data)Read from Inkle's own page on 2026-11-09
Retention
scope: tax/financial records and Deliverablesperiod: up to 7 years
tax/financial records and Deliverables up to 7 yearsRead from Inkle's own page on 2026-11-09
scope: identity/verification documentsperiod: while the account is active plus any statutory minimum
identity/verification documents while the account is active plus any statutory minimumRead from Inkle's own page on 2026-11-09
scope: marketing dataperiod: 2 years of inactivity
marketing data until you opt out or 2 years of inactivityRead from Inkle's own page on 2026-11-09
scope: Customer Materials after relationship ends
we make Customer Materials available for export for 30 days, then delete them except records we must retain by law (up to 7 years)Read from Inkle's own page on 2026-11-09
Residency
region: United States and India
We process data in the United States and India, with appropriate safeguards for international transfers.Read from Inkle's own page on 2026-11-09
International transfers
mechanism: other
We process data in the United States and India, with appropriate safeguards for international transfers.Read from Inkle's own page on 2026-11-09
Subprocessors
listed in the DPA subprocessor scheduleRead from Inkle's own page on 2026-11-09
Data processing agreement
Deletion
route: contact privacy@inkle.ai or write to Inkle, Inc., Attn: Privacy Officer
a deletion request does not override a legal retention obligationRead from Inkle's own page on 2026-11-09
Data subject rights
right: access, correct, delete, restrict, object, portability, withdraw consent
Access, correct, delete, restrict, or object to processing; portability; withdraw consent; and complain to your supervisory authority (in the UK, the ICO).Read from Inkle's own page on 2026-11-09
right: California know, access, delete, correct, opt out of sale or sharing
Know, access, delete, and correct; opt out of the "sale" or "sharing" of personal information; limit use of sensitive personal information; and non-discriminationRead from Inkle's own page on 2026-11-09
right: India access, correction, erasure, grievance, nomination
As a Data Principal you may access a summary of your data and its processing; correct, complete, update, or erase it; seek grievance redressal; and nominate another person to exercise your rights.Read from Inkle's own page on 2026-11-09
Sale or sharing
stance: conditional
We do not sell your personal information for money. Some analytics/advertising tools may count as "sharing" or a "sale" under certain U.S. laws: you can opt out (Section 6).Read from Inkle'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