Privacy

Last updated: 3 November 2026.

In short

• We process your documents only to make your video and to check every sentence against its source. We do not train models with your documents.
• You delete a job, or your whole account, yourself from the panel; you do not need to write to us.
• zipirapp.com sets no cookies. The panel (app.zipirapp.com) uses only the cookies needed for the session.
• We do not write a raw IP address to our database. For counting and preventing abuse we keep salted, irreversible digests.

What data we process

Site visit (zipirapp.com). Cookieless page counting: the page visited, only the domain of the referring site, the language and country derived from the browser language, the device type (desktop, mobile, tablet) and a one-way visitor digest made from the IP address and browser information with a key that changes every day. The raw IP address and the browser information are not written. If “Do Not Track” or “Global Privacy Control” is on in your browser, you are not counted at all.

Application form. Your work e-mail, your role, the type of your first document, the time you confirmed the information notice and the version of the text, a salted digest of your IP address and the browser information (user agent, first 200 characters). The digest and the browser information are there to tell repeated and abusive applications apart.

Panel account (app.zipirapp.com). Your name and e-mail address. If you sign in with Google or GitHub, the account ID the provider gives, the profile image address and the session tokens (only to link your account). The session record keeps browser information; the IP address is not kept. For accounts that come by invitation in the first period, the invited e-mail address and who gave the invitation.

Your documents and what we produce. The file you upload, the text lines read from it, the scene plan, the narration audio, the video, the cover frame, the proof report (PDF), frame-edit requests and the comments you write. Reading scanned pages (OCR) is done on our own server. If your document contains other people's personal data we process that too; for that data you or your organisation is the data controller; Zıpır works only on your instruction, as the processor, to make your video, and does not use this data for any other purpose.

Technical identifier in videos. The metadata (MP4 tag) of every video file we produce carries a technical identifier showing that the video was produced by Zıpır; it is derived from the job number. If you download the video and share it, this identifier goes with the file. The identifier does not point to you by itself; only we, by matching it against our own records, can find in which account the video was produced. The purpose is to investigate unauthorised copying and abuse. The tag is not embedded in the picture or the sound; you can remove it from the file if you like, and removing it does not affect the service.

Usage records. Which model and voice service was used how much in which job (tokens, characters, seconds) and its cost; video production minutes. These records carry no content.

Share links. If you share a video, no record is kept of the person who opens the link; only a salted digest of the IP address sits in a short-lived counter that limits abuse.

Test and attendance certificate (optional). If the video's owner turns the test on on the share page (it is off by default), the person who takes the test writes a first and last name. Then the following is kept: the name written, the number of correct answers, pass or fail, the time and, for those who pass, a verification code. The video's owner sees this data in the panel and can download it as CSV; it is given to nobody else and is not used for advertising or analytics. When the share link is closed or expires, these records and the attendance certificate files are deleted (immediately on closing, within one hour at the latest on expiry); the verification code is not verified after that moment. The attendance certificate is a Zıpır attendance certificate; it does not replace a legal training document or certificate provided for in legislation such as occupational health and safety. The test pages set no cookies.

Server and error logs. The servers record events line by line; error reports, when enabled, go to a separate error monitoring service. Before writing to either we strip out e-mail addresses, tokens, IP addresses, link queries and document content; job and user IDs (random numbers) remain.

Payment. When buying is open, the card payment is taken by the authorised payment institution. Your card number never reaches us. All we keep is the amount, date, payment status and the record numbers the payment institution gives. For the invoice, your name or company name, address and, if you wish, tax ID number are requested on the payment institution's payment page; we use this information to issue the invoice.

What we use it for

• To make your video, verify it against the source, narrate it, and prepare the video and the proof report.
• To let you into the panel and to send your sign-in link by e-mail.
• To stop abuse, excessive load and requests that exceed the spending cap.
• To find and fix errors and to monitor that the service is up.

We show no advertising, sell no data and build no personal profiles.

Who we work with

