Privacy policy

What happens to the details you leave on this website, and to the data Lidin receives from Meta and Google.

Version 4 · revised 24.09.2026 · effective from 24.09.2026

1. What this document covers

This document explains two things:

• what we do with the details you leave on lidin.co.il, the website of the Lidin product (sections 3–11);
• what data the Lidin system receives from Meta and Google when an office that is our client connects its advertising to Lidin, or when someone at the office signs in with a Google account (section 12).

All other data inside the Lidin system belongs to the office. There the office itself owns the data, and the office's own privacy policy applies; the office provides the link to it.

2. Who is responsible for the data

The details left on this website are held by Israsky, which builds and runs the Lidin product: Ilia Shuliak, עוסק מורשה (licensed dealer) 324648047, 48 Binyamin Mintz St., Petah Tikva, Israel.

Email: support@lidin.co.il · Phone: 050-577-0731

For the data described in section 12, Israsky acts on behalf of the office (section 12.2).

3. What details are collected on the website

There is one form on this site: a request for a demo. In it you provide:

• full name
• phone number
• email address
• office name

There are no other fields on the site, and we do not collect details about you on this site in any other way. Filling in the form is your choice, not a legal obligation; without these details we simply cannot get back to you.

4. What we use the form details for

To get back to you about your request, arrange the demo and see the enquiry through.

That is the only use of the form details: we do not build profiles, we do not score you, and we do not use the details for anything else.

5. Who the form details are shared with

No one. The details are held by Israsky and are available only to the people handling your enquiry. We do not sell them, do not pass them to advertisers and do not share them with third parties, except where the law or an order from a competent authority requires it.

The details sit on a server we rent, in a data centre in Germany (European Union). The same goes for the form submission records in the site log.

6. How long we keep the enquiry

An enquiry is kept for up to 24 months from our last contact with you, and is deleted after that. If you ask us to delete it earlier, we delete it when you ask.

The record of the form submission is kept in the site log for up to 24 months from the date of submission and is deleted automatically. It holds the details you provided, the two consent tick-boxes (ticked or not) and the version of the consent wording in force at the time. The submission counter that protects the form from flooding is kept only by a hash of the IP address, without your details, and is deleted within an hour.

7. Cookies and analytics: this site has none

This site has no cookies, no web analytics, no advertising pixels and no files loaded from third-party services. Fonts and images are served from our own server. You read the page and nobody is following you around.

That is also why there is no cookie consent banner here: there is nothing to consent to.

If we ever add any measurement tool, we will update this document and ask for your consent before switching it on, not after.

8. Server-side technical records

Like any website, the server that hosts lidin.co.il records technical requests: IP address, time, page address and browser type. These records are used for maintenance and security only, and are not linked to the details you submit through the form. They are kept for up to 90 days and are then deleted automatically.

9. Security

Access to enquiries is limited to the people who work on them, and the connection to the site is encrypted (HTTPS). Absolute security cannot be guaranteed, but we apply accepted and up-to-date measures.

10. Your rights

• Access: find out what details of yours we hold.
• Correction: ask us to correct details that are wrong or out of date.
• Deletion: ask us to delete your details.
• Withdrawing marketing consent: at any time.

For any of these, write to support@lidin.co.il. We confirm receipt by the next business day and complete the request within 30 days. If the case is a complex one we may need up to 15 days more, and we will tell you if that happens.

How to revoke access to, and delete, data Lidin received from Meta and Google: section 12.10.

11. Marketing messages

The marketing tick-box is separate from the demo request, is not pre-ticked and is not a condition for submitting the form. Even if you leave it unticked, we will still answer your demo request.

Marketing messages go out by email only; this site has no other mailing channel. You can unsubscribe at any time: support@lidin.co.il or through the unsubscribe link in every message.

12. Lidin: data we receive from Meta and Google

12.1. What this section covers.

