In short
- We keep what the work needs: your account, conversations, files and the connections you gave.
- A conversation goes to the model provider that runs the Kringl, mostly Anthropic. We do not train models on your content.
- We do not sell personal information. It goes only to the providers listed here, to run the service.
- The site kringl.ai measures visits and enquiries with Wizzo's own tools. The landing page of our Facebook and Instagram campaign, and the app's signup and sign-in screen at web.kringl.ai, also measure with the Meta pixel. The full list is in the section on cookies.
- To see, correct, copy or delete your data, write to info@wizzo.co.il and we answer within 30 days.
The summary helps you find your way. The full document below is the binding text.
Who is responsible
Wizzo Software Ltd., which runs Kringl, is responsible for the data collected in the service. Address: 3 Totzeret HaAretz St., Petah Tikva, Israel. Any privacy question: info@wizzo.co.il.
This policy covers the site kringl.ai, the app at web.kringl.ai, the Android and iPhone apps and the desktop program. The browser extension has its own privacy page.
What we collect
| Kind | What exactly | From where |
|---|---|---|
| Account | Name, email, phone, and a password kept only as a hash | From you, at sign-up |
| Workspace and payment | Business name, people and number of seats, a card charging token, last 4 digits, expiry and brand, charge log and invoice details | From you and the payment processor |
| Conversations | Messages, voice notes, files and images you upload, and what the Kringls wrote and captured | From you and the Kringls |
| Work | A copy of the repositories you connected, the Kringls' work logs, and the records of changes made to databases | From the connections you gave |
| Connections and secrets | Tokens for GitHub, Google and the stores, and passwords and keys you saved in the vault | From you |
| Desktop program | Content from the folders you shared, only while a Kringl works on them and only what it needs | From your computer, with your approval |
| Technical | IP address, device and browser type, server logs, a push token for your phone, and crash reports from the app | Automatically |
| Enquiry from the site | Name, phone, email and what you wrote, where you came from (including a campaign ID, if any), and the consent you gave | From you, in the form |
| Newsletter | Your email address, your name if you gave it, when and where you signed up and confirmed, and which issues were opened and what was clicked | From you, in the signup form, and from the email itself |
Your phone number is not verified, and is used to contact you.
Required or optional. You are under no legal duty to give us personal data, and giving it is up to you. A name, an email address, a phone number and a password are needed to open an account and enter into the agreement with us, and without them you cannot sign up. Without a payment method, access stops at the end of the 14 day trial. Connections (a repository, a server, a store, a mailbox) are optional, and without them the Kringls do not work in that place. An enquiry on the site is optional too.
Why we use it
| Purpose | Basis |
|---|---|
| Providing the service: running the Kringls on your conversation, code and connections | Our contract with you |
| Billing, invoices and records under tax law | Our contract with you, and a legal duty |
| Security, preventing abuse and fixing faults | Our legitimate interest |
| Improving the service from usage and fault data | Our legitimate interest |
| Getting back to you after an enquiry from the site | Your consent |
| Sending the newsletter "השבוע למי שבונה" to people who signed up and confirmed by email | Your consent, which you can withdraw in every issue |
| Measuring visits to kringl.ai | Our legitimate interest, and consent where the law requires it |
AI and your data
When a Kringl works, what it needs for the work (the message, pieces of code, files) is sent to the model provider that runs it. That is part of the work, not another use.
We do not train models on your content. What a model provider may do with the data is set by its own terms. When a workspace connects its own model account (for example a Claude subscription), that account's terms and settings also decide whether data is used for training. Check them in the account itself.
The Kringls learn from the work: a lesson found in a project is saved in your workspace's lessons store, so the same mistake is not repeated. The store belongs to the workspace and is not shared with other workspaces, and the workspace admin can switch it off in settings.
Your users' data
When the Kringls work on your product, they may see data of its users, for example in the database or in server logs. You are responsible for that data, and we process it for you, only for the work you asked for.
The Kringls do not send messages, emails or notifications to your users, or delete their data, unless you asked.
If a referrer sent you
Kringl takes part in Wizzo's referral program (go.wizzo.market): businesses and people who recommend Kringl and earn a commission on those who sign up through them. This section applies only if you came through a referrer's link, or bought a bundle on a referrer's page.
- What is kept when you arrive. The click id from the link, a random number that does not identify you on its own, is kept in a cookie named wzr for 30 days, and in the app's local storage for the same time. When you sign up, it is saved with your account and with the workspace you open.
- What goes to the referral program. The workspace name, the name and email of the person who opened it, when it was opened, and the click id. When you pay for seats, the number of seats and the amount and date of each charge, and any refund, go too, to calculate the commission. When Wizzo's team credits a signup to a referrer by hand, for example when the link was not picked up, it finds the account by email, name or mobile number, and the mobile number is then kept in the referral program as well.
- If you bought a bundle on go.wizzo.market. Your Kringl account is opened with the name, email and mobile number you gave there, and Kringl reports to the referral program how many seats are in use and how many were active in the last 14 days, to run the bundle and charge for it.
- What never goes. Card details, and anything inside your account: conversations, code, files and projects.
- What the referrer sees. Your name and the workspace name, your email partly hidden, the bundle, the status (trial, paying, ended) and dates. Not your phone number, payment details or what you do in Kringl. The agreement lets the referrer use this only to support you and settle accounts with Wizzo, and requires them to delete it within 30 days after the referral or the agreement with them ends, whichever comes first.
- A form on this site after a referrer's link. If you came through a referrer's link and left your details in a form on this site, the Kringl team gets back to you and the request is credited to the referrer. The referrer sees only that a request came and when, for 30 days, without your name or any way to contact you.
- Why. To credit the signup to the right referrer, calculate and pay the commission, and prevent fraud, such as a referrer referring themselves.
- Who is responsible, and how to see or correct your data. The referral program's database is owned by Wizzo Software Ltd. You can ask to see the information kept about you in the program, and to correct it, at info@wizzo.co.il.
- How long, and how to ask for deletion. All in chapter 14 of the WizzoMarket privacy policy.
Google connection: Gmail, Calendar and Drive (Google user data)
Anyone who chooses to can connect their Google account to Kringl from their personal area, and through it, each with its own consent, their Gmail inbox, their Google Calendar and their Google Drive. The connection goes through Google's consent screen, is personal to each user, and can be disconnected in the same place at any moment. Kringl does not touch a mailbox, a calendar or a Drive the user did not connect themselves.
- Gmail. With the read scope (gmail.readonly): messages, threads and labels in the user's inbox, according to what they ask in the conversation. With the compose scope (gmail.compose): creating drafts, and sending a draft only when the user taps Send on the card that shows it in the conversation. Kringl never sends an email by itself, does not delete messages, does not change labels and does not change account settings.
- Calendar. With the events scope (calendar.events), on the user's primary calendar only: reading events to answer about their schedule and to show their day in the personal area, adding an event they asked for, and moving or changing it. An event Kringl added is marked as its own and can be removed at the user's request; any other event is deleted only after the user confirms with a tap on a card in the conversation. Kringl does not read or change other calendars, sharing settings or calendar settings.
- Drive. With the read scope (drive.readonly): searching the user's files and opening a file they named in the conversation. A file opened this way is copied into that conversation's files, so the Kringl can read it. With the file scope (drive.file): saving into the user's Drive a file Kringl made in the conversation, into the root or into a folder Kringl created. Kringl does not change, move, share or delete the user's own files.
- Why. Only to do what the user asked in the conversation about their own mailbox, calendar or Drive: answer about it, prepare a draft and send it on their tap, book or move an event, read a document or save a file they asked for. Not for advertising, not for marketing profiles, not for sale and not for training models.
- With whom. The content relevant to the request (a message, an event or a file) is sent to the model provider running the conversation, only to produce the answer. By default that is Anthropic (Claude). When the workspace chose another engine, the provider is OpenAI (Codex), xAI (Grok) or Cursor, together with the model providers Cursor works through (for example Fireworks). When the workspace connected its own account or subscription with such a provider, the content goes through that account and under its terms. The access itself runs against Google's servers (Gmail, Calendar and Drive) with the user's token. The data goes to no one else.
- Who reads it. No person at Wizzo reads the content of the user's email, events or files, except when: the user explicitly asked us to look at specific messages; it is needed for security, for example to investigate a bug or abuse; the law requires it; or the data is aggregated and anonymised, so no person can be identified from it, for internal operations.
- How it is protected. Access tokens are stored encrypted in the database, separately for each user, and are used only for actions the user asked for. All traffic is encrypted with HTTPS.
- For how long. Inbox and calendar content is not stored as a collection: it is read to produce the answer, and only the answer stays in the conversation history. A Drive file the user asked to open stays in that conversation's files, like any file uploaded to it (see How long we keep it). Disconnecting the Google account in the personal area revokes the token at Google and deletes it on our side at once, and access can also be removed at any moment from the permissions page of the Google Account. To delete a conversation or the whole account, write to info@wizzo.co.il.
Limited Use statement, our own and in Google's wording:
Kringl's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Raw or derived user data received from Workspace APIs is not used to develop, improve or train generalized AI or ML models.
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
Cookies and measurement
The site and the app keep what is in the table in your browser. The site's measuring tools are Wizzo's own, not Google Analytics. The one exception is the landing pages of our Facebook and Instagram campaigns (/he/atar, /he/at and /he/build), and the app's signup and sign-in screen at web.kringl.ai: only there the Meta pixel runs, to measure the ads and show them to people who may be interested. On the landing pages it tells Meta that the page was opened, that a form was sent and that the signup button was pressed. On the signup screen it tells Meta that the screen was opened and that a new account was created, and with a new account it also sends the account's internal number, so the same signup is not counted twice. There it runs only in a browser and only before you sign in: not after you sign in, and not in the Android and iPhone apps, so Meta sees no conversations, projects or anything else inside the account. Meta receives the page address, the IP address, browser details and its own cookies, not the name, phone, email address, password or link you typed in the form. What Meta does with it is in Meta's own privacy policy.
| Name | Where | What for | How long |
|---|---|---|---|
| portal_token and the workspace cookie | web.kringl.ai | Keeping you signed in and remembering your workspace | 1 year |
| wizzo_a11y_v1 | kringl.ai | Remembering the settings you chose in the accessibility menu | Until deleted |
| _tuid | kringl.ai (Target) | Recognising a returning browser, and knowing where visits and enquiries came from | 1 year |
| The WizzoRadar ID | kringl.ai | Visit statistics: pages, referrer, page speed and click positions for a heatmap | 2 years, plus a visit ID until the browser closes |
| Pilot | kringl.ai | The chat window on the site | Until deleted |
| poosh_reg | kringl.ai | Signing up for browser notifications, only if you allowed them | Up to 30 days, renewed |
| _fbp, _fbc (the Meta pixel) | kringl.ai/he/atar, kringl.ai/he/at, kringl.ai/he/build and the signup and sign-in screen of web.kringl.ai only | Measuring how many people came from the ads, how many left their details or went on to sign up, and how many opened an account | 90 days |
| kr_attr | kringl.ai and web.kringl.ai | Remembering which ad or campaign brought you, to know whether it led to a signup or an enquiry. Only when you came from a campaign link | 30 days |
| kr_ref | kringl.ai and web.kringl.ai | When you came with no campaign: remembering which site sent you (its name only, for example google.com) and to which page, to know how you found us when you sign up or get in touch | 30 days |
| wzr | kringl.ai and web.kringl.ai | Only when you came from a referrer's link: the click id from the link, so the signup is credited to the referrer. In the app it is kept in local storage | 30 days |
| kr_attr and the Google Play install source | The Android app | The app asks Google Play once which link it was installed from, and keeps it only when that link belonged to an ad or a campaign, to know whether it led to a signup. If you sign up in the app, it is kept with the account | 30 days from install |
You can block or delete cookies and local storage in your browser settings. The site works without the measuring tools; in the app you cannot stay signed in without them.
How long we keep it
| What | How long |
|---|---|
| Account, conversations, files and the Kringls' memory | While the account is active, and up to 30 days after a deletion request |
| The Kringls' full work logs | 180 days |
| Server logs | 14 days |
| Backups | Rotating backups, the oldest at most six months old |
| A voice recording in a conversation | Turned into text; the recording is not kept. A voice note in the team box is kept like a file |
| Billing records and invoices | 7 years, as tax law requires |
| A managed server that was shut down | A last backup for 30 days |
| An enquiry from the site | Until you ask us to remove it |
| Newsletter | Until you unsubscribe. After that only the address stays on the suppression list, so you are not mailed again |
A deletion request removes the data from the service. Whatever is already in a backup is removed when that backup rotates out.
Security
All traffic is encrypted with HTTPS. Passwords are kept only as a hash. Connection tokens, and passwords and keys in a project's vault, are stored encrypted. Wizzo staff may access data only to run, support and secure the service. The content of a connected Gmail inbox, calendar or Drive is not read by a person, except as described in the Google connection section.
Please note: a file or image uploaded to a conversation is stored at a long address that is hard to guess, with no password. Anyone who gets the link can open it, so do not pass on a link to a sensitive file.
No method guarantees full security. If a security incident affects your data, we will tell you and the authorities as the law requires.
Your rights
You may see the data kept about you, correct it, ask us to delete it and get a copy of it. You may also ask us to stop marketing to you, and withdraw a consent you gave.
If you live in the European Union you may also restrict processing, object to processing based on legitimate interest, and receive your data in a portable format.
Write to info@wizzo.co.il and we answer within 30 days. Deleting an account or a conversation is done by such a request for now, not by a button in the app.
You may also complain to the Privacy Protection Authority in Israel, or to the data protection authority of your country in the European Union.
Children
Kringl is a work tool for businesses and is not meant for anyone under 18. We do not knowingly collect data about children, and such data that reaches us is deleted.
Changes to this policy
When this policy changes, the date at the top changes. We announce a material change by email or in the app before it applies.
A question about this document? Write to info@wizzo.co.il and a person answers.