Your data goes only to the services below, and only for them to do that job.

• Cloud hosting provider (Europe): application servers, database, job queue and server logs. Database and file storage service (Europe): videos, audio clips and uploaded documents.
• AI model providers (USA): text passages chosen from the document; the providers' terms forbid training models on customer data. Requests go directly to the provider's API. Under the provider's commercial terms of service no model training is done on customer content; inputs and outputs are, unless otherwise agreed, automatically deleted from their systems within 30 days at the latest. The providers are bound, as processors, by a data processing addendum (DPA).
• Narration voice provider (USA): scene sentences only; no document file, user ID or e-mail address goes. There is a single voice provider; it receives the text only during narration.
• Transactional e-mail provider (EU): the recipient address and the e-mail text for sign-in links, account confirmations and administrator alerts. Sending is done from the EU region.
• Payment institution (USA; only when buying is open): name or company name, e-mail address, billing address, tax ID number if any, and card details. Only the payment institution sees the card details.
• Error monitoring service (USA; when enabled): error reports with e-mail, tokens, IP and document content stripped out. Stripped error reports as described above.
• Google and GitHub (only if you choose to sign in with them): name, e-mail address and profile image. These services are subject to their own privacy terms.

The hosting, file storage and analytics providers are in Europe; the model, voice, payment and error monitoring providers are in the USA; the e-mail provider is in EU countries. The data stays in data centres in the EU but most of the companies are abroad. The transfer is made to perform the service and is limited to the data needed; which data goes to which provider is written in the list above. Your rights and how to apply: KVKK information notice.

Retention and deletion

Deleting a job. You delete it from the job's page in the panel. Running steps are stopped; the source file, the lines read, the scene plan, the audio, the video, the cover, the proof reports, the edit frames and the share links are deleted. What remains: that job's content-free usage and cost rows, the video production minutes record and the “project deleted” audit row (IDs and the number of files deleted).

Deleting your account. You delete it from the Account page in the panel by typing the confirmation sentence. All your jobs are deleted as above, your file folder is scanned; the application form record you gave with the same e-mail, your user record, your sessions and your Google or GitHub link are deleted, and the session cookies in your browser are cleared. What remains: usage, cost and minutes records and, if any, payment records (by user number, without the e-mail), the audit rows and (if any) the first-period invitation record. Their retention periods are in the list below.

Model response cache. So as not to pay for the same request twice, model responses are kept on the worker's temporary disk, in files named after a digest of the content. This disk is not persistent and is reset with every new version; deleting a job does not delete these files at that moment.

Periods that end by themselves. The sign-in link is valid for 15 minutes, the session for 30 days (extended as you use it), file download links for 1 hour, frame-edit previews for 60 minutes.

Retention periods. We keep the following for the following periods:

• Source document and what is made from it (video text, audio, video, proof report): Until you delete it.
• Application records: 12 months.
• Session records: 30 days.
• Usage and cost records and audit records: 24 months.
• Page-count rows (only the daily totals remain): 90 days.
• Test results and attendance certificates (only if the video owner turned the test on): As long as the video's share link is open; deleted immediately when the link is closed, and within one hour at the latest when it expires.
• Payment records (amount, date, status; we do not hold card details): For the retention period in tax and commercial law.

Backups are taken daily and kept for 7 days; a copy of a record you deleted also drops out of the backups at the end of that period.

Security

• Every connection is encrypted with TLS. The file store is closed to everyone; files are opened only through short-lived signed links.
• The session cookie is HttpOnly, Secure and SameSite=Lax. The origin of every change request coming from the panel is checked.
• Everyone sees only their own jobs. The administrator screens show the e-mail address, job status and cost; they do not show document and video content.
• Sharing starts closed; you open it. Everyone who opens the link sees the verbatim quotes from the document; you close the link whenever you like.

Your rights

Your rights under KVKK art. 11 and how to apply are in the information notice. Short way: [email protected]. You see and delete most of your data yourself in the panel.