הגרסה בעברית

Privacy Policy · Tim8

Last updated: 5 November 2026 Version: 3.29

0. Introduction

This policy explains what personal information is collected on the website www.mytim8.com and in the Tim8 services, why it is collected, with whom it is shared, how long it is retained and what rights you have.

The policy is drafted in accordance with the Israeli Protection of Privacy Law, 5741-1981, including Amendment 13 to that law, and in accordance with the Protection of Privacy Regulations (Data Security), 5777-2017.

Accompanying documents: Terms of Use · Cancellation Policy · Accessibility Statement.

1. Who is responsible for the information

Controller of the database: the Service is operated by Tim8, Shlomi Baruch · Licensed business (Osek Murshe) no. 300613999.

Email for privacy enquiries and enquiries concerning personal information: support@mytim8.com

1.1 Two kinds of information, and two different levels of responsibility

This policy distinguishes between two kinds of information:

A. Information of which we are the controller. Information about agents registered to the Service, about prospective customers and about visitors to the website. This policy applies to that information in full.

B. Information that we hold on behalf of the agent. An agent who registers for the Service enters into the system information about their clients and about the properties they market. The agent is the controller of this information, and is responsible for the lawfulness of its collection and for its use. We act as a holder on their behalf and in accordance with their instructions alone, and we make no independent use of this information.

A client of an agent who wishes to access, correct or delete information about them should contact the agent with whom they are in contact. An enquiry that reaches us directly will be passed to the relevant agent, and answered by them.

2. The duty to inform

In accordance with the law, these are the particulars that must be provided to you at the time the information is collected:

Consent is inferred from an active and informed action: registering for the Service, accepting the terms of use, connecting a Google Calendar, or installing the browser extension. We do not use pre-ticked boxes, and we do not make the Service conditional on consent to purposes that are not required for it.

3. What information is collected

3.1 Information about the registered agent

A friend who joined through an invitation link: the referrer knows that the friend joined and made a first payment, because a credit is added to the referrer's balance as a result. The friend's licence number is kept in the referrer's balance record.

3.2 Information the agent enters about their clients and about properties

Subject to section 1.1B.

3.3 Digitally signed documents

The Service allows forms to be created for digital signature and returned as a locked file. From the signatory are collected a full name, contact details, an image of the signature, the time of signing and further particulars according to the type of form.

The signatory is not a registered user of the Service. They reach the form through a link that the agent sent them, and the agent is the controller of this information.

3.4 Collaboration between agents

The Service includes a network in which a property that an agent opens for collaboration is displayed to other agents in the system.

What is exposed: the details of the property and the details of the publishing agent. What is not exposed: the agent's client details. They are not displayed to any other agent under any circumstances.

3.5 External connections that the agent activates at their own choice

Google Calendar. An agent who chooses to connect their calendar grants a single permission, to read and write events in their own calendar. We do not request access to mail, contacts, files or any other content in the Google account.

Why the events are read. To show the agent their own calendar inside the Service, to answer their questions about their schedule, and to include the day's meetings in the morning update the Service sends them. Writing is used to create the meetings and reminders the agent asks for.

What we store. The Google access tokens, encrypted, for as long as the connection is active. We do not copy the calendar into our database. When an agent creates a meeting or a reminder through the Service, we store the event title, its time and the Google event id, so that we can raise the reminder on time and keep it in step with a change or a deletion. These are kept while the account is active and are deleted when the account is deleted.

Where it goes and why. When an agent asks the assistant about their calendar, the relevant event details are sent to the language model provider in order to compose the answer, and are not used to train models, as set out in section 4.3. The day's meetings appear in the morning update sent to the agent themselves on WhatsApp, and therefore pass through the business WhatsApp provider. Beyond this, calendar data is not transferred to anyone.

What we do not do. Calendar data is not sold, is not used for advertising or marketing segmentation, and is not used to train general artificial intelligence models. We do not allow a person to read it, except with the agent's consent, for security purposes or to diagnose a fault the agent reported, or as required by law.

Only events the Service created. The Service reads all events in the calendar in order to show the agent a complete picture, but it changes, moves and deletes only events that were created through it. An event the agent created themselves in Google Calendar is shown in the Service as read only.

