Chatlytics Blogs
Version 1.0 · Last updated 22 October 2026 · Effective 22 October 2026
Operated by Chatlytics, the business of Omer Nesher, a licensed Israeli sole trader, business number 037289931, Israel ("Chatlytics", "we", "us", "our").
Contact: [email protected]
1. Scope
1.1 This policy explains how we collect, use, store, share and delete personal data when you use Chatlytics Blogs: the service that turns a WhatsApp group or channel into a public blog (the "Service").
1.2 It covers three groups of people: Customers (the group owners or administrators who open an account and connect a group), Group members (people who send messages in a connected group), and visitors to a Blog.
1.3 This policy does not cover what a Customer does with the Blog or with data they obtain through the Service. The Customer decides what to publish and is responsible for their own use of that content.
2. Who is responsible for your data
2.1 Chatlytics is the controller of account, billing, support and security data, and of technical data about visitors to our websites and Blogs.
2.2 For the Content captured from a connected group and published on a Blog, the Customer is the controller and Chatlytics is the processor. We process that content on the Customer's instructions: to capture, format, store and publish it as the Customer has configured.
2.3 If you are a Group member and want to know who decided to publish your messages, that is the Customer — the group's owner or administrator. If you contact us, we will help you reach them.
3. What we collect
3.1 Account data. Name, email address, telephone number if you provide one, business name and tax details where relevant, login credentials, Plan, and the settings you choose.
3.2 Billing data. Plan, Subscription Period, payment status and invoice references. Card and payment details are collected and processed by Polar.sh as Merchant of Record. We do not receive or store full card numbers.
3.3 Group connection data. The group's name and identifier, the date the connection was made, connection status, and the technical identifiers needed to maintain the connection. As part of the connection, the platform may expose the telephone numbers and push names of group participants. We use telephone numbers only to operate and secure the connection and to attribute messages internally. We do not publish them.
3.4 Content. Messages, captions, images, video, audio, documents, links, polls, reactions and timestamps sent in a connected group, together with the sender's push name. We capture only groups that a Customer has connected. We do not access groups that have not been connected.
3.5 Published content and visitor data. The Blog pages we generate, and technical data about visits: IP address, approximate location derived from it, browser and device type, referring page, and the pages viewed.
3.6 Communications. Emails and messages you send to support, and our replies.
3.7 Technical and security data. Log data, error reports, and records of administrative actions taken in your account.
3.8 We do not buy personal data from data brokers, and we do not use third-party advertising trackers on the Blogs.
4. Why we process data, and on what basis
4.1 To provide the Service — capturing messages, generating and publishing the Blog, applying your settings, and managing your account. Basis: performance of our contract with you.
4.2 To take payment and meet tax and accounting duties — billing, invoices, VAT records. Basis: performance of the contract and our legal obligations.
4.3 To keep the Service secure and reliable — detecting abuse, preventing fraud, debugging, and protecting the Blogs from attacks. Basis: our legitimate interests in running a safe service, and our legal obligations.
4.4 To provide support — responding to your requests and resolving problems. Basis: performance of the contract and our legitimate interests.
4.5 To improve the Service — understanding in aggregate how the Service is used. Basis: our legitimate interests, using aggregated or de-identified data wherever possible.
4.6 To comply with the law and respond to lawful requests — Basis: our legal obligations.
4.7 With consent — where we ask for consent for a specific use, for example before sending marketing email to someone who is not a Customer. You can withdraw consent at any time.
4.8 We do not sell personal data and we do not use Content to train third-party artificial intelligence models.
5. What is published, and what is not
5.1 Blogs are public by default. Anything published on a Blog can be read, copied and shared by anyone, and may be indexed by search engines and included in their caches.
5.2 Group members appear on a Blog under the public push name they use in the group. We do not publish telephone numbers, profile photos, or private account details.
5.3 The Customer chooses whether to publish, which group to connect, whether to pause publication, and whether to protect the Blog with a password. Password protection limits casual access but is not a substitute for not publishing something in the first place.
5.4 If a Blog is made private or deleted, we remove it from public view and ask search engines to refresh their index. Third parties may still hold copies they made while the Blog was public; we cannot reach those copies.
5.5 If you are a Group member and do not want your messages or push name published, contact the group's administrator first, and contact us at [email protected] if that does not resolve it. See section 12.
6. Cookies and similar technologies
6.1 At launch we use only the cookies and local storage needed to run the Service and the Blogs: keeping you signed in, remembering display preferences such as language and theme, balancing load, and protecting forms against abuse.
6.2 We do not use advertising cookies or third-party analytics trackers at launch. If we add analytics, we will update this policy and, where the law requires it, ask for consent before the tracker is set.
6.3 You can block or delete cookies in your browser. Blocking essential cookies may prevent parts of the Service from working.
7. Who we share data with
7.1 Polar.sh — as Merchant of Record, for payment processing, invoicing and tax. Polar receives the billing and contact details needed to complete the transaction.
7.2 Hosting and infrastructure providers — who host our servers, store backups and deliver the Blogs.
7.3 Email and support providers — who deliver transactional email and handle support correspondence.
7.4 The messaging platform connection — the Service depends on the connection you authorised to WhatsApp. Data exchanged through that connection is also subject to that platform's own terms and privacy policy.
7.5 Professional advisers — lawyers, accountants and auditors, where needed and under duties of confidentiality.
7.6 Authorities and courts — where we are required by law to disclose, or where disclosure is necessary to establish, exercise or defend a legal claim.
7.7 A successor entity — if the business is sold or merged, data may transfer to the successor, subject to this policy and to applicable law.
7.8 We require service providers who process personal data for us to protect it and to use it only for the purposes we specify. A current list of processors is available on request at [email protected].
7.9 We do not sell personal data.
8. Where data is stored and transferred
8.1 Our servers and those of our providers may be located outside Israel. Where personal data is transferred outside Israel, we take steps required by applicable law to keep it protected.
8.2 If you are in the European Economic Area or the United Kingdom, we rely on the transfer mechanisms those frameworks require, including standard contractual clauses where applicable. Contact us for details.
9. How long we keep data
9.1 Active accounts — for as long as the account exists and the Subscription is active.
9.2 After cancellation — updates stop and the Blog is unpublished. Data is kept for 60 days, during which the Customer can request an export, and is then deleted from production systems.
9.3 Backups — residual copies may remain in encrypted backups until those backups are overwritten in the ordinary course. Access to backups is restricted and they are used only for recovery.
9.4 Billing and tax records — kept for the period required by Israeli tax and accounting law, even after the account is closed.
9.5 Support correspondence — kept for as long as needed to resolve the issue and to maintain a record of our dealings, then deleted or archived.
9.6 Logs — kept for a limited period for security and troubleshooting, then deleted or aggregated.
10. Security
10.1 We use technical and organisational measures designed to protect personal data, including access controls, least-privilege administration, encryption in transit, logging of administrative actions, and regular review of our providers.
10.2 No system is completely secure. If a security incident affects your personal data, we will investigate, mitigate, and notify you and the relevant authority where the law requires it.
10.3 You are responsible for keeping your account credentials secure and for telling us promptly about suspected unauthorised access.
11. Your rights
11.1 Subject to applicable law, you may ask to:
(a) see the personal data we hold about you;
(b) correct data that is inaccurate, incomplete or out of date;
(c) delete data we no longer have a lawful reason to keep;
(d) restrict or object to processing based on our legitimate interests;
(e) receive a copy of data you provided to us, in a structured format, where the law gives you that right;
(f) withdraw consent you previously gave, without affecting processing carried out before withdrawal.
11.2 To exercise a right, write to [email protected] from the email address associated with your account, or include enough information for us to identify you. We may ask for verification to protect against unauthorised access.
11.3 We respond within the period the law allows. Requests are normally free of charge; where a request is manifestly unfounded or excessive, we may charge a reasonable fee or refuse it, and we will explain why.
11.4 If you are in the EEA or the UK, you also have the rights those frameworks grant, including the right to lodge a complaint with your local supervisory authority.
12. Group members
12.1 If your messages appear on a Blog and you did not expect that, the first step is to contact the group's administrator, who controls the Blog.
12.2 You can also contact us at [email protected]. We will identify the Customer responsible, pass your request on, and, where the request concerns content that is unlawful or clearly outside what the Customer is entitled to publish, act on it ourselves.
12.3 We may remove or unpublish content while a request is being examined, where the circumstances justify it.
12.4 We keep a record of requests and our response so that we can show how we handled them.
13. Children
13.1 The Service is intended for adults. Accounts may not be opened by anyone under 18.
13.2 Groups may include minors, and their messages may be captured if a Customer connects such a group. The Customer is responsible for ensuring there is a lawful basis for publishing that content and for protecting the interests of minors. We will act on requests to remove content that identifies or endangers a child.
14. Automated processing
14.1 We use automated processes to format messages, generate titles and summaries, categorise posts and detect abuse. These processes support the Service; they do not produce legal effects or similarly significant decisions about individuals.
14.2 We do not make automated decisions about your creditworthiness, eligibility or legal status.
15. Changes to this policy
15.1 We may update this policy to reflect changes in the Service, in the law, or in our practices. The current version, with its version number and date, is always published with the Service.
15.2 If a change materially affects how we use personal data, we will give reasonable notice before it takes effect. Where the law requires consent, we will ask for it.
16. Contact and complaints
16.1 Questions, requests and complaints: [email protected].
16.2 Chatlytics — Omer Nesher, licensed Israeli sole trader, business number 037289931, Israel.
16.3 If you are not satisfied with our response, you may complain to the Israeli Privacy Protection Authority. If you are in the EEA or the UK, you may complain to your local supervisory authority.