Where your briefs are stored, who sees them.
You give Gözetçi your briefs and your firm archive. They carry attorney-client privilege. This page states in plain language what we do and what we do not do, and says which claims are measured by a gate. The certifications we do not hold are listed below too, because a company that sells a product built on keeping secrets should not speak in polish about this.
Commitments
Your documents are not sold and do not train models
The briefs and firm documents you upload are not sold to third parties, are not used for advertising and are not used to train AI models.
Text stays in your browser by default
Brief pre-check, adding a document to the archive and the 11 deterministic rules of Document Analysis run entirely in your browser: the text never goes to the server. The 4 contextual checks in Document Analysis are the exception and depend on explicit consent. The consent box is off by default; if you do not tick it, the text does not leave your machine, those four checks do not run, and the screen says so.
Document content does not enter the job queue
The background job queue (Inngest) carries only event identifiers: the ruling id and the account id. Document content never passes through that line.
Card data never reaches us
Payment is taken through the merchant of record (Creem). On our side the card number is neither seen nor stored.
Encryption in transit, authorization on access
Data is encrypted with TLS in transit, access is limited by authorization. Encryption at rest is at the provider level (Neon, Vercel).
If there is a breach, you are told
No system can promise absolute security. If a data breach occurs, both you and the KVKK Board are notified within the period the legislation requires.
Where the data is stored
All of the infrastructure providers we use are outside Türkiye: Vercel, Clerk, Neon, Creem, Resend, Anthropic and Inngest. We do not write this in small print at the bottom of the page, because where a KVKK compliance tool itself runs is the first thing a buyer needs to know.
Transfer abroad is based on your explicit consent or on the other conditions set out in the Law, under KVKK Article 9, and is limited to the minimum the service needs in order to run. Which provider processes which data for which purpose is written item by item in the sub-processor list (Turkish); the legal basis is in the KVKK privacy notice (Turkish).
The path your document takes
- 01
Upload
The document arrives from your browser over TLS, the application runs on Vercel.
- 02
Storage
Document metadata and matching results are stored on Neon (PostgreSQL), tied to your account.
- 03
Matching
When the watch finds a new ruling, the citation references extracted from your document are compared with the ruling's reference. This comparison is deterministic and does not call a model. The model is involved only when asking whether a conflict between rulings really exists.
- 04
Notification
The result e-mail is sent through Resend. The content of the notification is in that e-mail, so the notification text is also carried by the e-mail provider.
- 05
Deletion
Your deletion request is handled as a KVKK data subject request and completed within 30 days at the latest. Automatic retention periods that do not depend on a request are written in a separate section below.
How we measure this claim
The sentence “text does not leave” is cheap as a promise. We test it with a canary gate: a unique text fragment made for the test is placed inside the product, then every network call and console output is captured, and where that text ends up is measured.
The gate runs on every build. For brief pre-check and adding a document to the archive, the measured result is this: zero outgoing requests. The file is read in your browser, and citation and date extraction happen there too.
The same gate also counts the places that send text to the model and freezes that list. If a model is called from a new place, the gate fails, so a hidden exit cannot be opened. This measurement also corrected our own document: we had written “there is a single seam”, the measurement showed four, and the sentence was changed.
We also state what we do not measure: the cache and temporary file surface is outside the scope of this gate. The Document Analysis screen is also out of scope, because there we already say openly that the text goes to the model.
Retention periods
Every data table has a retention rule: period, legal basis, deletion path and reason. The rule list lives in code, not in a document, and a gate compares it with the schema. If a new table is added without a rule, the gate fails.
- ·Brief and firm document text: 90 days. After that the text is deleted; the record itself and the extracted citations remain. The radar works from citations, it no longer needs the full text.
- ·Notification record: 1 year.
- ·Client and matter records: for as long as your account is open. Deleted when the account is closed.
- ·Payment record: cannot be deleted. It is tied to the commercial ledger obligation; even if the account is closed, the fields tied to a person are kept anonymized.
These periods are today at the declaration stage. The automatic job that performs deletion has not been written yet, and we write this rather than hide it. Today deletion is done by hand, on your request. When automatic deletion is in place, this paragraph will change.
What we do not have yet
- ·We do not hold an ISO 27001 or SOC 2 certificate.
- ·We do not have an independent penetration test report.
- ·There is no option to run on your own servers (on-premise).
- ·No data residency in Türkiye; all infrastructure providers are outside the country.
When one of these changes, this page is updated. Showing what does not exist as if it were on the roadmap and misleading the buyer is the most expensive mistake for a product that sells compliance.
If you find a vulnerability
Write directly to merhaba@gozetci.com or choose "Hata bildirimi" (bug report) as the topic in the contact form. We read it the same business day and write back within three business days on what we will do. We do not have a bounty program; we ask you not to disclose the vulnerability publicly until the fix is live.