How to disconnect. At any time, with the "Disconnect calendar" button on the settings page in the Service. Disconnecting revokes the permission at Google and deletes the access tokens on our side. The permission can also be revoked directly in Google account settings.

Compliance with Google policy. The Service's use of information received from Google APIs, and the transfer of that information, adhere to the Google API Services User Data Policy, including the Limited Use requirements. The policy is available at https://developers.google.com/terms/api-services-user-data-policy

The browser extension for publishing in Facebook groups. The extension works only after the agent pastes the connection code from the Service into it. Publishing is carried out from the agent's own Facebook account, from their own browser. The extension sends the Service the following information, and only it:

1. The connection code, with every request, to identify the account in the Service. On our side the code is stored encrypted, alongside a one-way hash for verification. Clicking "Disconnect" in the extension revokes the code on our side as well.
2. The Facebook account identifier (a number) from which the groups were loaded and from which each post was published, to make sure that publishing goes out from the right account.
3. The list of Facebook groups of which the agent is a member: the group name, its identifier, the group image, and its number of members when Facebook shows it. The agent uses the list to choose the groups to publish to.
4. The result of each publication: whether the post went out, and the address of the published post, so that the agent can see what was published and link to the post.
5. When a publication fails: an error code, and an excerpt of the Facebook response of up to 500 characters, in order to diagnose the fault.
6. Whether "automatic publishing" is turned on in the extension, and the notification settings the agent sets in it.

The extension does not send the Service the Facebook password, Facebook cookies or sign-in details, messages, the friends list, posts or other content from the account, or browsing history. The Facebook sign-in details stay in the browser and are used only for the publishing itself.

WhatsApp connection. An agent who connects their WhatsApp number allows the Service to receive and send messages on that number. Stored: the number (encrypted, with a one-way hash for identification), the time of connection, and the content of the conversation as part of the chat history. Messages pass through Meta, as set out in section 5. The connection can be disconnected at any time in the settings.

3.6 Technical information collected automatically

IP address, browser and device type, times of use and error logs. Used for operation, security and fault diagnosis.

"I am not a robot" check. On the sign-in, registration, password reset and password change pages, the Turnstile component of Cloudflare, Inc. runs, checking that the action is being carried out by a person. For this, Cloudflare processes the IP address, the fingerprint of the encrypted (TLS) connection and the browser details (User Agent). The component may use cookies or local storage that are strictly necessary for its operation, and the information may be processed in the United States. The component does not run on the forms that the agent sends to clients.

3.7 The radar: listings from Yad2

The radar finds real estate listings published on Yad2 that match the agent's clients.

• Where the listings come from. Listings are collected from Yad2 through services that run on the Apify platform: a service by LeadProof, an independent developer in Israel, for an hourly check of new listings; a service by nice_dev, a developer in the Apify community, for an initial fill and a monthly refresh of neighbourhood names; and a service that reads Yad2's sitemaps. We send these services only Yad2 search addresses and search parameters. We do not send them information about agents or their clients, and we do not ask them for the advertisers' contact details.
• What is kept for each listing. The listing details as published: the listing id and address, the transaction type, city, neighbourhood, street and house number, rooms, floor and the number of floors in the building, size, price, previous price and the time the price changed, property type, the type of advertiser (private, agency or unknown), a summary and the publication time. When the full listing details are fetched, the property features are also kept, and when the advertiser is an agent, their real estate licence number as it appeared in the listing. We do not keep the advertiser's name or telephone number, and we do not keep images.
• Why the licence number. To identify a listing of a property that is already in the Tim8 network, and not show it as a new listing, and to distinguish between listings by private owners and listings by agents. Other agents' licence numbers are not used to contact them or for marketing.
• For how long. A listing is deleted from our systems 30 days after it was published on Yad2, or 30 days after we first saw it when the publication time is not known. A listing whose price changed in the last 30 days is kept until 30 days after the change. A listing removed from Yad2 is deleted.
• Matching to a client is carried out on our side, and the result is kept in the agent's client file, like any other information the agent holds (section 1.1B).

3.8 Converting an address to a location

