Linx
Privacy Policy
This English version is a translation provided for convenience. The binding version of this document is the Hebrew original, which prevails in the event of any conflict or discrepancy. Exception: Section 6.5 (Use of Data from Google Workspace APIs), including the Limited Use Disclosure, is binding in both the Hebrew and the English versions. The two are written to state the same commitments, and neither is subordinate to the other. Linx Tech (Authorized Dealer Peter Kobi Gor, ID 032625048) respects your privacy. This policy explains how we collect, use and protect your information, in accordance with the Israeli Privacy Protection Law, 5741-1981, and with international standards. Version: 1.9 · Last updated: October 18, 2026
1. Information We Collect
We collect the following categories of information: 1. Information you provide: Name, email address, phone number (when you sign in with a WhatsApp code, or if you gave it to us), shipping address (when ordering), form of address / gender (optional, used solely to phrase how we address you), and your profile content. Credit card details are not stored by us; they are processed by a secure PCI-DSS certified payment provider. 2. Automatic technical data (metadata): When you use the site we collect your IP address, device type (User Agent), approximate location data (geolocation), login times and browsing patterns. 3. NFC scan data (hardware data): When an NFC card is scanned, the system collects technical data, including a scan counter that advances on each tap, the scanner's IP address and the device type. This data is used for security, fraud prevention and detecting reuse of an old link (anti-replay). 4. Sign-in data: You can sign in to the account with an email and password, or with Google, Facebook, a WhatsApp code or an email code. When you sign in through Google or Facebook (OAuth), we receive your email address, full name and profile picture, according to the permissions you approved. When you sign in with a code, the code is sent to the phone number (on WhatsApp) or to the email address on the account. 5. Data from social accounts you connected: If you chose to connect a business Instagram account or a Facebook Page, we read the account name, the profile picture and the follower count, and for Facebook also the list of Pages you manage (full detail in Section 6.6b). If you chose to connect a TikTok account or a YouTube channel, we read the account identifier, the handle, the display name, the profile picture and the follower or subscriber counts (full detail, including the permissions requested, the alternative that requires no account connection, and how to disconnect, in Section 6.6c). 6. Data from a Google Calendar you connected: If you chose to connect a Google Calendar, we read only the free time windows in the calendar (free/busy), and we write a new event when a visitor books a meeting. We do not read event titles, attendees or the contents of existing meetings. Use of this data is governed solely by Section 6.5, which prevails over every other provision of this policy. 7. Push notification data: When push notifications are enabled, the system stores a unique device token. This token is used solely to deliver notifications and is deleted automatically when notifications are disabled or the account is deleted. Providing information is up to you. You are under no legal obligation to give us information, but without the basic details (name and email address) we cannot open an account for you or provide the service, and without a delivery address we cannot ship you a physical card. Fields marked as optional, such as form of address, are not required at all and may be left blank.
2. Purposes of Use
• Operating the system and delivering the services. • Information security, fraud prevention and monitoring of cyber attacks. • Statistical analysis and improvement of the user experience. The statistics tools on the LINX site (such as Google Analytics and Microsoft Clarity) run only with your consent to statistics cookies (see Section 5). • Measuring LINX's advertising and showing LINX's ads, only with your consent to marketing cookies (see Section 5). One exception unrelated to cookies: reporting to Meta that a WhatsApp conversation started from a LINX ad became an enquiry, with no identifying details (see Section 6.6a). • Counting visits and actions on customer pages for the page owner, with no cookies and without storing the IP address (see Section 5). • Fulfilling orders and billing. • Contacting you and mailing (subject to your consent). • Operational notices and registration completion reminders. • Operating the AI Copilot tools (see Section 6 below). Exclusion: data received from Google Workspace APIs is not governed by the list of purposes above. Its use is limited solely to the purposes set out in Section 6.5 below, and does not include mailing, marketing, advertising, statistical analysis or general improvement of the service. In any conflict, Section 6.5 prevails. Automated account risk scoring: For security and fraud prevention, the system automatically computes a risk score for accounts based on registration and login data (including IP address and usage patterns). The score flags accounts for human review only and does not automatically block any account; every restrictive decision is made after human review.
3. Disclosure to Third Parties (Sub-Processors)
We do not sell your information. We transfer information only to providers essential to operating the service ("sub-processors"): • Supabase Inc., database hosting, user authentication and file storage. • Vercel Inc., website hosting and Edge servers. • Google LLC, OAuth sign-in, AI services (Vertex AI), Google Tag Manager, Google Analytics (only with consent to statistics cookies, see Section 5), Google Fonts (loading the fonts of the site and of customer pages, in which Google receives the IP address and browser details, with no cookie), Google Calendar API (see Section 6.5 below), and the YouTube Data API for connecting a YouTube channel and displaying its data on the mini-site (see Section 6.6c below). • TikTok Pte. Ltd., connecting a TikTok account in order to display its data on the mini-site (see Section 6.6c below). • Meta Platforms Inc., Facebook OAuth sign-in, Facebook Pixel and Conversions API (only with the visitor's consent to marketing cookies, see Sections 3.2 and 6.8), the WhatsApp Business Platform messaging channel and a conversion report on a WhatsApp conversation started from a LINX ad (see Section 6.6a below), and connecting a business Instagram account or Facebook Page in order to display account data on the mini-site (see Section 6.6b below). • Amazon Web Services, Inc., hosting Meta's Conversions API Gateway connected to the LINX pixel, on servers in the United States. The events the LINX pixel sends on the LINX site, only with consent to marketing cookies, also pass through it on their way to Meta (see Section 6.8). • Microsoft Corporation (Clarity), user-experience analytics including heatmaps and session recordings, for the purpose of improving the service, on the LINX site only. This data is collected only with the user's consent to statistics cookies (in the cookie banner or in "Cookie settings"). Input fields are masked in the recording, and on the checkout, contact, sign-in, sign-up and cancellation pages the whole page is masked. Clarity runs without Microsoft's advertising sync (Bing). • Grow (Meshulam Payment Solutions Ltd.), our payment processor: secure payment processing (PCI-DSS) and setting up standing orders. Credit card details are provided directly to the payment processor and are not stored on Linx servers. • Functional Software Inc. (Sentry), error and stability monitoring. When an error occurs, a cleaned technical report is sent (the error, its place in the code, the page and the browser), with no recording, no user details and nothing stored in the browser. This report is necessary for the proper operation of the service and is sent without consent too. Session replay and performance measurement for troubleshooting run on the LINX site only, never on customer pages, and only with consent to statistics cookies: approximately 10% of sessions are sampled and 100% of sessions in which an error occurred. Replay is configured not to send personally identifying information by default (sendDefaultPii=false), with built-in text masking and media blocking. • Telegram FZ-LLC, delivering notifications and messages (personal assistant) to users who connected their Telegram account. • Courier companies, shipping hardware products. • Cloudflare Inc., security services, bot protection (Turnstile) and CDN. We verify that these providers meet strict information-security standards.
3.1. Transfer to External Tools (Webhooks)
A user who configures a webhook URL for their lead forms causes the enquiry data (name, phone, email, note) to be transmitted to an external server that is not under Linx Tech's control. The platform records the webhook delivery in internal logs (webhook_logs), but is not responsible for the security of the information once it has reached its destination.
3.2. Third-Party Pixels and Tracking Tags
When a mini-site owner enables pixels and tags (Google Analytics, Meta Pixel, TikTok Pixel, LinkedIn Insight Tag), that owner becomes an independent Data Controller with respect to their visitors' data, and Linx Tech acts as a processor on their behalf with respect to that data. These tools load only after the visitor consents on that page: Google Analytics only with consent to statistics cookies, and Meta, TikTok and LinkedIn only with consent to marketing cookies. Each customer page asks separately, and a choice made on the LINX site or on another page does not apply to it. Google's advertising features are always off in the page owner's Google Analytics. Browser-side pixel scripts send data from the visitor's browser to Meta, Google, TikTok or LinkedIn. In addition, conversion events on the server-to-server channel (Conversions API) pass through Linx servers on their way to Meta, as detailed in Section 6.8 below. Alongside mini-site owners' pixels, Linx operates its own system pixel to measure the effectiveness of Linx's own advertising. With respect to system pixel data, Linx Tech is the Data Controller. The system pixel does not run on customer pages (mini-sites and customers' domains), and Linx sends no event of any kind to the system pixel from a customer page, not even when a contact form is submitted. It runs only on the LINX site itself (including the store, checkout and the dashboard), and only after the visitor consents to marketing cookies in the cookie banner or in "Cookie settings". System pixel events carry no name, phone or email (Advanced Matching is off). As with every event sent through Linx servers, Meta receives the visitor's IP address and browser type (User Agent) in the clear, and the identifiers held in Meta's _fbp and _fbc cookies. Detailed in Section 6.8.
3.3. Disclosure to Public Authorities
A competent authority sometimes approaches us with a request for information. This is how we handle such requests: • Only on a valid legal instrument: No information is disclosed on the basis of a telephone call, or of a request that is not supported by a valid legal document identifying the authority, its legal power and the proceeding. A request that does not meet this is answered in writing with a request for a proper instrument. • Information belonging to a business customer: With respect to leads, CRM data and visitor data collected through a customer's assets, the customer is the owner of the data and Linx Tech acts solely as a processor on their behalf (see Section 9.2 of the Terms of Use). Such a request is referred to the customer, and it is the customer who answers it, unless the law directs otherwise. • Minimum disclosure: Only the records named in the instrument are disclosed, and only for the period it specifies. We do not provide a general export of a database and we do not add information that was not requested. • Notifying the user: We will notify the user that information relating to them has been requested, unless we are prohibited from doing so by law or by court order. • A request exceeding its authority: A request that appears unlawful, or that exceeds the power it relies on, is not carried out before legal advice is obtained, and a written objection is filed in respect of it. • Record keeping: Every request is recorded by us: the date it was received, the identity of the authority, the power asserted, what was requested, what was actually disclosed and who approved the disclosure. It is clarified that our infrastructure providers (see Section 3 above) may receive requests directly from authorities in the jurisdictions in which they operate, in accordance with their own policies and without this passing through us.
4. International Data Transfer
Some of your data is processed and stored on secure cloud servers located outside Israel, through the cloud providers listed above. The primary database is hosted in the Asia-Pacific region (Seoul, South Korea) at Supabase; Vercel's website and Edge servers are deployed globally; Google services (including Vertex AI, the Google Calendar API, the YouTube Data API, Google Analytics and Google Fonts) operate from Google servers in the United States and the European Union; Meta and TikTok process data on their servers in the United States, Europe and Asia respectively; Microsoft (Clarity), Functional Software (Sentry) and Cloudflare process data on their servers, including in the United States; and Meta's Conversions API Gateway connected to the LINX pixel is hosted at Amazon Web Services in the United States. This transfer is subject to appropriate security measures, including encryption in transit (TLS/SSL) and at rest. Use of the service constitutes consent to the transfer of information to servers outside Israel, except for transfers to statistics and marketing tools (Google Analytics, Microsoft Clarity, Sentry recordings and performance measurement, Meta and its Conversions API Gateway, and on customer pages the page owner's tools as well), which take place only with your consent to the relevant category and can be withdrawn at any time (see Section 5).
5. Cookies
We use cookies and similar technologies (browser storage, vendors' pixels and scripts) in three categories. The full detail, including every cookie, its purpose and how long it is kept, is in our Cookie Policy (version 1.5). • Necessary: sign-in, cart and checkout, security, language and accessibility, and remembering your cookie choice. Always on and need no consent. Sentry's technical error report (see Section 3) is necessary too, and stores nothing in the browser. • Statistics: Google Analytics, Microsoft Clarity, Sentry recordings and performance measurement, and LINX's own usage data. On customer pages: the page owner's Google Analytics, and recognising a returning visit to that page. Consent only. • Marketing: the Meta pixel and Conversions API, and ad click identifiers. On customer pages: the page owner's Meta, TikTok and LinkedIn. Consent only. Your choice. Before you choose, no statistics or marketing tool loads and no identifier is written to the browser. The cookie banner has three equal buttons: "Accept all", "Necessary only" and "Customize". The LINX site and each customer page ask separately, and a choice on one does not apply to another. The choice is kept in the browser for 12 months. If your browser sends a Global Privacy Control signal, marketing cookies are off, whatever the stored choice. Changing or withdrawing consent. You can change or withdraw consent at any time, as easily as it was given, through the "Cookie settings" link at the bottom of every page of the LINX site, on the checkout page, in the dashboard menu and at the bottom of every customer page. Withdrawing stops the category's tools, deletes from the browser its cookies that LINX controls, and reloads the page once. Counting visits on customer pages, with no cookies. A page owner sees how many people viewed their page and acted on it. LINX counts this for them with no cookie and without storing or reading anything in the browser, apart from your cookie choice: the server computes in memory a daily key from the page, the IP address and the browser string, with a random value for that day that is deleted 30 minutes after midnight (Israel time). The IP address is not stored, and the key is different for every page and changes every day. A visitor who chose "Necessary only" on the page is counted as a number only, and a visitor who chose "Do not count my visits" in "Cookie settings" is not counted at all. With consent to statistics on that page, an identifier for that page only is also kept in the browser, for up to 13 months. Detailed in Section 5.3 of the Cookie Policy. The consent record. Every choice and every change is recorded by us, so that we can show which choice was made and when: a random identifier of the choice, the site or page, the version of the question, the answers, where the choice was made (banner or settings), the browser family and the time. No IP address and no full browser string. The record is kept for 36 months and then deleted. You may also change your browser settings to block cookies, but doing so may impair the user experience.
6. Processing by Artificial Intelligence (AI)
The system uses AI agents (large language models / LLMs) to provide advanced services. The AI agents use the Google Vertex AI service (Gemini model). The information transmitted to the AI engines includes: • AI Copilot: A text instruction plus account data (tag names, URLs, statistics), for account management. • Personal AI agent: Visitors' questions plus profile information (bio, links, services), for automated replies to visitors. • Profile setup assistant: Name, role, business description, for automated setup. • Sales advisor: Visitors' questions plus product catalogue information, for sales guidance. • Graphics generation: A text prompt, for image generation. • Card Studio: When a background for the card is created, the following are also sent at the user's choice: the logo in the design (to match its colours; this can be switched off), a style picture and a photo of the user, and, when the user asks for a change, the design itself. The style picture and the user's photo are processed in real time and are not stored on Linx servers; only the resulting design is kept. A photo of a person is used only with the user's explicit consent, and only if it is the user's own or the user has permission from the person in it. • Speech to text: An audio file, processed and deleted immediately (not retained on the server). • Business card scanning: A photograph of a physical business card taken by the user is processed in real time to extract contact details (Google Vertex AI) and deleted immediately; it is not stored on Linx servers. The extracted contact details are saved as a lead in the user's CRM only.
6.1. Retention of AI Conversation Data
• AI Copilot conversations: Retained in the system, including the request type, timestamp and a summary. • Personal agent conversations: Retained in the system, including the content of the questions and answers. • Usage logs: Retained, including token counts (input/output), model and cost. • Purposes of retention: Improving service quality, monitoring for abuse, pattern analysis and technical support. • Retention period: 12 months from the date of the conversation, after which the data is anonymised or deleted. • Transfer to third parties: Conversation data is transmitted to Google Vertex AI for real-time processing only. Google does not use the data to train models (Vertex AI Data Governance). Conversation data is not sold or transferred to any further third party. • Right to deletion: An account holder may request deletion of their AI conversation history by contacting support.
6.2. Affiliate and Analytics Tracking
The system operates an affiliate tracking mechanism in order to identify referrals made through affiliate codes. This mechanism uses cookies and localStorage to attribute a conversion to the referring affiliate and to record the conversion. An affiliate code from a referral link is held in the page's memory for that visit only, and is stored in the browser for 30 days only if the visitor clicked "להחלת ההנחה" (apply the discount). Arriving through the link is counted as a number (code, page, time), with no IP address and no browser details. This tracking data is used solely to calculate affiliate commissions and is not used for marketing or for exposing personal information.
6.3. Automatic Lead Score (Lead Scoring)
The server gives each enquiry a lead score from 0 to 100 based on what it contains (such as a phone number, an email address, the length of the message and how it arrived), without artificial intelligence. This data is accessible to the account holder through the lead management dashboard (CRM) and is deleted together with the lead data when the account is deleted. It is not shared with third parties, with one exception: when a contact form is submitted on a mini-site whose owner connected a Meta pixel of their own, and subject to the visitor's consent to marketing cookies on that page, Lead conversion events are sent to the mini-site owner's pixel at Meta with identifying fields hashed only, as detailed in Sections 3.2 and 6.8. For accounts associated with an organisation, see Section 6.3.1 below.
6.3.1. Privacy in Organisation Accounts
When a user joins an organisation on LINX (at the invitation of an organisation administrator, and subject to explicit consent on the joining screen), the organisation's administrators and owners may view the account's data and activity in the organisational context: lead details and analytics collected through organisational assets, usage statistics, and cards or mini-sites created for the organisation. This sharing is intended for managing the organisation's team and business activity. • Personal assets remain private: Personal cards, mini-sites and tags (including pet tags) that do not belong to the organisation are not exposed to the organisation's administrators. • Informed consent: The exposure is presented to and explicitly approved by the user when joining the organisation; there is no automatic joining without consent. • Organisation control: The organisation administrator is the owner or holder of the database with respect to organisational data. The full allocation of responsibility is set out in the organisational terms of use and in the data processing addendum (DPA). • Leaving an organisation: When a member leaves the organisation, their personal assets remain theirs; assets supplied or funded by the organisation may remain the organisation's property.
6.4. Sharing Information with Linx Ambassadors (Ambassador Consent)
When a purchase is made through an ambassador's referral link, the purchaser may voluntarily opt in to sharing some of their details with the ambassador who referred them: • 6.4.1. Information shared: First name, first letter of the surname, and a partially masked email address (for example: k***@gmail.com). • 6.4.2. Purpose of sharing: Mentoring, marketing follow-up and initial contact within the LINX NET network, only. • 6.4.3. Default is no sharing: If the purchaser does not consent, the conversion will still be counted and the ambassador's commission calculated, but the purchaser's details will not be exposed to the ambassador in any way. • 6.4.4. Restriction on use: The ambassador may not use the information received for direct marketing, for selling data, or for any purpose not directly related to the purpose of the sharing. A breach will result in immediate termination of participation in the programme. • 6.4.5. Right of withdrawal: The purchaser may request removal of the exposed data by contacting support@linxcard.me.
6.5. Use of Data from Google Workspace APIs (Google Calendar)
The system supports integration with Google Calendar for automatic meeting scheduling by the AI agent. This section prevails over every other provision of this policy with respect to data received from Google Workspace APIs, including Sections 1, 2, 6.1 and 7. Use of the information is as follows: • Type of information and scopes requested: The system requests two narrow scopes only: calendar.freebusy, reading availability (free/busy) with no access to event contents, and calendar.events, creating an event in the calendar. We do not request access to calendar settings, the calendar list, or their sharing permissions. Users who connected their calendar before the scopes were narrowed may still hold a broader grant given previously; it can be revoked and reconnected through Google account settings. • Purpose of use: The system reads availability data (free/busy) solely in order to offer meeting times to mini-site visitors, and writes a new event to the calendar only when a visitor books a meeting. The system does not read or view the contents of existing meetings (titles, attendees or details). This is the only feature in which calendar data is used, and it is presented prominently in the user interface, on the settings screen and in the meeting booking conversation itself. • Exactly what is transmitted to the AI engine: From the calendar data we compute the free time windows only (a start time and an end time). That list of free windows is transmitted to Google Vertex AI in real time, for one purpose only: phrasing a proposal of meeting times for the visitor. Event titles, attendee names, descriptions and locations are not transmitted to the AI engine, because we never read them at all. • Retention: We do not retain calendar data. Free time windows are recomputed on every conversation and are never written to our database. The agent's reply to the visitor, which may mention the times it offered, is kept in the conversation transcript under Section 6.1 and is visible to the calendar owner, who is the user that granted the permission. Only the OAuth access tokens are stored, encrypted, and only for as long as the connection is active; they are deleted on disconnection or account deletion. • Revoking permission: The user may disconnect the calendar connection at any time through Settings / Integrations in the dashboard, or through Google account settings. On disconnection we delete the access tokens. Limited Use Disclosure. Linx Tech's use and transfer of information received from Google's APIs to any other app adheres to the Google API Services User Data Policy, including its Limited Use requirements. Beyond that reference, we commit expressly and directly, with respect to all information received from Google Calendar: • One purpose only. We use the information solely to provide and improve the user-facing feature for which permission was granted, namely offering free meeting times to a visitor and booking a meeting in the calendar. We put it to no other use, and in particular not to statistical analysis, not to pattern analysis and not to lead scoring. • Never for advertising. We do not use Google Calendar data for advertising of any kind, including personalised advertising, interest-based advertising and retargeting, and we do not transfer it to advertising networks, advertisers or data brokers. This data is not included in conversion events sent to Meta or to any other advertising platform. • Not read by humans. Information received from Google Calendar is not written to system logs and is not accessible to Linx employees or its contractors. Access to it is automated only. Narrow exceptions: your explicit consent with respect to a specific item, necessity for security purposes or to comply with applicable law, and aggregated, anonymised data for internal operations. • Never used to train models. We do not use Google Calendar data to develop, improve or train generalised or non-personalised artificial intelligence or machine learning models. The transfer to Google Vertex AI is for real-time inference only, and Google does not use this data to train models (Vertex AI Data Governance). • Never sold, never transferred. We do not sell Google Calendar data and we do not transfer it to third parties, except where the transfer is necessary to provide the feature itself (Google, as the operator of the calendar and of the AI engine), for security purposes, or to comply with applicable law.
6.6. Telegram Integration (Personal Assistant)
The platform allows users (on selected plans) to link their private Telegram account to the system through the official Linx Assistant bot. Use of this feature includes: • Push notifications: Sending information about customer enquiries (leads), including the name, phone and email of the visitor who contacted you, directly to your Telegram inbox. • Data querying (AI chat): Messages you write to the bot (for example, "show me this week's leads") are processed in real time by Linx servers and at times by an AI model in order to compose the answer. • Telegram policy: Sending and receiving messages through the Telegram application is additionally subject to the terms of use and privacy policy of Telegram FZ-LLC.
6.6a. WhatsApp Channel (WhatsApp Business Platform)
The platform operates an official WhatsApp communication channel through Meta Platforms Inc.'s WhatsApp Business Platform. Contacting Linx's WhatsApp number involves processing the following information: • Conversation retention: The content of the messages you send and receive on the channel is retained in Linx's systems (conversation history) for service continuity, support and record-keeping. • AI processing: Messages are processed in real time by Linx's AI agent (Lia) for automated replies. The principles set out in Sections 6 and 6.1 above apply. • Lead capture: Contact details provided in a conversation (name, phone, areas of interest) may be saved as a lead in the system for further handling. • Escalation to a human representative: Certain conversations (for example a request for a representative or a complex enquiry) are passed to the Linx team, and a summary of the conversation is sent to an internal Linx management channel (Telegram) for further human handling. • A conversation that started from an ad, and reporting to Meta: When you contact us from a LINX ad on Facebook or Instagram, Meta attaches the ad's details and a click identifier (ctwa_clid) to the first message, and we keep them with the conversation to know which ad the enquiry came from. If the conversation becomes an enquiry (details are saved so that we can get back to you, or a call with a representative is requested), LINX reports this to Meta once, through Meta's Conversions API for business messaging, to measure which ads bring enquiries. The report contains only the click identifier, the ID of LINX's WhatsApp Business account and the event type (LeadSubmitted), with no name, phone number, email or conversation content. This report is not related to cookies and does not depend on consent to marketing cookies. Questions about it can be sent to support@linxcard.me. • Meta policy: Sending and receiving messages on WhatsApp is additionally subject to the terms of use and privacy policy of WhatsApp and of Meta Platforms Inc. In addition, LINX sends automated WhatsApp messages from its own number, including: a new-lead alert to the page owner, a daily summary, a notice before a plan ends, and a confirmation to a visitor who asked for one on a form, sent on the page owner's behalf. The daily summary and the visitor confirmation are kept in the history of the LINX WhatsApp channel.
6.6b. Connecting an Instagram Account and a Facebook Page
The platform allows users to connect a business Instagram account and/or a Facebook Page they own, in order to display real account data on the mini-site instead of manually entered data. The connection is made through Meta's official permissions screen and requires your explicit approval. • Permissions requested: instagram_business_basic for Instagram, and pages_show_list and pages_read_engagement for Facebook Pages. We do not request publishing permission, and we have no ability to publish, edit or delete content on your behalf. • Information read: The account's username and display name, the profile picture, the follower count, and for Facebook also the list of Pages you manage and the Page's follower count. We do not read private messages, comments, follower lists or post content. • What is displayed publicly: The public mini-site displays the follower count, the profile picture and a "connected" mark next to the link. This mark indicates that the page owner completed a genuine connection to the account, not that the account was verified or endorsed by Meta. • Storage: Access tokens are stored encrypted in the database and are not exposed in the browser or on the public page. Follower counts are refreshed periodically for as long as the connection is active. • Disconnection and deletion: Any account can be disconnected at any time from the integrations screen. Disconnecting deletes the token and removes the connection mark from the public page immediately. Revoking the permission on Meta's side (from Facebook or Instagram settings) triggers the same automatic deletion on our side. • Meta policy: The connection and use of the API are additionally subject to the terms of use and privacy policy of Meta Platforms Inc.
6.6c. Connecting a TikTok Account and a YouTube Channel
As with the Instagram and Facebook connection, the platform allows you to connect a TikTok account and/or a YouTube channel you own, in order to display real account data on the mini-site instead of manually entered numbers, and to receive the connection mark next to the link. The connection is made through TikTok's or Google's official permissions screen and requires your explicit approval. • Permissions requested: For TikTok, user.info.basic, user.info.profile and user.info.stats. For YouTube, youtube.readonly. We do not request publishing permission, and we have no ability to publish, edit or delete content on your behalf. • Information read: On TikTok, the account identifiers (open_id and union_id), the username (@) and display name, the profile picture, the follower count, the following count, the likes count and the video count. On YouTube, the channel identifier, the handle (@), the channel title, the channel picture, the subscriber count and whether you chose to hide it. We do not read private messages, comments, follower lists or video content. • Clarification regarding the scope of the YouTube permission: The youtube.readonly permission is Google's general read scope for YouTube, and it is broader than the use we actually make of it. We read only the channel details listed above (a single call to channels?part=snippet,statistics&mine=true), and we do not access your videos, playlists, subscriptions, watch history or channel analytics. • What is displayed publicly: The follower or subscriber count and a "connected" mark next to the link. If you have hidden your subscriber count on YouTube, the number is not displayed and only the connection mark is shown. This mark indicates that the page owner completed a genuine connection to the account, not that the account was verified or endorsed by TikTok, Google or YouTube. • Storage: Access tokens are stored encrypted in the database and are not exposed in the browser or on the public page. The TikTok access token is valid for 24 hours and the refresh token for up to one year, and it rotates on each use. The counts are refreshed periodically for as long as the connection is active. • Disconnection and deletion: Any account can be disconnected at any time from the integrations screen. Disconnecting deletes the token and removes the connection mark from the public page immediately. You may also revoke the permission directly in TikTok's settings, and for Google from the permissions page of your Google account. • Alternative without connecting an account: You can obtain the connection mark without connecting an account at all, by placing a one-time verification code in the channel or profile description. With this method the system reads public information only in order to locate the code, receives no access to the account, and stores no token whatsoever. The code itself is derived cryptographically and is not stored by us. • YouTube API Services: The platform uses YouTube API Services. Such use is subject to the YouTube Terms of Service and the Google Privacy Policy. You may revoke Linx's access to your YouTube data at any time through the Google security settings page. • TikTok policy: The connection and use of the API are additionally subject to TikTok's terms of use and privacy policy.
6.7. Public Profile Exposure to Search Engines (SEO Indexing)
When search engine visibility is enabled, the system allows search engines (such as Google and Bing) and AI engines (such as Perplexity) to crawl and display the profile page in search results. The exposed information includes: name, role, profile picture, biography, links and contact details, as uploaded by the profile owner. By default, a mini-site is not listed by search engines. The system marks it noindex and leaves it out of the sitemap until its owner chooses to turn on the "Search Engines & AI" switch in the mini-site's advanced settings (opt-in). You may turn the switch off at any time. Once it is off, the system marks the page noindex again; removal from existing search results depends on the search engines' re-crawl rate and may take several days to several weeks. The page itself stays public at its address either way, and the switch does not affect the preview of a shared link, for example on WhatsApp or a social network: whoever receives the link sees the page's name, description and image even while the switch is off, except for a password-protected page.
6.8. Server-to-Server Conversions (Facebook Conversions API / CAPI)
The platform may transmit conversion events (such as purchase, registration, page view, form submission) to Meta (Facebook) servers through the Conversions API (CAPI), in addition to or instead of the browser-side Pixel. These events are sent from the visitor's browser to Linx Tech servers, pass through Linx Tech servers, and are forwarded from there to Meta. • Type of data: Pixel identifier, event type (Purchase, PageView, Lead), cookie identifier (_fbp/_fbc), and in the mini-site owner's Lead events also identifying fields the visitor provided in the form (email, phone, name, and depending on the form's configuration also gender and date of birth). The identifying fields are hashed (SHA-256) on Linx servers before being sent to Meta. The visitor's IP address and User Agent are sent to Meta in the clear (not hashed), in accordance with Meta's technical specification. • Purpose: Improving the measurement accuracy of the mini-site owner's advertising campaigns, including conversion tracking not captured due to cookie blocking in the browser. • Linx system pixel: Alongside the mini-site owner's pixel, Linx measures its own funnel, on the LINX site only (including the store, checkout and the dashboard) and not on customer pages. These events (such as page view, button click, enquiry, registration, add to cart and purchase) are sent without email, phone or name (Advanced Matching is off). As with every CAPI event, Linx servers attach the visitor's IP address and User Agent in the clear, and the _fbp/_fbc identifiers if they exist in the browser. The LINX pixel is also connected to Meta's Conversions API Gateway, hosted at Amazon Web Services in the United States, and the events the pixel sends also pass through it on their way to Meta. • Consent: Transmission of the mini-site owner's CAPI data, with the identifying fields it carries, is conditional on the visitor's consent to marketing cookies on that page. Without consent no event is sent to their pixel. Linx's own system measurement is conditional on the visitor's consent to marketing cookies on the LINX site, and does not run on customer pages at all, not even when a contact form is submitted. Without consent, Linx servers forward nothing to Meta from the website. The conversion report from a WhatsApp conversation that started from a LINX ad (Section 6.6a) is not a website event and does not depend on cookies. If the browser sends a Global Privacy Control signal, marketing cookies are off and no event is sent. • Data Controller: With respect to the mini-site owner's pixel, the mini-site owner is the independent Data Controller and Linx Tech acts as a processor on their behalf (the data passes through its servers). With respect to the system pixel, Linx Tech is the Data Controller. • Meta policy: The transmitted data is subject to the Meta Business Tools Terms.
6.9. Bot Protection (Cloudflare Turnstile)
The site uses Cloudflare Turnstile, an invisible verification service (invisible CAPTCHA) from Cloudflare Inc., for protection against bots, abuse of forms, and prevention of automated attacks. • What is collected: Turnstile collects minimal technical data for verification purposes (such as IP address, browser data and interaction patterns), without using tracking cookies. • Purpose: Distinguishing human users from automated bots, without disrupting the user experience. • Data processing: The data is processed by Cloudflare in accordance with Cloudflare's privacy policy and subject to the Turnstile privacy addendum. • Data retention: Cloudflare does not use Turnstile data for advertising or personal tracking. The data is retained for a limited period required for security purposes only.
7. Data Retention Periods
We retain your personal information for as long as your account is active and for the time required for the purposes for which it was collected. The details are as follows: • Profile and account data: Permanently deleted at the end of a 30-day cancellation window from the deletion request. • Aggregated, non-identifying analytics data: May be retained indefinitely for the purpose of improving the service. • Page load speed measurements (web_vitals): When pages on the site load, technical measurements of loading speed and stability are sent to us (such as server response time, the time until content is displayed, and layout shifts), together with the type of page (for example a mini-site or the home page, without the page address), the device class (phone, tablet or computer), the browser family, the connection type, whether the visit comes from Israel as determined by our hosting provider, and, with consent to statistics cookies on the LINX site, whether the browser is signed in to a Linx account. These measurements contain no IP address, no visitor identifier and no cookies. Within about an hour of arrival they are stored with the hour only and in random order, without the exact time they arrived. We do not link them to any other data we hold, and we do not use them to identify anyone. A visitor who chooses "Necessary only" in the cookie banner, including during a visit, or who chooses "Do not measure my visit" in "Cookie settings", is not measured. They are used only to improve the speed of the service and are deleted automatically after 90 days. • Records of views and taps on customer pages: Deleted automatically after 90 days. The daily random value from which the counting key is derived is deleted 30 minutes after midnight (see Section 5). • Cookie consent records: Kept for 36 months, with no IP address, and then deleted. • Transaction and billing records: Retained for 7 years in accordance with Israeli tax law. After the account is deleted they are kept detached from it. • Abuse logs: Retained for 3 years from the time of the record for legal defence, even if the account is deleted in the meantime. In that case they are kept detached from the account. • Login records and IP addresses (login_events): Retained for 12 to 24 months for security, fraud detection and legal defence. • NFC anti-replay data: Retained for 90 days for security. • Social and third-party connection tokens (OAuth): Stored encrypted only for as long as the connection is active, and deleted immediately when the connection is disconnected from the integrations screen, when the permission is revoked on the provider's side, or when the account is deleted. • Ambassador commission data: Commission records, clawbacks and wallet balances are retained for 7 years in accordance with tax law. • Database backups: Information may remain in encrypted backups for up to 90 days from the date of deletion.
8. Your Rights
Under the Israeli Privacy Protection Law you are entitled to review the information held about you and to request its correction or deletion. For enquiries on this matter: support@linxcard.me. In addition, we honour the following rights in accordance with GDPR principles: • Right to data portability: You may request an export of all your data in a structured format (JSON/CSV). • Right to restriction of processing: You may request that processing of your information be frozen (without deletion) for a defined period. • Right to object: You may object to processing of information for direct marketing purposes. • Right to withdraw consent: Consent to statistics or marketing cookies can be withdrawn at any time, as easily as it was given, through the "Cookie settings" link (see Section 5). For further details on data deletion, see our Data Deletion Policy. Complaint to the Privacy Protection Authority: If you are not satisfied with how your enquiry was handled, you may file a complaint with the Israeli Privacy Protection Authority, privacy.gov.il.
8a. The Company's Databases
Amendment 13 to the Privacy Protection Law, which came into force on 14 August 2025, abolished the general duty to register databases with the Registrar of Databases and replaced it with a narrow registration duty applying only to defined categories of database. As at the date of this policy, the Company's databases do not fall within those categories and are not subject to registration. This does not derogate from the Company's other duties under the Law and under the Privacy Protection Regulations (Information Security), 5777-2017. The Company maintains an internal database definitions document as required by regulation 2, acts in accordance with the notice and transparency duties set out in this policy, and will register a database if and when the scale of its activity or the nature of the information requires it by law.
9. Breach Notification
In the event of a security incident involving unauthorised exposure of personal information, we undertake: • To notify affected users within 72 hours of discovery. This is a voluntary commitment by the Company, beyond what Israeli law requires. • To report a severe security incident to the Privacy Protection Authority in accordance with the Privacy Protection Regulations (Information Security), 5777-2017, and to act on its directions, including any direction regarding notification of data subjects. • In respect of information we process on behalf of a user (leads and CRM data), where the user is the database owner and we are a processor on their behalf, to notify that user immediately so that they can meet the duties applying to them. • For visitors and users in the European Union and the United Kingdom, to act also in accordance with Articles 33-34 of the GDPR (notification to the supervisory authority within 72 hours, and notification to the data subject where there is a high risk to their rights). • To provide practical guidance for protecting the user (such as changing passwords and monitoring accounts). • To publish a transparency report once handling of the incident is complete.
10. Information Security
We employ technological and organisational security measures (such as SSL communication encryption, Row-Level Security, and encryption of data at rest) in order to protect the information. However, no system is entirely immune, and we cannot guarantee absolute security.
11. Contact
For any question regarding this privacy policy, you may contact us: Email: support@linxcard.me Phone: 053-3443330