Leadly מבית אימפקט (Leadly by Impact)
Privacy Policy
1. Scope and service
Leadly is a work management service for real estate agents and offices. This policy applies to goleadly.app, the Leadly application at agent.goleadly.app, and related services. Each office is responsible for the client information it enters; Leadly processes that information to deliver the service under the office's permissions. Last updated: October 19, 2026.
2. Information we process
Account and contact details such as name, email address, phone number, office and role; information users enter about leads, properties, tasks, appointments, transactions, documents and messages; information submitted through site forms and support requests; and technical information needed to operate and secure the service, such as IP address, browser, activity and error logs. Users should only enter client data they are authorized to process.
3. Why we use information
We use information to operate accounts and the service, associate users with offices, manage leads and properties, perform actions requested by users, synchronize integrations they choose, provide security and support, handle billing, comply with law, and improve reliability. AI features process information needed for the user-facing action under office permissions. Connected Google data is not used for targeted advertising or general-purpose AI model training.
4. Google Calendar and Google Tasks
Connecting either service is optional and requires the user's authorization through Google's consent screen. Leadly displays writable calendars and task lists so the user can choose a synchronization destination. The current implementation does not import the contents of existing Google events or tasks to build a profile. It uses the granted access to create, update and delete records originating in Leadly in the selected calendar or task list. The precise permissions are shown on Google's consent screen.
5. Information sent to Google
A synced appointment may include its title, location, dates and times, notes, participant names, and a link to the lead record in Leadly. A synced task may include its title, due date, status and notes; where present in the source record, those notes can include a lead's name and phone number, the agent's name, lead source, and a link to the lead record. Users should avoid entering information in notes that they do not want to appear in the selected Google account. Leadly retains the selected calendar or list, account address, and synchronized event or task identifiers to prevent duplicates and enable updates or deletion.
6. Limited use of Google data
Information obtained from Google APIs is used only to provide and maintain the calendar, tasks and search-volume features the user selected. We do not sell Google user data, transfer it to advertising platforms, use it for personalized ads or credit scoring, or use it to train general-purpose AI models. Human access is limited to user-requested support, security, or legal obligations, subject to access controls. Our use of Google data follows the Google API Services User Data Policy, including its Limited Use requirements where applicable.
Google Ads: Leadly reads only keyword search-volume data by city from Leadly's own Google Ads account, to decide which city pages to publish on its website. Leadly does not create or change campaigns, does not read ad or billing data, and does not share this data with anyone.
7. The "Leadly for Yad2" Chrome extension
The optional "Leadly for Yad2" Chrome extension lets an office publish a property from Leadly to the office's own Yad2 account in the office's browser. It has a single purpose: filling in and submitting Yad2's ad form with the details of a property the user chose in Leadly, and reporting the result back to Leadly.
What it handles. (a) Property details the user saved in Leadly: type, address, rooms, floor, price, description, features, contact name and phone, and property photos downloaded from Leadly's file storage (files.goleadly.app). These are entered into Yad2's form only. (b) From Yad2: the publishing packages shown to the office (package names, ads remaining and expiry), the result of the publication, and the new ad's link and status. These are sent to the user's Leadly office. (c) A pairing token that links the extension to the user's Leadly account, kept in the extension's local storage until the user disconnects it. (d) When Yad2 asks the user to sign in, the Yad2 phone number and one-time SMS code the user types in Leadly are entered once into Yad2's own sign-in form. They are not stored by the extension, and Leadly deletes them as soon as they are used. The extension never reads or stores Yad2 passwords or cookies. It does not read browsing history, other sites or other tabs.
Permissions. Host access is limited to yad2.co.il (the ad form, sign-in and the office's ad pages), Leadly (ai.goleadly.app, agent.goleadly.app, test-agent.goleadly.app) and files.goleadly.app (property photos). "storage" keeps the pairing token. "alarms" checks every 30 seconds whether the user sent a property for publishing. "power" keeps the computer awake while the extension is paired, so a publication sent from a phone can run. "debugger" is used only on the Yad2 tab the extension itself opened for a publication, to perform the clicks and typing the form requires; it is detached when that publication ends.
Use and sharing. Data handled by the extension is used only to publish the user's property on Yad2 and to show the result in Leadly. It is not sold, not used for advertising, credit or lending decisions, and not used to train AI models. It is not transferred to anyone other than Yad2 (to publish the ad) and Leadly (to report the result). The extension buys nothing, never deletes ads and does not change existing ads. Our use of this data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
Removal. Disconnecting the extension in its popup, or removing it from Chrome, deletes the pairing token from the browser. Records already saved in Leadly (for example the ad link) remain under the office's retention and can be deleted as described below.
8. Service providers and sharing
We rely on infrastructure, hosting, security, communications and support providers needed to operate Leadly, and on third-party connections a user enables, such as Google, WhatsApp or Telegram. One office's records are not exposed to another office as part of the service. Some providers may process information outside Israel, subject to appropriate safeguards and applicable law. We do not sell personal information.
9. Security and retention
We use access controls, activity records and reasonable technical and organizational measures to protect information. No system can guarantee absolute security. Information is retained while needed to operate accounts, maintain business records, provide support or meet legal obligations; periods vary by data type and office instructions. Disconnecting Google stops future synchronization but does not automatically remove appointments or tasks already written to Google, or source records retained in Leadly.
10. Your choices and deletion
Calendar and Tasks may each be disconnected in Leadly settings, and access may also be revoked in your Google Account's connected-app settings. After disconnection, no new sync is initiated through that connection, subject to operations already in progress. To delete a synchronized record, manage it in the service where it remains stored. For access, correction, export or deletion requests concerning Leadly data, contact your office administrator and Leadly; requests are handled subject to others' rights and applicable retention duties.
11. Cookies and the marketing site
The site and app may use browser storage and cookies for sign-in, security, preferences and operation. Information submitted in a site inquiry is used to respond and arrange a requested demonstration or trial. Marketing messages, if sent, are subject to applicable law and user preferences, and users may ask to stop them.
12. Changes
We update this document when the service or its data practices change and publish an updated date. A material new use of Google data will be disclosed and, where required, consent obtained before that use. The current version is available on this page.
13. Contact
For privacy questions, data requests or reports of a problem, use the Leadly contact page and identify your inquiry as a privacy request. Office users may also contact their office administrator.
