Clipkit · Privacy & Data

Clipkit privacy & data

Read from Clipkit'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

value: controller
Controller: Clipkit, Inc. ("Clipkit", "we", "us")
Read from Clipkit's own page on 2026-11-09

Data categories

category: identifying
Account information: name, email, password (hashed), organization, and authentication data when you register or sign in.
Read from Clipkit's own page on 2026-11-09
category: financial
We do not store full card numbers; we receive limited billing metadata (e.g., last four digits, plan, status).
Read from Clipkit's own page on 2026-11-09
category: location
approximate location derived from IP.
Read from Clipkit's own page on 2026-11-09
category: device
Usage & device data: log data, IP address, browser/device info, pages and features used, timestamps, and approximate location derived from IP.
Read from Clipkit's own page on 2026-11-09
category: communication
Communications: messages you send us (support, abuse reports).
Read from Clipkit's own page on 2026-11-09
category: other
Content & assets: the video sources (JSON), uploaded or generated assets (images, screenshots, audio, video), and renders you create with the Service.
Read from Clipkit's own page on 2026-11-09

Purposes

purpose: Provide the Service
Provide the Service: create accounts, host/render/store/display your content, deliver links and exports.
Read from Clipkit's own page on 2026-11-09
purpose: Billing
Billing: process subscriptions and payments via our payment processor.
Read from Clipkit's own page on 2026-11-09
purpose: Improve the Service
Improve the Service: we use aggregated and de-identified usage data to analyze and improve the Service.
Read from Clipkit's own page on 2026-11-09
purpose: Safety and moderation
Safety & moderation: detect and prevent abuse and enforce our Acceptable Use Policy.
Read from Clipkit's own page on 2026-11-09
purpose: Marketing
Marketing: for free/anonymous tiers, we may feature content per our Terms §4(b); you can opt out.
Read from Clipkit's own page on 2026-11-09

Retention

scope: Anonymous content and assetsperiod: 7 days
Anonymous content & assets: deleted automatically after 7 days .
Read from Clipkit's own page on 2026-11-09
scope: Account content and assets
Account content & assets: retained while your account is active and within your plan's storage quota; deleted or anonymized after account closure, subject to backups and legal-hold requirements.
Read from Clipkit's own page on 2026-11-09
scope: Logs and security dataperiod: 12 months
Logs & security data: retained for 12 months .
Read from Clipkit's own page on 2026-11-09

Residency

region: United States
We may process information in the United States .
Read from Clipkit's own page on 2026-11-09

International transfers

mechanism: SCC
Where required, we use appropriate safeguards (e.g., Standard Contractual Clauses) for cross-border transfers.
Read from Clipkit's own page on 2026-11-09

Subprocessors

Supabase — database, storage, authentication
Read from Clipkit's own page on 2026-11-09

Data processing agreement

Deletion

route: contact support@clipkit.dev
To exercise these rights, contact support@clipkit.dev .
Read from Clipkit's own page on 2026-11-09

Data subject rights

right: access, correct, delete, port, restrict, object
you may have rights to access, correct, delete, port, restrict, or object to processing of your personal information
Read from Clipkit's own page on 2026-11-09
right: withdraw consent or opt out
to withdraw consent or opt out of certain processing
Read from Clipkit's own page on 2026-11-09
right: complaint to supervisory authority
You may also lodge a complaint with your supervisory authority.
Read from Clipkit's own page on 2026-11-09

Sale or sharing

stance: prohibited
We do not sell your personal information.
Read from Clipkit'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