Lidin is a lead management system for offices and businesses that are our clients. An office can connect its Facebook Pages to Lidin so that leads from its Facebook and Instagram ads arrive straight in the system. People at the office can sign in to the system with a Google account. An office can also connect its Google Ads account to tell Google which leads from its ads turned out to be good ones. This section explains what data Lidin receives in each case, why, where it is stored, who it is not shared with and how to delete it.

12.2. Who is responsible for what.

Leads and all other data in the system belong to the office. The office is the database owner (בעל השליטה במאגר, the controller): it decides what data to collect and how long to keep it. Israsky stores and processes this data only for the office, on its instructions and under the data processing agreement attached to the service agreement with the office (here Israsky is the data holder, מחזיק, that is, the processor). We do not use this data for our own purposes.

12.3. What Lidin receives from Meta.

The office owner clicks "Connect Facebook" in Lidin, signs in to Facebook and chooses which Pages and advertising assets to open to Lidin. Lidin then receives:

• access tokens for the Pages and assets that were selected;
• for each selected Page, its ID, name, picture and category, and the IDs of the ad accounts and datasets selected in the same window;
• the Facebook account ID of the person who made the connection. We keep it only as a hash and use it in one case only: to carry out an access removal or a deletion request when Meta passes it to us. We do not store the name, email address or other Facebook profile data.

When someone submits a form in an ad of a connected Page (Instant Form), Lidin receives that lead:

• the answers in the form: usually name, phone number and email address, plus answers to any questions the office added to its form;
• the lead's ID at Meta, the time it was submitted, the platform (Facebook or Instagram) and the IDs of the form, ad, ad set and campaign it came from.

If the office sees the results of its advertising on the source screen, Lidin reads summary figures of its ad account (for example spend and number of leads), with no data about individual people.

Lidin does not read Page posts, comments, reactions or followers, and does not create or change ads, campaigns or budgets.

12.4. Why Lidin needs the Meta data.

Only to:

• get each lead into the office's system within a minute without losing it: if the connection was interrupted, Lidin fetches the missed leads from Meta once it is back;
• show the office which Page, form and ad a lead came from;
• check that the connection works, and warn the office at once if access was removed or the subscription was taken off;
• tell Meta about lead quality, if the office itself switched this on (section 12.6).

12.5. What Lidin receives from Google.

Signing in with Google. If the office allows Google sign-in, Google confirms to us who you are when you sign in. We receive your email address, the confirmation that it is verified, a permanent account identifier, and for a work account also the domain name. Your name and profile picture, if present, are used for display only and are not stored. This data is needed only to let you into the office's system and to record the sign-in in the access log. We do not receive your Google password, we get no access to your email, files or calendar, and we do not send Google any data from the system.

