PRIVACY

The leads stay on your computer. The account does not.

What we collect, why, who else touches it, how long it stays, and how to get a copy or delete it.

DRAFT, NOT YET IN FORCE

This page is a draft written from the source code, not a policy that has been reviewed by a lawyer. It has no legal effect until the owner of Chizuki has a lawyer review it and sets an effective date.

Everything in SQUARE BRACKETS is a placeholder for the owner to fill in: the company's legal name and registered address, the privacy contact address, the hosting region, the governing law, and how long to keep the records that nothing deletes yet. No company name, address or support address on this page is real.

Drafted 2026-08-31 from the code. Effective date: [TO BE SET BY THE OWNER]

01

Who is responsible for this data

The company responsible for the account data described here (the controller) is [CONTROLLER LEGAL NAME], of [REGISTERED ADDRESS]. Send privacy questions, rights requests and complaints to [PRIVACY CONTACT ADDRESS].

We have not appointed a data protection officer. Where the law requires a representative in the EU or the UK (Article 27), it is [REPRESENTATIVE, IF ONE IS APPOINTED].

02

The short version

Chizuki is a desktop app. The businesses it finds, the contacts, the page records it keeps as evidence, the scores, the AI check results and the do-not-contact list live in a database on your own computer, in the ~/.chizuki folder. Export files are ordinary files in the export folder the app shows, under Downloads/Chizuki unless you pick another folder. We never upload, sync or back up any of it. We hold no copy and have no way to get one.

What we hold is your account: your email address and when you confirmed it, a hash of your password (a one-way code that cannot be turned back into the password), one record per signed-in device, your billing history, a code that marks which account has had your mailbox's free credits, and one hash per lead you export so credits can be counted. We cannot turn that hash back into a website address, because the key it is made with stays on your computer. That is all.

03

What we collect, why, and on what legal basis

  • Email and hashed password. So your account exists and you can sign in. Your password is stored as a one-way hash, never in plain text. Legal basis: performance of the contract with you.
  • Mail server check. When an account is opened, our server asks the DNS, the internet's public directory of domains, which mail servers take mail for the address, to turn away temporary inboxes. Only the part of the address after the @ is looked up, and nothing from the answer is stored. Legal basis: our legitimate interest in keeping the free plan for mailboxes people keep.
  • Email confirmation. When you confirmed your email address with the link we sent, or by setting a new password from a reset email. The free plan's credits wait for it. The link itself is not stored: it carries its own expiry and a signature our server checks, and it can only confirm the address. Legal basis: performance of the contract.
  • Free credit claims. One row per mailbox that has had the free plan's credits: a code made from your email address with a secret only our server holds, after taking out a +tag and the dots of a Gmail address, and the account that has the credits. Addresses that reach the same mailbox make the same code, so the free credits go to one account per mailbox. Legal basis: our legitimate interest in keeping the free plan to one per mailbox.
  • Sign-in sessions. One record per signed-in device: a hashed sign-in key, the last four characters of that key so you can recognise it, whether it is a browser or an app sign-in, the device name, the operating system, the app version, when it was created and last renewed, when it expires, and when it was signed out. This is the "Devices signed in" list on your account page. Legal basis: performance of the contract.
  • Sign-in attempts. When the app asks for a sign-in code, we store the hashed code, the device name and operating system, the app version, the IP address the request came from and a rough location based on it, plus the status and times. You see this in the browser so you can check where a request came from before you approve it. Legal basis: our legitimate interest in account security.
  • Abuse counters. Counters tied to an IP address, an email address or its domain, an account, a browser that has signed in before, a sign-in code, or a founder licence sign-in and the networks it is used from. Each holds only a start time and a count. They stop repeated guessing, sign-up abuse and one sign-in being shared across many computers, and flag a domain whose addresses take the free credits many times in one day. Legal basis: our legitimate interest in keeping the service up.
  • Password reset links. A hashed code that expires after 30 minutes and records when it was used, so a reset link works once. Legal basis: performance of the contract.
  • Billing records. Plan, billing period, the price you chose, subscription status, renewal and cancellation dates, invoice number, amount, currency, refund times, and the card brand, last four digits and expiry month that Paddle reports back to us. Legal basis: performance of the contract, and legal obligation for the records tax law requires us to keep.
  • Credit usage. One row per lead you export. It holds a hash of that lead's website address, made on your computer, the time the credit was spent, the time we recorded it, and a refund time if the credit came back because you marked the lead do not contact or the export file could not be written. It exists so your monthly credits can be counted and so a lead you already exported from that machine does not charge you twice. The key for the hash is created on your computer, never leaves it and is never sent to us, so we cannot reverse the hash back to the domain or check a guess against it. What the row does tell us: that your account exported a lead at that moment, and, if the same hash arrives again, that the same lead was exported again from the same computer. We never receive the website address, the business name, the street address, the phone number or anything else about the lead. Legal basis: performance of the contract.
