DATA PROCESSING

Almost nothing for a data processing agreement to cover.

For teams buying Chizuki: who controls your account data, who controls your leads, and the few limits worth writing into your own records.

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 app's code. Effective date: [TO BE SET BY THE OWNER]

01

Why this page exists

If you buy Chizuki for a team, your compliance paperwork will ask who processes what on whose behalf, and whether you need a written data processing agreement with us (GDPR Article 28). For most of what Chizuki touches, no such agreement is possible: the data never reaches us. This page says where that is true and where it is not.

This is a summary of how the app is built, not a signed agreement. If you need a signed Article 28 agreement or a security questionnaire completed, write to [PRIVACY CONTACT ADDRESS].

02

Three data sets, three answers

  • Your account data. Your email address, a one-way scrambled form of your password, sign-in sessions, sign-in attempts with their IP address and approximate location, and billing history. We are the controller. We process this to run your account, not on your instructions, so Article 28 does not apply. The privacy notice covers it in full.
  • Your lead data. Every business you collect, its contacts, the record of the pages read, the scores, the AI check results and every export file. You are the controller. We are not a processor, because we never receive any of it: the app keeps it on your computer, in a database under ~/.chizuki and in the export files you save, and there is no upload, no sync and no backup to us. There is nothing for a data processing agreement with us to cover.
  • Credit usage keys. One hash (a one-way scrambled code) per lead you export, with the time the credit was spent, the time we recorded it, and a refund time if there was one. We hold these because credits have to be counted somewhere other than the machine spending them. The code is made with a key generated on your machine, which never leaves it and is never sent to us. So we cannot turn it back into the business it came from, cannot check a guess against it, and hold nothing else about the lead. What it does give us is a record of how many leads an account exported and when, plus a code that repeats if the same lead is exported again from the same machine. We use it for billing and nothing else. [TO BE CONFIRMED BY COUNSEL: whether a stable identifier held against a named account, which we cannot reverse because the key exists only on the customer's machine and is never transmitted to us, is personal data in our hands, and if so whether we are controller or processor for it. We currently treat ourselves as controller for the narrow purpose of counting credits.]
03

What the app does on your computer

Since we do not process your lead data, the controls that matter to your records are the ones running on your computer. The How it works and What it refuses pages describe them in full; the short list is here so you can cite it.

  • Collection. A browser the app controls visits Google Maps and the business websites behind it, from your computer and your IP address. The browser is not inside the installer: the first run downloads it, or uses Google Chrome if that is already on the computer. Google Maps itself is read without consulting a robots file (the file a website uses to say which pages automated visitors may read). When the app then goes to a business website it reads that site's robots file first and does not fetch a page the site disallows, and marks the site "unverifiable_blocked" instead. There is a pause after every listing, a random 2 to 5 seconds around the default 3-second delay, a daily cap on detail views (300 by default), and a block signal stops the run.
  • Storage. The leads, their scores and AI check results, the record of the pages read, the run and export history and the do-not-contact list are kept in one database per account under ~/.chizuki, on the computer that collected them. Profiles are files in ~/.chizuki/profiles, shared by every account on that computer, and export files go to the export folder the app shows. For each page it reads, the app keeps the address, the status and the date as evidence for a score, not the page itself. A lead also keeps an extract of its website, which the AI check reads. Each time it starts, the app trims three kinds of derived data: page records go 30 days after the pages were read, the model result cache keeps its newest 50,000 entries, and the screenshots and page copies saved when a run is blocked keep the newest 20 that are under 7 days old. The leads, the profiles, the do-not-contact list and the export history are not swept and stay until you delete them.
  • Enrichment. If you connect a model provider and ask for an AI check on a lead, that 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, are sent from your computer to that provider, using the key you got from that provider and your own agreement with it. That provider is your sub-processor, not ours. Nothing about a business is sent until you ask for a check, and scoring never calls a model: it runs on this computer and can only read what an earlier check returned. Setup also asks the provider you pick for its list of models, and the test button there sends it a short test message, at most twice; neither carries lead data. Making a profile with AI sends it only what you wrote about your offer and the app's own lists, and no lead data.
  • Suppression. A do-not-contact list of business websites and Google Maps listings, each with a reason and a date, kept in the same local database. A run checks it when it reads a listing and again when it scores a lead, and every export checks it before the file is written. The list is shown in the app, on the "do not contact" tab of the leads screen, with how and when each entry was added. It can be searched, and a business marked by mistake can be allowed again. Allowing an erased business again restores nothing that was erased; it only lets a later run collect the business afresh.
  • Erasure. Deleting the ~/.chizuki folder removes the leads, the do-not-contact list, the profiles, the page records, the run history, the captures saved when a run is blocked and the log. Deleting only an account folder under ~/.chizuki/accounts removes that account's leads, do-not-contact list, page records and run history, but not the profiles, the log or the captures, which every account on the computer shares. Erasing one lead from its panel in the app deletes it with its page records, reviews, scores, site and AI checks and every Maps listing stored with its website, and puts its website and those listings on the do-not-contact list so no later run collects it unless you allow it again from that list. Nothing outside the database changes: export files you already saved are ordinary files in the folder you chose and still hold it, and the log keeps the lines that named it until newer lines push them out.
04

Sub-processors for the account data

  • Paddle. Paddle.com Market Ltd is the merchant of record and an independent controller for the payment details you enter with it. Card numbers never reach us. Its checkout script is also loaded by the pricing page and the billing part of the account page, so your browser contacts cdn.paddle.com there even if you buy nothing and have no account.
  • Resend. Resend, Inc. sends the links that confirm an email address and our password-reset emails, and nothing else.
  • Hosting. [HOSTING PROVIDER] for chizuki.com and the account database, [RELEASE FILE HOST] for the installer files.
  • Changes. Additions to this list will be posted here. [NOTICE PERIOD AND OBJECTION PROCESS TO BE SET BY THE OWNER.]
05

Security measures on the account data

  • Passwords. Stored only in a one-way scrambled form, never as typed. Each one is scrambled with its own random addition, so two identical passwords are stored differently.
  • Sign-in keys and codes. Session keys, sign-in codes, their approval secrets and password reset links are stored only as HMAC-SHA256 hashes keyed with a server secret: a one-way scrambled form that also needs a secret kept outside the database. A stolen copy of the database holds nothing that can sign in. Checks give away no timing clues.
  • Transport and cookies. Everything travels encrypted. We set two cookies, both only after you sign in: the sign-in cookie, and chz_known, which marks a browser that has signed in to the account so wrong passwords tried elsewhere cannot lock it out; it holds a random code and a signature and lasts a year. Both are sent only over encrypted connections, page scripts cannot read them, and another website cannot submit forms as you with them. They are not the only thing that can end up in your browser: the pricing page and the billing part of the account page load Paddle's checkout script from cdn.paddle.com, and whatever that script stores is Paddle's, under Paddle's own notice. There is no analytics or advertising script anywhere on the site.
  • Abuse limits. Sign-in, sign-up, password reset, account export, account deletion and sign-in codes each allow only so many tries in a period, counted per IP address, per email, per account, per browser that has signed in before and per code.
  • Sign-in approval. A sign-in from the app has to be approved in your browser. The approval page shows the device name, its operating system and where the request came from. The code expires in 10 minutes, and only a browser sign-in made after the app asked can approve it.
  • To be completed. [ACCESS CONTROL, BACKUP, ENCRYPTION AT REST AND PERSONNEL MEASURES TO BE DESCRIBED BY THE OWNER: these depend on the hosting arrangement, not on the code, and cannot be written from the source tree.]
06

Breach notification

If account data is exposed we will email the address on the account without undue delay and say what was affected. [NOTIFICATION WINDOW, ESCALATION CONTACT AND SUPERVISORY AUTHORITY REPORTING PROCESS TO BE SET BY THE OWNER.] We cannot detect or notify you about a breach of your lead data, because it is on your computer and not ours.

07

Limits to record in your own assessment

These are facts about the product today, not policy. They matter to a team writing its own records of processing.

  • Suppression is per machine. The do-not-contact list does not sync. An opt-out recorded on one person's laptop is invisible on another's, so keep the master list in your sending tool.
  • Credit keys are per machine. The key used to make an exported lead's code is generated on the machine that exported it and does not sync, so the same lead exported from a second machine hashes differently and spends a second credit. Deleting the app's local data deletes the key too, and leads exported after that count as new.
  • There are no seats. An account is one email address and one password, shared across computers. There is no per-person sign-in, no invites and no record of which person spent a credit or made an export, so our records cannot show who exported what.
  • The account email cannot be changed. Billing, credits and the local database folder are all tied to the address you signed up with. Plan ahead for when someone leaves.
  • Sign-in attempt records are short lived. The IP address and approximate location of each sign-in attempt are deleted 24 hours after the attempt, by a sweep that runs on the next sign-in rather than on a clock. If your security process expects to review where sign-ins came from later, that record will be gone: the account export includes only what is still inside the 24 hours, and the session list is what goes back further.