Connecting Google Ads (the office's choice). If the office owner clicks "Connect Google" and grants access, Google gives Lidin permission to upload conversion events to the office's Google Ads account through the Google Data Manager API. The office itself enters its Google Ads account number and the conversion the events go to. For each lead that came from the office's Google ads, Lidin sends the click identifier (GCLID, GBRAID or WBRAID), the time and the stage of the lead, for example "qualified lead". From Google, Lidin receives only an access token and a reply saying whether the upload was accepted. Lidin does not read campaigns, ads, audiences, reports or any other data from the Google Ads account.

People at Israsky do not look at data received from Google, except when you have asked us for help, when it is needed for security, or when the law requires it.

12.6. Lead quality reports to Meta and Google.

This option is off until the office switches it on. When it is on, it tells Meta and Google which leads turned out to be good ones, so that the office's ads find better-matched customers. Only the lead's stage and its identifiers are sent: to Meta, the lead's ID at Meta, the browser markers fbp and fbc, or the phone number and email address as an irreversible hash (SHA-256); to Google, the click identifier. Names, message texts and amounts are never sent. Only leads collected by a form that told the person about this transfer in advance are sent. Recipients: Meta Platforms Ireland Limited and Google Ireland Limited, Ireland (European Union). An event that has been sent cannot be pulled back from the advertising system.

12.7. Where the data is stored and who sees it.

The data is stored in the office's own separate database on our servers at Hetzner Online GmbH, in a data centre in Germany (European Union). Access tokens are stored encrypted. The shared part of the system, which routes a Meta notice about a new lead to the right office, keeps only technical numbers: the Page ID and the Facebook account ID as hashes, the lead's ID at Meta and the form ID, with no names or contact details. Leads are visible only to the office users the office has given access to. People at Israsky open an office's data only for maintenance and support, and every such access is logged. Data received from Google is also subject to the restrictions in sections 12.5 and 12.11 (Limited Use).

12.8. Who we do not share the data with.

We do not sell data received from Meta and Google, we do not pass it to other offices, advertisers or data brokers, we do not use it for our own advertising or our own purposes, and we do not train artificial intelligence models on it. The data leaves the office's database only:

• to Meta and Google, if the office switched on lead quality reports (section 12.6);
• to Hetzner, which runs our servers and does not use the data itself;
• where the law or an order from a competent authority requires it.

12.9. How long the data is kept.

• Leads are kept for as long as the office sets in its retention settings. When the office's agreement ends, the data is handed over to the office and deleted under the exit procedure attached to the agreement; it disappears from backups within 30 days of deletion.
• Meta and Google access tokens and the hash of the Facebook account ID are kept while the connection is active and are deleted when it ends: when the office disconnects the source in Lidin, when the person removes the Lidin app in their Facebook settings, or when Meta passes us a deletion request.
• Technical records of notices received from Meta (numbers with no names or contact details) are kept for up to 90 days.
• The email address, account identifier and domain received at Google sign-in are kept in the user's account until the office deletes it. A record of each sign-in is kept in the access log for 24 months, as the law requires, and then deleted.

12.10. How to revoke access and delete data.

• The office can disconnect Facebook or Google in Lidin at any time: Settings → Lead sources → "Disconnect". The Pages' subscription is removed, the Google permission is revoked, the tokens are deleted, and new leads stop arriving. Leads already received stay in the system until the office deletes them.
• The person who connected the office through Facebook can remove the Lidin app in their Facebook settings: "Settings & privacy" → "Settings" → "Apps and websites" (for business connections, "Business integrations"), and send a data deletion request there. Meta passes the request to our address https://app.lidin.co.il/connect/meta/data-deletion. We delete, in every office, the tokens and the account ID hash received through that account, and Meta shows you a confirmation code and a link where you can see whether the request has been carried out.
• You can also revoke the permission given to Lidin in your Google account: https://myaccount.google.com/connections ("Third-party apps & services").
• You can also send a deletion request by email to support@lidin.co.il.
• If you left your details in an office's ad and want to know what data is held about you, correct it or delete it, contact that office: it owns the database and makes the decision. If you write to us, we will confirm receipt by the next business day and pass your request on to the office.

12.11. Google's rules for data received through its APIs.

Lidin's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

Google's policy: https://developers.google.com/terms/api-services-user-data-policy

13. Changes to this document

This is version 4, in force from 24.09.2026.

What changed in it: section 12 was added, on the data Lidin receives from Meta and Google and how to delete it; section 1 now names this data too; section 2 now gives Israsky's full details. The form on this site, and the way we use what you submit in it, have not changed.

Earlier versions: version 3 (26.08.2026): we said how long we take to handle a request about your rights (§10), that marketing messages go out by email only (§11), how long the server's technical records are kept (§8), and where the data is stored, a server in a data centre in Germany (§5); version 2 (18.08.2026): §6 gained the description of the form-submission log and the submission counter, and the form gained a separate consent tick-box for using your details; version 1 (11.08.2026): the first text.

An update creates a new version with a new effective date, and the updated text is published on this same page.

14. Accessibility

The accessibility statement for this site: הצהרת נגישות (accessibility statement)

15. Contact

Israsky · email support@lidin.co.il · phone 050-577-0731

Business hours: Sunday to Thursday, 9:00 to 21:00. We are closed on Friday, Saturday, holidays and holiday eves.