To show an accurate location and navigation, the Service sends the Google Geocoding service the address of a property (street, house number and city), and the location text of a meeting, for a navigation link, unless the meeting is at a property whose location is already stored. A point on the map is received in return. The request is made from the Service's servers only and not from the browser, without a client's name or any other identifying detail. The location point of a property is kept in the property file, refreshed after 25 days, and deleted after 29 days if it was not refreshed, in line with Google's terms.

4. The chat and the artificial intelligence systems

Tim8 is an automated system and not a human representative.

The content of the conversation is stored in the system in order to allow continuity between conversations and to support the Service.

4.1 Who processes the content of the conversation

Language processing is carried out by means of Anthropic, through its commercial programming interface.

What is sent to the provider: the content of the messages in the chat, and images that the user attaches to the conversation. In addition, the Service uses the same provider in order to extract client and property details from free text, to draft advertisements, to translate, and to classify Facebook groups.

What does not happen: there is no automatic character recognition from images, and there is no artificial intelligence provider other than the two set out in this section and in section 4.2.

4.2 Voice messages and transcription

An agent may send Tim8 a voice message on WhatsApp, or record a message in the chat. The recording is transcribed into text, and Tim8 treats it as a written message.

The provider: transcription is carried out by Soniox, a commercial transcription provider. Processing of the information at this provider takes place in the United States.

What is sent: the audio file of the message alone.

What is deleted immediately: on completion of the transcription we delete at the provider both the recording file and the transcript, in every case, including where the transcription failed. No recording remains with them and no transcript remains with them.

What we retain: the recording itself is not stored by us at any stage. The transcribed text is retained as a message in the conversation, like any written message, for as long as the account exists. In addition, a copy of the text is retained together with transcription quality data and the processing duration, for monitoring the quality of transcription. This copy is deleted automatically 90 days after the recording.

What was said in the voice message continues from there like any message in the chat, that is, it is also sent to Anthropic for the purpose of producing the answer.

4.3 What the providers do with the information

In accordance with the providers' commercial terms, the content of requests is not used to train models, and it is deleted from their systems within a short period after processing.

4.4 Reservation

We do not sell the content of conversations and we do not transfer it to a third party for its own purposes.

Sensitive information that is not required for the Service, such as detailed medical or financial information, should not be entered into the chat.

5. With whom the information is shared

We do not sell personal information and we do not trade in it. Information is shared only to the extent required for operation of the Service:

Providers that process information on our behalf are subject to contractual undertakings of confidentiality and data security, in accordance with regulation 15 of the Protection of Privacy Regulations (Data Security), 5777-2017.

5.1 Transfer of information outside Israel

• The information is stored in Frankfurt, Germany, a member of the European Union. That is where the database, the files and the signed documents reside.
• Server-side processing also takes place in Frankfurt, Germany. Routing of requests, encryption in transit and caching of static files may pass through the hosting provider's global network.
• What goes to the United States: the content of conversations and images in the chat, for the purpose of producing an answer; voice messages, for the purpose of transcription; WhatsApp messages; email messages that we send; calendar data, for those who connected it; addresses of properties and meeting locations, for converting them to a location; and the technical signals of the "I am not a robot" check. These are processed at the providers set out in the table above.
• What reaches providers around the world from the browser itself: the IP address and technical details, when a third party component loads, as set out in section 11.1 and section 11.2.

Transfers are carried out in accordance with the Protection of Privacy Regulations (Transfer of Information to Databases Abroad), 5761-2001, and on the basis of contractual undertakings by the providers to an adequate level of protection.

5.2 The payment processor

Payments are collected via Tranzila. The card fields on the payment page are Tranzila frames, and the card number goes from the browser directly to Tranzila, without passing through our servers. Full credit card details are not stored in our systems: we store only a token that allows Tranzila to charge the card, the last four digits, the card type and its expiry date. Tranzila does not allow deleting the token on its side. When the account is deleted, the token and the card details are deleted from our systems, so the card can no longer be charged through us. The invoice ID number, the business name if provided, your name and your email address are passed to Tranzila with each charge, and Tranzila issues the tax invoice and sends it to you. We keep a copy of the invoice details: the document number, the amount, the date and a key for viewing it, and it is shown on the billing page. No document is issued for the part paid from the refer a friend balance, and we record its amount and the VAT included in it.