04

What we never receive

  • Your leads. Business names, addresses, phone numbers, email addresses, social profiles, website technology and hiring signals, scores, reasoning, AI check results, records of the pages the app read, run history, your profiles and your do-not-contact list. All of it is kept on your own computer and never reaches us. An AI check you ask for sends part of it to your model provider, as Model traffic below describes.
  • Your export files. Your export files (CSV, XLSX and JSON) are saved to the folder you chose. We never see them, and the app has no way to upload them.
  • Card numbers. Paddle takes the payment, and we never see your card. Paddle sends us only the card brand, the last four digits and the expiry month, so the billing screen can show which card paid.
  • Model traffic. If you connect an AI model, the app calls it from your computer with your own key, and sends it information about a lead only when you ask for an AI check on that lead. That call carries the business's listing details, its website text, its one and two star reviews, the three lines of your profile (what you sell, who it is for, who to skip) and the questions you added to it, with phone numbers and email addresses cut out first. Setup also asks that provider for its list of models, sending your key if you saved one, and the test button sends it a short test message, at most twice; neither carries anything about a business or a lead. Making a profile with AI, also only when you ask, sends it what you wrote about your offer, with the app's own fact list and example profiles, and nothing about a business or a lead. Your key is encrypted with your operating system's password store and kept in a file in the app folder that only your user account can read. It is never synced and never sent to us. On a system without that password store, the app falls back to storing that key base64-encoded in the same file, which is encoding and not encryption. The traffic goes straight from your computer to the provider you chose, which the app expects to use the same format as OpenAI, such as api.openai.com or openrouter.ai. It does not pass through us. We are neither the controller nor a processor for it, and that provider's own privacy terms cover it. You can leave the model unset and the app still works.
  • Analytics and crash reports. There is no analytics, no crash reporting, no error reporting, no session recording, no advertising and no tracking pixel. Our server has nowhere to receive any of it. We set two cookies of our own, and only after you sign in: the session cookie, and chz_known, which marks this browser as one that has signed in to your account, so wrong passwords tried elsewhere cannot lock it out. chz_known holds a random code and a signature, nothing about you, and lasts a year from your last sign-in in that browser. One thing on the site is not ours: the pricing page and the billing part of your account page load Paddle's checkout script from cdn.paddle.com so a checkout can open. You do not need to be signed in to visit those pages, and whatever that script stores in your browser belongs to Paddle under Paddle's own notice. No other page loads a third-party script, and none is loaded for analytics or advertising.
05

Who else touches it

  • Paddle. Paddle.com Market Ltd is the merchant of record (the seller) for every purchase. Paddle sells you the subscription, takes the payment and is separately responsible (an independent controller) for the payment details you enter with it, under its own privacy notice. It reports back to us the plan, the amount, the invoice number, and the card brand, last four digits and expiry. Paddle also reaches your browser directly: the pricing page and the billing part of the account page load its checkout script from cdn.paddle.com, so Paddle sees a request from your browser on those pages whether or not you buy anything or have an account.
  • Resend. Resend, Inc. sends the links that confirm an email address and our password reset emails from no-reply@chizuki.com. It handles your email address and the message on our instructions and for nothing else.
  • Hosting. [HOSTING PROVIDER] runs chizuki.com and the account database. [RELEASE FILE HOST] serves the installer files. Both act on our instructions.
  • Nobody else. We do not sell, rent, trade or share account data. There is no advertising partner, no data broker and no affiliate network. We disclose data only where the law requires it.
06

Where the data is held

[TO BE COMPLETED BY THE OWNER: the country or region the account database is hosted in, and the transfer mechanism relied on for Paddle and Resend where they process outside the EEA or the UK, which will normally be Standard Contractual Clauses or the UK Addendum.] This paragraph is a placeholder and must not be published as it stands.

07

