Skip to content

Wording of 2026-10-23

What we collect, why, and who handles it.

What ClaraDB collects, why, who handles it and what you can choose.

1. Who is responsible (controller)

The Plain Works Co., Ltd. operates ClaraDB and is the controller of the personal data described here. Contact for privacy questions and requests: hello@claradb.com. Privacy contact under the Korean Personal Information Protection Act: Privacy team (개인정보보호 담당 부서), hello@claradb.com. This contact also serves supervisory authorities. If we have no establishment in the EU or UK and the law requires a representative, we will name one here.

2. What we collect, why, and the legal basis

Data
Why
Legal basis (GDPR and UK GDPR)
Email address, display name, sign-in history
Create your account, sign you in, keep it secure
Contract (providing the service); legitimate interests (security)
Workspace content: SKU names and codes, supplier names, materials, markets, files you import, results, alerts, members and activity log
Run the checks, alerts and evidence packs you ask for
Contract
Emails we send: sign-in links, invitations, alerts, replies
Deliver the service and answer you
Contract; legitimate interests (alerts you have not switched off)
Contact and corrections forms: email, name, company, message, page and source links
Reply to you, check a correction, run the business
Legitimate interests; steps at your request before a contract
IP address and request details, stored with sign-in requests, forms and invitations, and in server logs
Stop abuse, enforce rate limits, keep the service secure
Legitimate interests (security and fraud prevention)
Analytics: pages viewed, clicks, device and browser, approximate location from the IP address, a random visitor id, your account id after sign-in, errors and performance. Not your email address, and no SKU content
Count visits, find errors, improve the product
Consent where the law requires it (EU, EEA, UK, Switzerland); legitimate interests elsewhere
Free checks: the product facts you enter appear in the page address, which your browser and our host's (Vercel) logs can see. We do not save them to an account
Show you the result and let you share it
Contract; legitimate interests
  • Email address, display name, sign-in history
    Why
    Create your account, sign you in, keep it secure
    Legal basis (GDPR and UK GDPR)
    Contract (providing the service); legitimate interests (security)
  • Workspace content: SKU names and codes, supplier names, materials, markets, files you import, results, alerts, members and activity log
    Why
    Run the checks, alerts and evidence packs you ask for
    Legal basis (GDPR and UK GDPR)
    Contract
  • Emails we send: sign-in links, invitations, alerts, replies
    Why
    Deliver the service and answer you
    Legal basis (GDPR and UK GDPR)
    Contract; legitimate interests (alerts you have not switched off)
  • Contact and corrections forms: email, name, company, message, page and source links
    Why
    Reply to you, check a correction, run the business
    Legal basis (GDPR and UK GDPR)
    Legitimate interests; steps at your request before a contract
  • IP address and request details, stored with sign-in requests, forms and invitations, and in server logs
    Why
    Stop abuse, enforce rate limits, keep the service secure
    Legal basis (GDPR and UK GDPR)
    Legitimate interests (security and fraud prevention)
  • Analytics: pages viewed, clicks, device and browser, approximate location from the IP address, a random visitor id, your account id after sign-in, errors and performance. Not your email address, and no SKU content
    Why
    Count visits, find errors, improve the product
    Legal basis (GDPR and UK GDPR)
    Consent where the law requires it (EU, EEA, UK, Switzerland); legitimate interests elsewhere
  • Free checks: the product facts you enter appear in the page address, which your browser and our host's (Vercel) logs can see. We do not save them to an account
    Why
    Show you the result and let you share it
    Legal basis (GDPR and UK GDPR)
    Contract; legitimate interests

We do not make decisions about you by automated means that have legal or similarly significant effects. Providing the data for your account is needed to use the service; giving analytics consent is optional.

3. Who processes it

Processors act on our instructions. Each has a data processing agreement with us.

Processor
Role
Data
Location
Vercel
Hosting and delivery of the website, workspace and API
Requests, IP address, technical logs
United States; delivery through Vercel's global network
Cloudflare
DNS for claradb.com
DNS queries
Global network; processing may occur in any country where Cloudflare operates
Supabase
Database and sign-in
Everything in your account and workspace, IP addresses in request logs
Project region: us-east-1 (Amazon Web Services, N. Virginia, United States)
PostHog (US Cloud)
Product analytics, error reports, sampled session replay
Analytics events, with the IP address processed for approximate location. Loaded only after consent in the EU, EEA, UK and Switzerland. No replay in the signed-in app or on sign-in pages
United States
Resend
Sending email
Recipient address, message content
United States
Paddle
Merchant of record for paid plans: checkout, payment, tax, invoices, refunds
Name, email address, billing country and payment details you give at checkout. We do not receive card numbers; we receive a customer id, subscription status and plan
United Kingdom and the countries where Paddle operates
  • Vercel
    Role
    Hosting and delivery of the website, workspace and API
    Data
    Requests, IP address, technical logs
    Location
    United States; delivery through Vercel's global network
  • Cloudflare
    Role
    DNS for claradb.com
    Data
    DNS queries
    Location
    Global network; processing may occur in any country where Cloudflare operates
  • Supabase
    Role
    Database and sign-in
    Data
    Everything in your account and workspace, IP addresses in request logs
    Location
    Project region: us-east-1 (Amazon Web Services, N. Virginia, United States)
  • PostHog (US Cloud)
    Role
    Product analytics, error reports, sampled session replay
    Data
    Analytics events, with the IP address processed for approximate location. Loaded only after consent in the EU, EEA, UK and Switzerland. No replay in the signed-in app or on sign-in pages
    Location
    United States
  • Resend
    Role
    Sending email
    Data
    Recipient address, message content
    Location
    United States
  • Paddle
    Role
    Merchant of record for paid plans: checkout, payment, tax, invoices, refunds
    Data
    Name, email address, billing country and payment details you give at checkout. We do not receive card numbers; we receive a customer id, subscription status and plan
    Location
    United Kingdom and the countries where Paddle operates

