CoreLoop · Privacy & Data
CoreLoop privacy & data
Read from CoreLoop's own page on 2026-11-09. 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
value: both
We are the controller of the personal data we hold for our own purposesRead from CoreLoop's own page on 2026-11-09
Data categories
category: identifying
Identity, from our authentication provider: email address, first and last name, and profile image.Read from CoreLoop's own page on 2026-11-09
category: contact
Either way we receive your name and message, and — if you provide them — your email address, phone number and a subject line.Read from CoreLoop's own page on 2026-11-09
category: behavioral
We measure which pages are visited and which features are opened.Read from CoreLoop's own page on 2026-11-09
category: device
a value derived from the network address and browser details your browser already sendsRead from CoreLoop's own page on 2026-11-09
category: communication
Anything you write into your profile, upload as a document or image, or type into a cancellation survey.Read from CoreLoop's own page on 2026-11-09
Purposes
purpose: Run account, publish profile, serve page and agent endpoints
Run your account, publish your profile, serve your page and agent endpoints, and support youRead from CoreLoop's own page on 2026-11-09
purpose: Payment and subscription management
Take payment, manage your subscription, and handle cancellationsRead from CoreLoop's own page on 2026-11-09
purpose: Newsletter
Consent is reserved for the one thing that is genuinely optional: the newsletter.Read from CoreLoop's own page on 2026-11-09
Retention
scope: Individual agent and page interaction recordsperiod: 90 days
Raw records are deleted after 90 days, leaving only daily counts.Read from CoreLoop's own page on 2026-11-09
scope: Deleted company dataperiod: seven days
The data is kept for seven days .Read from CoreLoop's own page on 2026-11-09
scope: Backup copies of uploaded filesperiod: thirty days
Every backup copy is deleted thirty days after it was takenRead from CoreLoop's own page on 2026-11-09
scope: Resolved or spam support ticketsperiod: 180 days
Resolved or spam support tickets, their messages and their attachments 180 daysRead from CoreLoop's own page on 2026-11-09
Residency
region: Ireland
Our database, our file storage and the application servers that run CoreLoop are all located in Ireland.Read from CoreLoop's own page on 2026-11-09
region: EU (email)
Email is sent and received through our provider's EU region.Read from CoreLoop's own page on 2026-11-09
International transfers
The page states nothing on this.
Subprocessors
Who else processes data for usRead from CoreLoop's own page on 2026-11-09
Data processing agreement
Deletion
route: Self-service in account settings, or request via support@coreloop.so
Delete your account. Delete your company, if you own it.Read from CoreLoop's own page on 2026-11-09
Data subject rights
right: Access
Access — a copy of the personal data we hold about you, and an explanation of what we do with it.Read from CoreLoop's own page on 2026-11-09
right: Rectification
Rectification — correction of anything inaccurate, and completion of anything incomplete.Read from CoreLoop's own page on 2026-11-09
right: Erasure
Erasure — deletion, where we have no overriding reason to keep it.Read from CoreLoop's own page on 2026-11-09
right: Restriction
Restriction — a pause on our use of it while a dispute about it is resolved.Read from CoreLoop's own page on 2026-11-09
right: Portability
Portability — the data you gave us, in a structured, machine-readable form, where we process it by consent or under our contract with you.Read from CoreLoop's own page on 2026-11-09
right: Objection
Objection — to any processing we base on legitimate interests, including our security and telemetry processing.Read from CoreLoop's own page on 2026-11-09
Sale or sharing
Document
Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page