[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"legale-privacy-en":3},"\u003Ch1 id=\"privacy-policy\" tabindex=\"-1\">Privacy Policy\u003C\u002Fh1>\n\u003Cp>\u003Cstrong>Last updated: 4 novembre 2026\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This policy explains what personal data \u003Cstrong>SincroLead\u003C\u002Fstrong> processes, and how.\nIt is written pursuant to Articles 13 and 14 of Regulation (EU) 2016\u002F679 (GDPR).\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"1.-who-we-are\" tabindex=\"-1\">1. Who we are\u003C\u002Fh2>\n\u003Cp>The data controller is:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>DA_CAMBIARE Srl\u003C\u002Fstrong>\nDA_CAMBIARE — via, numero, CAP, città, Italy\nVAT number DA_CAMBIARE\nEmail: \u003Ca href=\"mailto:contact@sincrolead.it\">contact@sincrolead.it\u003C\u002Fa>\nCertified email (PEC): pec@DA-CAMBIARE.example\u003C\u002Fp>\n\u003Cp>SincroLead is a subscription service (SaaS) available at \u003Ccode>app.sincrolead.it\u003C\u002Fcode>.\nBusinesses use it to collect the contacts generated by their own Facebook Lead Ads forms\nand to assign them to their own sales agents.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"2.-two-different-kinds-of-processing%2C-two-different-roles\" tabindex=\"-1\">2. Two different kinds of processing, two different roles\u003C\u002Fh2>\n\u003Cp>⚠️ \u003Cstrong>This is the part that matters most — read it even if you skip the rest.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>SincroLead processes two categories of data, under different rules.\u003C\u002Fp>\n\u003Ch3 id=\"2.1-data-of-the-people-who-use-the-app-%E2%80%94-we-are-the-controller\" tabindex=\"-1\">2.1 Data of the people who use the app — we are the \u003Cstrong>controller\u003C\u002Fstrong>\u003C\u002Fh3>\n\u003Cp>The data of people who log into SincroLead: the administrator of the client business and\nits agents. We decide the purposes and means, so we are the \u003Cstrong>data controller\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch3 id=\"2.2-lead-data-%E2%80%94-we-are-the-processor\" tabindex=\"-1\">2.2 Lead data — we are the \u003Cstrong>processor\u003C\u002Fstrong>\u003C\u002Fh3>\n\u003Cp>The data of people who fill in a lead form on a client business's Facebook Page, or on an\nInstagram account linked to that Page. That\ndata belongs to the relationship between \u003Cstrong>the client business and the person who filled\nin the form\u003C\u002Fstrong>: the client business decides why it is collected and what happens to it.\u003C\u002Fp>\n\u003Cp>We process it \u003Cstrong>only on that business's instructions\u003C\u002Fstrong>, as a \u003Cstrong>data processor\u003C\u002Fstrong> under\nArticle 28 GDPR, on the basis of a written agreement.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What this means in practice if you filled in a form:\u003C\u002Fstrong> if you want to know what data\nwas collected, correct it, or have it deleted, your counterpart is \u003Cstrong>the business that\nran the ad\u003C\u002Fstrong>, not us. If you write to us, we forward your request to that business and\ntell you we have done so — see §9.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"3.-what-data-we-process\" tabindex=\"-1\">3. What data we process\u003C\u002Fh2>\n\u003Ch3 id=\"3.1-account-data-(as-controller-%E2%80%94-%C2%A72.1)\" tabindex=\"-1\">3.1 Account data (as controller — §2.1)\u003C\u002Fh3>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>data\u003C\u002Fth>\n\u003Cth>why\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>First and last name\u003C\u002Ftd>\n\u003Ctd>identify the user inside the app\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Email address\u003C\u002Ftd>\n\u003Ctd>login, service messages, two-factor verification code\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Password\u003C\u002Ftd>\n\u003Ctd>stored only as a \u003Cstrong>hash\u003C\u002Fstrong> (bcrypt): not readable, not even by us\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Role and permissions\u003C\u002Ftd>\n\u003Ctd>determine what the user can see and do\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Business details\u003C\u002Ftd>\n\u003Ctd>company name, VAT number, billing data\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Activity log\u003C\u002Ftd>\n\u003Ctd>who did what and when inside the app, for security and incident reconstruction\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>IP address and session technical data\u003C\u002Ftd>\n\u003Ctd>security, abuse prevention\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Login history\u003C\u002Ftd>\n\u003Ctd>date, outcome, IP address and browser of every login attempt, to spot anyone trying to get into an account. The email or code typed is stored only in unreadable form (\u003Cstrong>hash\u003C\u002Fstrong>). Only the platform operator can view it\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Devices with notifications turned on\u003C\u002Ftd>\n\u003Ctd>only if the user turns them on from their profile: the delivery address the browser assigns to the device, its encryption keys, the browser and last use, to send alerts to the phone or computer. Deleted when the user removes the device, signs out or is deactivated\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Ch3 id=\"3.2-data-received-from-meta-(as-processor-%E2%80%94-%C2%A72.2)\" tabindex=\"-1\">3.2 Data received from Meta (as processor — §2.2)\u003C\u002Fh3>\n\u003Cp>When a client business connects one of its Facebook Pages — and with it any linked\nInstagram account — we receive from Meta:\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>data\u003C\u002Fth>\n\u003Cth>why\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Page access token\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>read that Page's forms and leads, including those submitted on Instagram. \u003Cstrong>Stored encrypted\u003C\u002Fstrong> in the database\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Page ID and name, and those of the linked Instagram account\u003C\u002Ftd>\n\u003Ctd>show the user what they connected\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>The Page's \u003Cstrong>lead forms\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>let the user choose which forms to sync\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>All answers submitted in the form\u003C\u002Fstrong>: name, email, phone and every custom question\u003C\u002Ftd>\n\u003Ctd>this is the lead itself — the service exists for this\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Advertising context: campaign, ad set, ad, and whether the form was submitted on Facebook or Instagram\u003C\u002Ftd>\n\u003Ctd>show the business which campaign and which channel produced the contact\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Submission date and time\u003C\u002Ftd>\n\u003Ctd>ordering, and measuring response times\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>We do not receive and do not request: your posts, your messages, your friend list, or\nyour payment details on Meta.\u003C\u002Fp>\n\u003Ch3 id=\"3.3-data-sent-to-us-by-the-client-business's-other-systems-(as-processor-%E2%80%94-%C2%A72.2)\" tabindex=\"-1\">3.3 Data sent to us by the client business's other systems (as processor — §2.2)\u003C\u002Fh3>\n\u003Cp>A client business may also connect sources other than Meta. In particular it can connect\nits own \u003Cstrong>Google Ads lead forms\u003C\u002Fstrong>, which deliver the data to us directly; and it can send\nus contacts from other systems — its website forms, an industry portal, its existing\nsoftware — through our application programming interface (API). It can also \u003Cstrong>upload a\nlist of contacts from a file\u003C\u002Fstrong> (Excel or CSV) or \u003Cstrong>enter them by hand\u003C\u002Fstrong>: in that case it\ndeclares that it has the right to contact those people, and consent to marketing messages\nis not recorded unless the file states it explicitly. The uploaded file is deleted once the\nimport is finished.\u003C\u002Fp>\n\u003Cp>In that case \u003Cstrong>the client business decides what to send us\u003C\u002Fstrong>: typically name, email, phone\nand the answers to the form it published. We process that data exactly as we process data\narriving from Meta: \u003Cstrong>only on that business's instructions\u003C\u002Fstrong>, as a processor, and never for\npurposes of our own.\u003C\u002Fp>\n\u003Cp>⚠️ For the person who filled in that form, the counterpart remains \u003Cstrong>the business that\npublished it\u003C\u002Fstrong> — as set out in §2.2.\u003C\u002Fp>\n\u003Ch3 id=\"3.4-what-we-do-not-do\" tabindex=\"-1\">3.4 What we do not do\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>We do not sell data to anyone.\u003C\u002Fli>\n\u003Cli>We do not use a client's leads for our own purposes, for profiling, or to train\nartificial intelligence models.\u003C\u002Fli>\n\u003Cli>We do not pool data across client businesses: each business sees \u003Cstrong>only\u003C\u002Fstrong> its own, and\nthat separation is enforced by the database, not merely promised.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2 id=\"4.-purposes-and-legal-bases\" tabindex=\"-1\">4. Purposes and legal bases\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>purpose\u003C\u002Fth>\n\u003Cth>legal basis\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Providing the service to the subscriber\u003C\u002Ftd>\n\u003Ctd>performance of a contract (Art. 6(1)(b))\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Processing leads on behalf of the client business\u003C\u002Ftd>\n\u003Ctd>our contract with the client business; for the person who filled in the form, the basis is the one declared \u003Cstrong>by that business\u003C\u002Fstrong> in its own privacy notice\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Security, activity log, abuse prevention\u003C\u002Ftd>\n\u003Ctd>legitimate interest (Art. 6(1)(f))\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Invoicing and accounting obligations\u003C\u002Ftd>\n\u003Ctd>legal obligation (Art. 6(1)(c))\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Service messages (technical notices, changes to terms)\u003C\u002Ftd>\n\u003Ctd>performance of a contract\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Chr>\n\u003Ch2 id=\"5.-who-else-sees-this-data\" tabindex=\"-1\">5. Who else sees this data\u003C\u002Fh2>\n\u003Cp>Nobody, except the parties listed below, who act as \u003Cstrong>processors\u003C\u002Fstrong> on our behalf:\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>party\u003C\u002Fth>\n\u003Cth>role\u003C\u002Fth>\n\u003Cth>where\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Meta Platforms Ireland Ltd.\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>the source of the leads\u003C\u002Ftd>\n\u003Ctd>EU \u002F USA\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Hetzner Online GmbH\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>hosts the application servers and the database\u003C\u002Ftd>\n\u003Ctd>Germania\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Email provider\u003C\u002Ftd>\n\u003Ctd>delivers service emails: verification, login codes, technical alerts, and the notice sent to an agent when a contact is assigned to them — ⚠️ that notice carries the person's \u003Cstrong>name\u003C\u002Fstrong>, never their email address or phone number\u003C\u002Ftd>\n\u003Ctd>EU\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Browser notification service (Google for Chrome and Android, Apple for Safari and iPhone, Mozilla for Firefox)\u003C\u002Ftd>\n\u003Ctd>delivers notifications to the device of whoever turned them on. The text travels \u003Cstrong>encrypted\u003C\u002Fstrong> and the service cannot read it: it carries the contact's \u003Cstrong>name\u003C\u002Fstrong> (can be turned off in the profile), never email or phone\u003C\u002Ftd>\n\u003Ctd>EU \u002F USA\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Ch3 id=\"access-by-the-provider-to-client-data\" tabindex=\"-1\">Access by the provider to client data\u003C\u002Fh3>\n\u003Cp>DA_CAMBIARE Srl staff access the data only for support and maintenance and are bound by\nconfidentiality. They can do so in two ways, both reserved to the platform administrators,\nwith two-factor authentication required:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Viewing\u003C\u002Fstrong>: from the platform panel they can \u003Cem>read\u003C\u002Fem> the leads, users, agent performance,\nforms and connections of client businesses, without being able to change, export or use\nthem to contact anyone. Every lead search and every lead record opened is kept in the\nclient business's activity log: who, when, which business, which lead.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Access to the business's account ("Log in as")\u003C\u002Fstrong>: to fix a reported problem, they can use\nthe app with the account of one of the business's users, \u003Cstrong>stating the reason\u003C\u002Fstrong>, for \u003Cstrong>at\nmost 60 minutes\u003C\u002Fstrong>. During that time they cannot change password, email, second factor,\nusers or roles, create tokens, or connect and disconnect social accounts. The start and end\nof the access, with the reason, and everything done are kept in the activity log, with\ntheir name next to the user's.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>We disclose data to an authority only where compelled by a lawful request.\u003C\u002Fp>\n\u003Ch3 id=\"transfers-outside-the-european-union\" tabindex=\"-1\">Transfers outside the European Union\u003C\u002Fh3>\n\u003Cp>Data is stored \u003Cstrong>in Germania\u003C\u002Fstrong>. Meta may also process data in the United States;\nthat transfer relies on the safeguards required by Chapter V GDPR (Standard Contractual\nClauses and, where applicable, the EU-US Data Privacy Framework).\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"6.-how-long-we-keep-it\" tabindex=\"-1\">6. How long we keep it\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>data\u003C\u002Fth>\n\u003Cth>how long\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Account data\u003C\u002Ftd>\n\u003Ctd>for the life of the subscription, then \u003Cstrong>90 days\u003C\u002Fstrong> for disputes and second thoughts\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Leads\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>per the client business's instructions, and in any case no longer than 90 days after the contract ends\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Activity log\u003C\u002Ftd>\n\u003Ctd>24 months, to allow a security incident to be reconstructed\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Login history\u003C\u002Ftd>\n\u003Ctd>12 months, then deleted automatically\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Technical log of messages received from Meta\u003C\u002Ftd>\n\u003Ctd>90 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Accounting records\u003C\u002Ftd>\n\u003Ctd>10 years, as required by law\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Sign-ups never confirmed by email\u003C\u002Ftd>\n\u003Ctd>deleted automatically, with no intervention\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>⚠️ \u003Cstrong>Transparency note, to be removed once it is no longer true\u003C\u002Fstrong>: today, periodic\ndeletion of leads is \u003Cstrong>not automated\u003C\u002Fstrong>. A request about a single lead is handled by the\nclient business from the app (§9); other requests are handled manually by our staff within\nthe timescales set out in §9.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"7.-how-we-protect-it\" tabindex=\"-1\">7. How we protect it\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>All traffic encrypted in transit (HTTPS).\u003C\u002Fli>\n\u003Cli>Passwords stored as hashes, never in clear text.\u003C\u002Fli>\n\u003Cli>Facebook Page access tokens are \u003Cstrong>encrypted in the database\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Two-factor verification available for app accounts.\u003C\u002Fli>\n\u003Cli>Separation between client businesses enforced at database level, on every single\nquery, rather than left to the code that renders the page.\u003C\u002Fli>\n\u003Cli>Messages arriving from Meta are verified by cryptographic signature: an unsigned\nmessage is discarded.\u003C\u002Fli>\n\u003Cli>Activity log on every sensitive operation.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No measure is perfect. In the event of a personal data breach we notify the supervisory\nauthority within 72 hours and, where the law requires it, the data subjects as well.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"8.-cookies\" tabindex=\"-1\">8. Cookies\u003C\u002Fh2>\n\u003Cp>SincroLead is a private, login-only business application: it uses \u003Cstrong>no profiling cookies\nand no advertising trackers\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>It uses strictly necessary technical cookies only:\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>cookie\u003C\u002Fth>\n\u003Cth>purpose\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Session cookie\u003C\u002Ftd>\n\u003Ctd>keep you logged in\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>CSRF token\u003C\u002Ftd>\n\u003Ctd>prevent another site from submitting forms in your name\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>These require no consent: without them the service does not work.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"9.-your-rights\" tabindex=\"-1\">9. Your rights\u003C\u002Fh2>\n\u003Cp>You have the right to access your data, have it corrected, have it erased, restrict\nprocessing, receive it in a machine-readable format (portability), object to processing\nbased on legitimate interest, and withdraw consent you have given.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Who to write to:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>if you are…\u003C\u002Fth>\n\u003Cth>write to…\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>a user of the app\u003C\u002Ftd>\n\u003Ctd>\u003Ca href=\"mailto:contact@sincrolead.it\">contact@sincrolead.it\u003C\u002Fa>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>a person who \u003Cstrong>filled in a lead form\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>the business that ran the ad\u003C\u002Fstrong>. If you do not know which one, write to \u003Ca href=\"mailto:contact@sincrolead.it\">contact@sincrolead.it\u003C\u002Fa>: we will identify it and forward your request\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>We reply \u003Cstrong>within 30 days\u003C\u002Fstrong>. Step-by-step instructions are on the\n\u003Ca href=\"\u002Fen\u002Flegal\u002Fdata-deletion\">Data Deletion\u003C\u002Fa> page.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Two features of the app are there to answer requests about a lead.\u003C\u002Fstrong> The client\nbusiness (its administrators) can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>export the data of a single lead\u003C\u002Fstrong> — name, contact details, form answers, consent,\nnotes and appointments — as a JSON file (machine-readable) or a CSV file (readable in a\nspreadsheet), to answer an \u003Cstrong>access\u003C\u002Fstrong> or \u003Cstrong>portability\u003C\u002Fstrong> request;\u003C\u002Fli>\n\u003Cli>\u003Cstrong>erase the data of a single lead\u003C\u002Fstrong> on request: name, contact details, answers and the\ntext of notes and appointments are deleted and cannot be recovered. Only an anonymous\nnumber remains, with date, source and status, for the business's statistics.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Both operations are recorded in the \u003Cstrong>activity log\u003C\u002Fstrong>, with who did them and when, but\n\u003Cstrong>without the person's contact details\u003C\u002Fstrong>: the log says "data erased on request", not which.\u003C\u002Fp>\n\u003Cp>You may also lodge a \u003Cstrong>complaint with the Italian Data Protection Authority\u003C\u002Fstrong>\n(\u003Ca href=\"http:\u002F\u002Fwww.garanteprivacy.it\">www.garanteprivacy.it\u003C\u002Fa>) or with the authority of the country where you live.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"10.-changes-to-this-policy\" tabindex=\"-1\">10. Changes to this policy\u003C\u002Fh2>\n\u003Cp>If we change something substantial, we notify registered users by email and update the\ndate at the top of this page. Previous versions remain available on request.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2 id=\"11.-contact\" tabindex=\"-1\">11. Contact\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>DA_CAMBIARE Srl\u003C\u002Fstrong> — DA_CAMBIARE — via, numero, CAP, città, Italy\nPrivacy requests: \u003Ca href=\"mailto:contact@sincrolead.it\">contact@sincrolead.it\u003C\u002Fa>\nSupport: \u003Ca href=\"mailto:support@sincrolead.it\">support@sincrolead.it\u003C\u002Fa>\u003C\u002Fp>\n",1793793206035]