Paddle is not a processor: it sells paid plans to you as merchant of record and is the controller of your payment data. The full list is on the subprocessors page.

We do not sell personal data and do not share it for cross-context behavioral advertising. We disclose data to authorities only where the law requires it.

4. International transfers

Some processors are in, or can access data from, the United States and other countries outside the EU, EEA, UK and Korea. Where the destination has no adequacy decision, the transfer relies on the European Commission's standard contractual clauses (with the UK addendum or the UK international data transfer agreement for UK data), or on the EU-US Data Privacy Framework where the recipient is certified. You can ask us for a copy of the safeguards. For Korean users, the table below gives the notice of overseas transfer under the Personal Information Protection Act.

Recipient and privacy policy (이전받는 자)
Country (이전 국가)
Items (이전 항목)
Purpose and holding period (이용 목적 및 보유 기간)
When and how (이전 일시 및 방법)
United States
IP address, request details
Hosting and delivery; logs kept for a limited period set by Vercel
When you use the service; sent over an encrypted network connection
United States and the countries of Cloudflare's network
DNS queries (IP address of the resolver)
DNS; logs kept up to 30 days
When you use the service; sent over an encrypted network connection
us-east-1 (Amazon Web Services, N. Virginia, United States)
Email address, display name, account id, workspace content
Database and sign-in; until you delete the account or workspace
When you use the service; sent over an encrypted network connection
United States
Random visitor id, account id after sign-in, usage events, error data
Analytics and error tracking; kept 12 months
When you use the service and have not rejected analytics; sent over an encrypted network connection
Plus Five Five, Inc. (Resend)Resend privacy policy(opens in a new tab)
United States
Email address, message content
Sending sign-in links, invitations and alerts; delivery records kept up to 30 days
When we send you an email; sent over an encrypted network connection
Paddle.com Market Limited and its affiliatesPaddle privacy policy(opens in a new tab)
United Kingdom and the countries where Paddle operates
Name, email address, billing details, payment details entered at checkout
Taking payment and issuing invoices as seller; kept as Paddle's policy and tax law require
When you buy a paid plan; sent over an encrypted network connection
  • Country (이전 국가)
    United States
    Items (이전 항목)
    IP address, request details
    Purpose and holding period (이용 목적 및 보유 기간)
    Hosting and delivery; logs kept for a limited period set by Vercel
    When and how (이전 일시 및 방법)
    When you use the service; sent over an encrypted network connection
  • Country (이전 국가)
    United States and the countries of Cloudflare's network
    Items (이전 항목)
    DNS queries (IP address of the resolver)
    Purpose and holding period (이용 목적 및 보유 기간)
    DNS; logs kept up to 30 days
    When and how (이전 일시 및 방법)
    When you use the service; sent over an encrypted network connection
  • Country (이전 국가)
    us-east-1 (Amazon Web Services, N. Virginia, United States)
    Items (이전 항목)
    Email address, display name, account id, workspace content
    Purpose and holding period (이용 목적 및 보유 기간)
    Database and sign-in; until you delete the account or workspace
    When and how (이전 일시 및 방법)
    When you use the service; sent over an encrypted network connection
  • Country (이전 국가)
    United States
    Items (이전 항목)
    Random visitor id, account id after sign-in, usage events, error data
    Purpose and holding period (이용 목적 및 보유 기간)
    Analytics and error tracking; kept 12 months
    When and how (이전 일시 및 방법)
    When you use the service and have not rejected analytics; sent over an encrypted network connection
  • Plus Five Five, Inc. (Resend)Resend privacy policy(opens in a new tab)
    Country (이전 국가)
    United States
    Items (이전 항목)
    Email address, message content
    Purpose and holding period (이용 목적 및 보유 기간)
    Sending sign-in links, invitations and alerts; delivery records kept up to 30 days
    When and how (이전 일시 및 방법)
    When we send you an email; sent over an encrypted network connection
  • Paddle.com Market Limited and its affiliatesPaddle privacy policy(opens in a new tab)
    Country (이전 국가)
    United Kingdom and the countries where Paddle operates
    Items (이전 항목)
    Name, email address, billing details, payment details entered at checkout
    Purpose and holding period (이용 목적 및 보유 기간)
    Taking payment and issuing invoices as seller; kept as Paddle's policy and tax law require
    When and how (이전 일시 및 방법)
    When you buy a paid plan; sent over an encrypted network connection