6. The photograph of the real estate licence

The photograph of the licence card is an identifying document, and is therefore handled separately:

• Collected during the introductory conversation and displayed on the agent's profile page.
• Retained for as long as the account exists, since a valid licence is a continuing condition of use of the Service and not merely a condition of registration.
• Deleted together with deletion of the account.
• Access to it is limited to the agent themselves and to the system administrator.

7. How long the information is retained

7.1 Signed documents and account deletion

What happens to a frozen account:

1. A frozen account is kept in full and is not deleted automatically. If automatic deletion is enabled in the future, the agent will receive a notice, and deletion will not take place until a full week has passed since that notice.
2. All signed documents are sent to them by email when the account is frozen, so that the copies remain in their possession.
3. Invoices and billing records are retained in accordance with obligations under law.

A signatory to a document who is not the agent receives the signed document by email immediately upon signing, and therefore a copy is in their possession and does not depend on the existence of the agent's account.

7.2 Deletion of an account at the agent's request

The agent may delete the account at any time: in the account settings, on the billing page, or by asking in the conversation with Tim8 on the website. The deletion is confirmed with a one-time code sent to the email address registered to the account.

1. Upon confirmation, access closes and the subscription ends with no further charges.
2. All signed documents are sent to the agent by email, and documents signed or filled in during the waiting period are sent before the deletion.
3. The account is deleted 7 days after the request, and not before a full week has passed since the documents were sent successfully. Until then, the request can be canceled with the link sent by email.
4. The Google Calendar permission is revoked at Google as part of the deletion.
5. Only invoices and billing records are kept, as set out in the table above.

Full details are on the Data Deletion page.

7.3 Backups

The information is also kept in backups, for recovery in case of a failure only. Information deleted from the Service, including a deleted account, is removed from the daily database backup and from the file backup within 30 days, and from the monthly database backup within 12 months.

8. Mailings and marketing

Marketing content will be sent only with prior express and documented consent, or under the exceptions in section 30A of the Communications Law (Telecommunications and Broadcasts), 5742-1982.

Every marketing approach will state the identity of the sender, will state that it is an advertisement, and will provide a simple and free means of removal by the same means by which the message was sent.

Operational messages are not marketing mailings. Notifications about matches, calendar reminders, messages about subscription status and signed documents are part of the Service itself.

Consent to receive messages on WhatsApp and by email. When registering for the Service, consent to receive service messages and updates about what's new on WhatsApp and by email is part of the single approval box, which is not pre-ticked. Stored: the time of consent, the consent wording as shown, its version and its language. Stopping: sending the word "STOP" (or "הסר") in the WhatsApp conversation and confirming with the button, or the unsubscribe link in every email. The time of stopping is stored, so that we can make sure we do not approach again. Stopping does not affect operational messages (the previous paragraph).

8.1 The waitlist

Before the Service opens, you can join a waitlist on the "coming soon" page, in order to receive an email update when the Service goes live.

• What is stored: your email address, the language of the page, the page from which you signed up, the time of consent, the version of the consent wording and the wording itself as it was shown to you, and the time the sign-up was confirmed. For confirmation and removal, one-way hashes of the confirmation and removal links are also stored, and not the links themselves.
• Why: to send you a message about the opening of the Service and marketing messages about it, as you agreed, and to document that consent was given.
• Consent and double confirmation: signing up requires ticking a consent box, which is not ticked in advance. You are then sent an email with a confirmation button, and the sign-up takes effect only after you press it. The confirmation link is valid for 48 hours, and until you confirm, no further email is sent to you.
• A sign-up that was not confirmed: is deleted automatically 72 hours after the last confirmation email.
• Removal: you can remove yourself at any time, in a single click on the removal link in every marketing email. After removal, no further email is sent to you from the list. Your email address and the time of removal are kept, so that we can make sure we do not contact you again. You can ask for your details to be deleted entirely by contacting us: support@mytim8.com.
• Protection against abuse: to limit repeated sign-ups, a hash of the email address and the network (IP) address from which the request was sent are stored temporarily. Records older than two days are deleted from time to time.

8.2 The launch queue