How long we keep it

  • Sessions. A session expires 30 days after it was last renewed and cannot be renewed past 90 days from sign-in. The expired row itself stays until the account is closed so you can see your device history.
  • Sign-in attempts. A code expires 10 minutes after you ask for it. The record of the attempt, including the IP address and rough location, is deleted 24 hours after the attempt was made. The clean-up runs whenever the app asks for a sign-in code, and when an expired one is checked or approved, not on a timer, so a row can outlive its 24 hours on a quiet server. Approved and refused attempts go the same way. Nothing older survives, so this is not a history you can look back at.
  • Abuse counters. Deleted 24 hours after they start counting.
  • Password reset links. Expire 30 minutes after they are issued and are marked used the moment a reset goes through, so a link works once. Used and expired rows are deleted the next time a reset link is made for anyone, and in any case when the account is closed. That clean-up runs on request, not on a timer, so a row can outlive its 30 minutes on a quiet server.
  • Billing records. Kept as long as tax and accounting law requires. [RETENTION PERIOD TO BE SET BY THE OWNER, and note that Paddle keeps its own copy under its own schedule.]
  • Credit usage. Kept while the account exists, because rollover and monthly usage are worked out from it. When the account is closed, rows older than 31 days are deleted and the rest are kept for up to 31 days under a code made from your email address with a secret only our server holds, not under the address, so closing the account and opening it again does not start the month's credits over. An account opened again with the same address within those 31 days takes them back. The clean-up runs when an account is closed, not on a timer, so a row can outlive its 31 days on a quiet server.
  • Free credit claims. Kept while the account exists. When it is closed, the claim stays, without the account, until the end of that calendar month, so the mailbox cannot have the free credits twice in one month, and is deleted after that. The clean-up runs when an account is closed, not on a timer, so a row can outlive its month on a quiet server.
  • Everything on your computer. Your leads have no expiry: the businesses, the contacts, an extract of each business's website, the scores, the AI checks, your profiles, the do-not-contact list, the run history and the export files are kept until you delete them. Three kinds of working data are cleaned up by a pass the app runs once when it starts rather than on a clock, so a row can outlive its window on a computer left open for weeks. Records of the website pages it read, the evidence behind a score, are deleted 30 days after they were fetched; the pages themselves are not kept. The store of AI model results keeps its newest 50,000 entries and drops the rest. The captures saved when a run is blocked, a screenshot and the page, keep the newest 20 that are under 7 days old and nothing else. All of this runs on your computer. We are not told about any of it, cannot see it and cannot delete it for you.
08

Your rights and how to use them

  • Get a copy. Signed in, use the "download your data" button on your account page, or request GET /api/auth/export directly. You get one file with your user record, every session, the sign-in attempts still on record with their IP address and rough location, any plan grant from us, your subscriptions, your transactions, the Paddle customer records, every credit spend, your billing periods and your mailbox's free credit claim. There are two things the file cannot show you. Sign-in attempts are deleted after 24 hours, so that part of the file is the last day, not your full sign-in history; the device list built from your sign-ins goes back further. And two short-lived security records are left out: the abuse counters, which hold nothing about you beyond what they count against, and any unexpired password reset code, which is only a hash.
  • Delete the account. Signed in, use the "close account" button on your account page, or send POST /api/auth/delete-account with your password. It removes your user record and with it every session and sign-in attempt, along with the billing periods, plan grants, subscriptions, transactions and Paddle customer rows for your address. Credit spends from the last 31 days and your mailbox's free credit claim stay a while longer, without your address, as How long we keep it explains. It refuses while there is a subscription that is still set to renew and charge you again. Cancel that subscription and you can close the account straight away, with no need to wait out the period you already paid for. A plan that has already stopped because its payment failed and its 14-day grace ran out does not refuse the closure either. Closing asks Paddle to end at once every plan still open under your address, a stopped one included, so Paddle stops retrying its card and no later charge can land. If Paddle cannot be reached while a plan it could still charge is open, the account stays open and you can try again in a minute. Paddle keeps its own invoice records for its own legal reasons; ask Paddle about those.
  • Correct something. Write to [PRIVACY CONTACT ADDRESS]. There is no way to change your account email address yourself today, so it has to be done by hand, and it may not be possible without closing the account and starting again.
  • Object or restrict. Write to [PRIVACY CONTACT ADDRESS]. The only processing based on legitimate interest is the abuse counters, the sign-in attempt records, the free credit claims and the credit use kept for 31 days after an account is closed. The rest is needed to run the account you paid for and cannot be switched off on its own.
  • Complain. If you are in the EU or the UK, you can complain to your national supervisory authority. You do not have to contact us first.
  • Your local data. The leads database is yours outright. Deleting the ~/.chizuki folder removes it. Erasing one lead from its panel in the app deletes it from that database but puts its website and Maps listings on the do-not-contact list, so no later run collects it unless you allow it again from the app's "do not contact" tab. Export files you already saved still hold it, and the app's log keeps the lines that named it until newer lines push them out. No request to us is needed, because we never had it.
09

The people in the leads you collect

Chizuki collects business listings. In the EU and the UK, a named contact or a personal work email inside a listing is personal data. For that data you are the controller. We are not your processor (we do not handle it for you), because we never receive it: it is written to your computer by software running under your control. Your own notice, your legal basis and your reply to anyone who writes to you about their data are yours to handle.

What the app does and refuses to do on your computer is described on the What it refuses page and the Data processing page.

10

Changes to this notice

The date at the top is the date of the current draft. When this notice takes effect, and whenever it changes in a material way, we will note the date here and email your account address if the change affects what we collect or who receives it.