How to refuse (거부 방법): do not use the service, delete your account in the account settings, or reject analytics for the PostHog transfer. Because these providers run the service, refusing the transfer to Vercel, Supabase or Resend means we cannot provide the service to you. Privacy contact (개인정보 보호 담당): Privacy team (개인정보보호 담당 부서), hello@claradb.com.

5. Analytics, cookies and your choice

Name
Purpose
Lifetime
cl_at, cl_rt, cl_si
Keep you signed in (strictly necessary)
Up to 30 days, removed when you sign out
cl_consent
Remember your analytics choice (strictly necessary)
6 months
ph_* cookie and local storage
PostHog visitor id for analytics. Set only after consent in the EU, EEA, UK and Switzerland, and not when your browser sends Do Not Track or Global Privacy Control
Up to 12 months
  • cl_at, cl_rt, cl_si
    Purpose
    Keep you signed in (strictly necessary)
    Lifetime
    Up to 30 days, removed when you sign out
  • cl_consent
    Purpose
    Remember your analytics choice (strictly necessary)
    Lifetime
    6 months
  • ph_* cookie and local storage
    Purpose
    PostHog visitor id for analytics. Set only after consent in the EU, EEA, UK and Switzerland, and not when your browser sends Do Not Track or Global Privacy Control
    Lifetime
    Up to 12 months
  • If you are in the EU, EEA, UK or Switzerland (or we cannot tell), analytics do not load until you accept. Rejecting is as easy as accepting. You can change the choice below at any time.
  • If your browser sends Do Not Track or Global Privacy Control, we load no browser analytics and treat it as a rejection.
  • A sample of visits is recorded as session replay. Form fields are masked, and replay does not run in the signed-in app or on sign-in pages.
  • Page addresses sent to analytics have their query strings removed (only campaign tags are kept), and workspace and SKU identifiers and sign-in tokens are replaced. Event properties carry counts and ids, not email addresses or free text.
  • Server-side events (sign-up, checks run, inquiries) follow the same choice. They carry your account id, not your email.

6. How long we keep it

Data
Kept
Workspace data (SKUs, results, alerts, members)
Until you or an owner delete it or the workspace. Deleted SKUs stay in Trash until an admin removes them
Activity log of a workspace
As long as the workspace exists
Account (email, display name)
Until you delete your account or ask us to; we then remove it within 30 days
Sign-in request log (email, IP address)
7 days
Contact inquiries and correction reports, with the IP address
24 months, then deleted. A correction's outcome is kept without personal data
Analytics and replay in PostHog
12 months
Email delivery records at Resend
As set by Resend, up to 30 days
Server logs at Vercel, kept as long as Vercel sets
As set by Vercel
  • Workspace data (SKUs, results, alerts, members)
    Kept
    Until you or an owner delete it or the workspace. Deleted SKUs stay in Trash until an admin removes them
  • Activity log of a workspace
    Kept
    As long as the workspace exists
  • Account (email, display name)
    Kept
    Until you delete your account or ask us to; we then remove it within 30 days
  • Sign-in request log (email, IP address)
    Kept
    7 days
  • Contact inquiries and correction reports, with the IP address
    Kept
    24 months, then deleted. A correction's outcome is kept without personal data
  • Analytics and replay in PostHog
    Kept
    12 months
  • Email delivery records at Resend
    Kept
    As set by Resend, up to 30 days
  • Server logs at Vercel, kept as long as Vercel sets
    Kept
    As set by Vercel

7. Your rights

  • EU, EEA, UK and Switzerland (GDPR and UK GDPR): access, correction, erasure, restriction, portability, objection to processing based on legitimate interests, and withdrawal of consent at any time (withdrawal does not affect earlier processing). You may complain to your supervisory authority, for example the ICO in the UK or your national data protection authority in the EU.
  • California (CCPA and CPRA): in the last 12 months we collected identifiers (email, IP address, device ids), commercial information you enter (SKU data) and internet activity (analytics), for the purposes in section 2. We do not sell or share personal information, and use no sensitive personal information to infer characteristics. You may ask to know, delete or correct your data, and we will not discriminate against you for asking.
  • Korea (PIPA): you may ask to see, correct, delete or suspend processing of your personal information, and withdraw consent. We handle requests within 10 days.
  • To use a right, write to hello@claradb.com or use the contact form. We may need to confirm your identity. Workspace owners can also export workspace data from settings.

We reply within one month (GDPR), 45 days (CCPA) or 10 days (PIPA).

8. Children

ClaraDB is for business use and is not directed at anyone under 16. We do not knowingly collect personal data from children. If you think a child has given us data, contact us and we will delete it.

9. Security

Sign-in links are single use and expire. Data is encrypted in transit. Access to workspace data is limited by membership and checked in the database. API keys are stored only as hashes. No system is perfectly secure; we will tell affected users and authorities of a personal data breach as the law requires.

10. Changes

We will update this notice when our processing changes and show the version date at the top. Material changes are announced in the app or by email. See also the terms of use.

Other legal pages