Before the Service opens to everyone, a registered agent can join a queue. Stored: name, city, licence number and the time it was verified with the Registrar of Real Estate Agents, phone number (encrypted, with a one-way hash) and the time it was verified, a joining code, who invited them, status in the queue and the times of the messages. The information is used to manage entry to the Service and to send a message when the agent's turn comes. Leaving the queue is possible at any time from the screen.

9. Your rights

• The right of access under section 13 of the law, to inspect the personal information held by us.
• The right of correction and deletion under section 14 of the law, to request correction or deletion of information that is not correct, complete, clear or up to date.
• Deletion of the account at any time, as set out in section 7.2.
• Removal from mailings at any time.
• Withdrawal of consent, without affecting the lawfulness of processing carried out beforehand.

To exercise these rights: support@mytim8.com. Handling will be carried out promptly and no later than the periods prescribed by law. In order to protect the information, we may request identity verification details.

A client of an agent should contact the agent, as set out in section 1.1.

10. Data security

We implement security measures in accordance with the Protection of Privacy Regulations (Data Security), 5777-2017:

• Encryption of the communication between the browser and the server.
• Full isolation between accounts. Each agent views and edits only their own data and is not exposed to another agent's data. The isolation is enforced at the database layer and not only in the interface.
• Access control and permissions, backups and monitoring of security events.
• Sensitive access keys are held on the server side alone and are not exposed to the browser.

In the event of a serious security incident we will act in accordance with the reporting obligations under law.

No system is absolutely immune, and we cannot undertake complete immunity from unauthorised access.

11. Cookies and tracking tools

Measurement tools run only on the marketing pages and the registration page, and only after consent in the cookie banner (section 11.2). On the rest of the site, including the sign-in page, the office, the signing forms, the showcases and the payment page, there are no analytics tools, no marketing pixels and no tracking tools of any kind.

First party functional cookies: retaining the signed-in state, protecting the sign-in process against request forgery, keeping the choice made in the cookie banner, and remembering that the notice about the policy update was closed. These cookies are required for the operation of the Service and do not require consent.

The fonts on the site are served from our own server and not from an external party.

11.1 Third party components that load in the browser

On some pages, components load from the servers of external providers. On every such load the provider receives the IP address of the browser and ordinary technical details, such as the browser type and the page address, as does any server that is contacted. These are the components, and the pages on which they load:

Apify, Google Geocoding and the services that run on Apify operate from our servers only, and do not load in the browser.

11.2 Measurement on the marketing pages and the registration page

On the home page, the pricing page, the about page, the contact page and the registration page, two measurement tools run, only if you accepted them in the cookie banner. Until then nothing of them loads. On the rest of the site, including the sign-in page, the office, the signing forms, the showcases and the payment page, they do not load at all.

Legal basis: consent. Withdrawal: at any time, through the "Cookie settings" link at the bottom of these pages. After withdrawal the tools stop, their cookies are deleted from the browser, and nothing more is collected. The choice, accept or decline, is kept in your browser in our own cookie for 180 days.

12. Minors

The Service is intended for licensed real estate agents and for persons aged 18 and over. We do not knowingly collect information about minors.

13. Management of databases

The databases are managed in accordance with the law and its regulations.

The obligation to register a database under Amendment 13 applies to public bodies and to data brokers holding a database concerning more than 10,000 persons, and does not apply to us. The obligation to notify the Authority applies to a database containing information of particular sensitivity concerning more than 100,000 persons, and does not apply to us. The obligations of the law concerning collection, processing and security apply in any event, including to a database that is not subject to registration, and we act in accordance with them.

If the scale of activity changes in a way that brings these obligations into effect, we will act in accordance with the times and requirements prescribed by law.

14. Changes to this policy

We will update this policy from time to time. The updated text will be published on this page, stating the date of the update and the version number. Notice of a material change will be displayed on the site.

15. Enquiries and complaints

For any question, request or complaint on privacy matters: support@mytim8.com

If you are not satisfied with the handling of your enquiry, you have the right to apply to the Israeli Privacy Protection Authority.

Language. This is a translation for convenience. The Hebrew version of this policy is the binding one, and in any discrepancy between the versions the Hebrew text prevails.