Notice under legal review.
HighOnDigital privacy notice
Version 1.3 · 29.09.2026
Version register
| Version | Date | What changes |
|---|---|---|
| 1.3 | 29.09.2026 | On the application pages no measurement starts, not even the anonymous count, until you answer the cookie banner (§3 and §4). Nothing changes on the Social Boost pages. |
| 1.2 | 29.09.2026 | The German text now uses the informal «du», like all our communication. No change of substance. |
| 1.1 | 28.09.2026 | Corrected: duration of the code that recognises returning visitors (6 months from the last visit) and of the opening version seen; recognition in the CRM needs both permissions; correct name of the «Your cookie choices» link; added: the shortened network address, used for one hour against abuse; applications of people selected stay until you ask us to delete them. |
| 1.0 | 28.09.2026 | First single privacy notice for all of HighOnDigital. It replaces the notice of the Social Boost pages (version 0.9 of 28.09.2026), which covered only those pages. Added: job applications on jobs.highondigital.net and the email that confirms an application. Every processing now says where it happens. |
The earlier versions (from 0.1 of 18.09.2026 to 0.9 of 28.09.2026) covered only the Social Boost pages; HighOnDigital keeps their text.
This notice explains which personal data we collect, why, who we share it with, how long we keep it and what rights you have. It applies to every place listed in §2. Where we use a technical word, we explain it in brackets the first time.
What we store in your browser (cookies and similar) is explained in the cookie policy.
1. Controller
The controller (meaning who decides why and how your data is used) is:
HighOnDigital di Peter Ishiodu & Veronica Motta
Via Canova 15, 6900 Lugano, Switzerland
Email: info@highondigital.net · Phone: +41 76 604 11 36
We have not appointed a data protection advisor: it is not mandatory for us.
2. Where this notice applies
| Where | What it is |
|---|---|
| agenzia.highondigital.net | The Social Boost pages: /socialboost (Ticino) and /socialboost-ch (German-speaking Switzerland, in Italian, German and English), the confirmation pages after booking and the reserved price pages you open from the link in our emails |
| jobs.highondigital.net | The pages we use to look for collaborators, one per search (today /video, video editor) |
| n1.highondigital.net | Our CRM (the software in which we keep contacts, bookings and applications). The cookie banner of the pages above, the links in our emails and the page where you choose which emails to receive all come from here |
| The emails we send you | After a booking, after an application, and marketing emails if you asked for them |
| Calendly and Google Meet | The service you use to book the video call and the one we use to hold it. They are our providers (§6): their own notices also apply to what happens on their pages |
3. What we collect, why and on what basis
Each row is one processing (meaning one use of your data). The «Where» column says on which site or at which moment. The «Legal basis» column says why we are allowed to: if you are in the European Union, the General Data Protection Regulation (GDPR), Article 6, applies; if you are in Switzerland, the Federal Act on Data Protection (FADP) applies, which requires the purpose to be recognisable and that you can say no.
Before you answer the cookie banner. Today, on the Social Boost pages, if you have not yet answered the banner, the statistics and advertising tools start straight away, as if you had accepted. The banner still asks for your choice, and from the moment you answer your answer applies (§4).
On the application pages no measurement starts until you answer the banner: no count, not even an anonymous one, no cookie and no data about your visit to our CRM, apart from the technical request that shows you the banner (row «Operation and security»). The answers you write in the questionnaire stay, as always, only in your browser (§3.3). After your answer the rows below apply; in any case there are no Google or Meta tools there.
3.1 On all our pages
| Processing | Where | Data | Why | When | Legal basis |
|---|---|---|---|---|---|
| Operation and security | All pages and the CRM (hosted by Vercel) | IP address, requested page, address parameters, browser, date and time, network region, in the provider's technical logs. Our CRM also uses your shortened network address for one hour, to limit abuse of its public pages | Serving the pages, protecting them from abuse, finding errors | On every request | Legitimate interest (GDPR Art. 6(1)(f)): running and protecting the site |
| Remembering your cookie choice | agenzia and jobs | A cookie with the choice you made in the banner, the text version, the time and a random choice number | Not asking you again and being able to prove what you chose | From when you answer | Legal obligation (point c) and legitimate interest in proving consent (GDPR Art. 7(1)) |
| Register of choices | CRM | Choice number, site, categories accepted or refused, version and language of the text, button pressed, page, date and time. We do not record your IP address or your browser. Your choices about emails are recorded here too (§5) | Keeping proof of consent or refusal, and not asking again anyone who has already said no | When you answer or change your mind | As the row above |
| Our own visit statistics | agenzia and jobs | A random code in the browser (nx_v); pages viewed, clicks and events, referring page, campaign tags | Counting visits and understanding which pages work | On agenzia: straight away, if you have not answered yet; after your answer, only if you chose «Statistics». On jobs: only after your answer, and only if you chose «Statistics» | After your yes: consent (point a). On agenzia, before your answer there is no consent: we inform you here and you can refuse at any time (§4) |
| Anonymous count | agenzia and jobs | Totals per day and per page: page opened, banner shown, answer given, how far people scroll, which parts are seen, where people click, time on the page in bands, phone or computer. No code, no network address, no cookie | Knowing how often the pages are opened and used, including by people who give no permission | On agenzia: always, even if you refuse. On jobs: nothing before your answer; when you answer we count which answer you gave; from the pages you open afterwards, always, even if you refused | Not personal data: the totals lead back to no one |
| Personal recognition in the CRM | agenzia and jobs | The link between the nx_v code and your record in the CRM, if you arrive from a link in one of our emails that recognises you, or when you give us your details by booking or applying | Knowing those visits are yours, so we do not repeat what you already know | On agenzia: straight away, if you have not answered yet; after your answer, only if you chose both «Statistics» and «Marketing and personalisation». On jobs: only after your answer, and only with both permissions | After your yes: consent (point a). On agenzia, before your answer there is no consent: we inform you here and you can refuse at any time (§4) |
| Campaign tags in the address | agenzia and jobs | Labels that say which ad or channel you came from (utm_*, c); on their own they identify no one | Knowing which channel works | Always | Not personal data until linked to a code or a record: that happens with the statistics and, for applications, when you submit (§3.3) |
3.2 Social Boost pages (agenzia.highondigital.net)
| Processing | Where | Data | Why | When | Legal basis |
|---|---|---|---|---|---|
| Visit statistics, Google Analytics 4 | Social Boost pages | Google's cookies (_ga, _ga_*) and the page's events: pages viewed, scrolling, sections reached, videos watched and for how long, clicks on questions and buttons, time on the page, version of the opening seen, campaign tags; our own random code (hod_vid) as identifier | Understanding how the page is used and which opening works better. Google Analytics is linked to our Google Ads account: visits are also used to build lists of visitors, to whom Google can show our ads again | Straight away, if you have not answered yet. After your answer, only with «Statistics» | After your yes: consent (point a). Before your answer: we inform you here and you can refuse (§4) |
| Recognising returning visitors | Social Boost pages | A random code (hod_vid), valid for 6 months from your last visit (its copy in local storage stays until you delete it or withdraw consent), the number of visits, which of our pages you have already seen, the first and last campaign you came from. Never linked to your name or email | Knowing whether you come back and where you first came from | Straight away, if you have not answered yet. After your answer, only with «Statistics» | As the row above |
| Ad measurement, Meta | Social Boost pages; our server | Meta's cookies (_fbp, _fbc), the page address without personal data, the events «visit», «click on the booking button» and «booking made», the Facebook or Instagram click identifier (fbclid). Our server also sends the same event to Meta (Conversions API), with your network address and your type of browser and device | Measuring whether our ads bring bookings, and showing them to people who visited the page | Straight away, if you have not answered yet. After your answer, only if you chose both «Statistics» and «Marketing and personalisation» | As the row above |
| Ad measurement, Google Ads | Social Boost pages | The fact that a booking came from one of our Google ads (without your name); Google Ads cookies (_gcl_au, _gcl_aw) and the click identifier (gclid); visits, for visitor lists; on the confirmation page only, your email in encrypted form (Google turns it into an irreversible code before matching it with its own data) | Measuring whether our Google ads bring bookings, and showing them again to visitors | Straight away, if you have not answered yet: cookies, click identifier and lists, but without your email. After your answer: with «Statistics» only, Google Ads measures without advertising cookies, without lists and without email; everything else only if you also chose «Marketing and personalisation» | As the row above |
| Booking the video call | Calendly | First name, surname, email, phone number (mandatory in the forms) and your other answers; day and time; in the form for German-speaking Switzerland also the language of the call | Setting up the call and sending you the confirmation. The phone number is for calling you back if something goes wrong: we do not use it for advertising messages | When you book | Pre-contractual steps at your request (point b) |
| SMS reminder | Calendly | The number you write in Calendly's SMS field, separate from the phone question; the SMS text with your name and the time | Reminding you of the call | 2 hours before, only if you wrote the number in that field. It comes from a Calendly number; to stop receiving them, reply STOP | Pre-contractual steps (point b); you choose the SMS yourself, in Calendly |
| «grazie» confirmation page | Social Boost pages | Calendly brings you back to our page, passing your name, email and the time in the address. The page shows them only to you (email masked), removes them from the address at once and does not store them. It never sends them to Meta; to Google it sends only the encrypted email, and only if you chose «Marketing and personalisation». The «booking made» event goes to Google and Meta with day of the week, time and campaign tags | Confirming what you booked | When you come back from booking | Pre-contractual steps (point b); legitimate interest for the technical logs (point f) |
| Email after booking | CRM, email | Name, email, day and time; the email text with the personal link to the price page | Confirming the call and sending you, about 15 minutes later, the page with the prices. It is a service email: it does not add you to any list | When you book | Pre-contractual steps (point b) |
| Reminder the day before | CRM, email | Name, email, day and time; the links to join, reschedule or cancel | Reminding you of the call. It does not add you to any list | 24 hours before, only if you booked at least 24 hours ahead. It is not sent if you cancel or if you chose not to receive our emails any more (§5) | Pre-contractual steps (point b) |
| Email after the call | CRM, email | Name, email; the email text | Thanking you and offering the written proposal, if you want it. It does not add you to any list | About 2 hours after the end of the call. It is not sent if only one person or nobody was connected on Google Meet, or if you chose not to receive our emails any more (§5) | Pre-contractual steps (point b) |
| Reading the call on Google Meet | Google Meet, CRM | Whether the meeting started, when it ended and who connected (the name shown and whether it was a Google account, a guest or a phone). We do not read participants' emails, audio, video or chat. In the CRM we note the outcome, the end time and who joined | Knowing whether the call took place before we write to you or call you back | From a few minutes after the planned end, every quarter of an hour, up to 6 hours later | Legitimate interest (point f) |
| Reserved price page | Social Boost pages, CRM | The link in our email carries a random personal code; the page shows your name, the name and town of your business, day and time of the call, if you gave them to us. Every time you open it from the link we note in your record that you opened it, how many times in total and when last; the first time also on the deal. For this count we record neither network address nor software | Showing you the prices with your details and knowing before the call whether you have seen them | Every time you open it from the link, while it is valid (§8). Also if you refused cookies: the code is in the link, not in a cookie | Showing the page: pre-contractual steps (point b). Counting openings: legitimate interest (point f), preparing for the call |
3.3 Job applications (jobs.highondigital.net)
| Processing | Where | Data | Why | When | Legal basis |
|---|---|---|---|---|---|
| Answers saved in your browser | Application pages | The answers you give while filling in, saved only in your browser (local storage). They reach us only when you press «Invia» (Send) | Letting you leave, do the test and pick up where you left off | While you fill in. They are deleted 24 hours after the last save, or when you submit | Needed for the feature you are using: they stay on your device |
| Uploaded CV and video | Application pages, CRM | The CV file and, if you upload it, the video: file name, size, type and content | Assessing your application | As soon as you choose the file we upload it to a temporary area of the CRM, so it stays even if you leave. If you do not submit within 24 hours we delete it; when you submit it moves to the applications | Pre-contractual steps at your request (GDPR point b; FADP Art. 31(2)(a)) |
| Submitted application | CRM | Name and contact details, area, work situation, VAT number (Partita IVA), experience, languages, the other answers of the questionnaire, the portfolio link, the link to your test video with your notes, CV and video, the channel you came from, the page, the referring page and your browser's nx_v code, if present. The application enters the CRM as a «Candidato» (applicant) record, in a flow separate from clients | Assessing the application, watching the test and contacting you for the interview | When you press «Invia» | Pre-contractual steps at your request (GDPR point b; FADP Art. 31(2)(a)) |
| Internal sorting | CRM | A colour (green, yellow or red) calculated from some answers, with the reason | Helping us read first the applications closest to what we are looking for. No one is excluded automatically: a person always decides | When the application arrives | Pre-contractual steps (point b) |
| Application confirmation email | CRM, email | Name, email; the email text | Telling you the application arrived and what happens next. We do not measure whether you open it or which links you click, and it does not add you to any list | Right after you submit | Pre-contractual steps (point b) |
| Applications archive | CRM and private file area | The same application data | Keeping you in mind for this and future searches | From when you send the application | Consent (GDPR point a; FADP Art. 6(6)), given in the box before sending, which you can withdraw at any time |
3.4 Our emails
| Processing | Where | Data | Why | When | Legal basis |
|---|---|---|---|---|---|
| Sending and delivery | CRM, sending provider Resend | Address, subject and text of the email; whether it was delivered, bounced or reported as unwanted | Sending you the emails and knowing whether they arrive | For every email sent from the CRM | The same basis as the email we send you |
| Measuring opens and clicks | Social Boost emails and marketing emails; not the application confirmation email | An invisible image (a «pixel») and links that pass through the CRM before taking you to the page. If you open with images on or click, we record: which email, date and time, which link, the software or device you use and your shortened network address (the last part deleted). The pixel sets no cookie. We do not infer where you open from. We keep automatic opens by software (for example Apple's privacy protection) separate | Knowing whether the email arrives and is read, which links interest you, and preparing for the call. Today we do not use them for a score and they do not trigger automations | On every open or click | We do not ask for consent beforehand: we inform you here and you can say no at any time, wherever you are (§5). In Switzerland: Telecommunications Act Art. 45c; FADP Art. 30 and 31, for our interest in knowing whether service emails arrive |
| Marketing emails | Booking form on Calendly, CRM, email | Name, email; your answer to the box, with date and text of the question | Sending you now and then, in Italian, ideas and examples from our social media work for companies like yours and, sometimes, an offer of ours. If you do not tick the box we send you no marketing emails, and the call and its emails stay the same. The tick concerns only these emails: it does not change your cookie choice | From the moment you tick the box in the booking form. We stop when you withdraw consent from the «Non ricevere più queste email» (Stop receiving these emails) link at the bottom of each one. Your latest choice always applies (§5) | Consent (GDPR point a; in Switzerland Art. 3(1)(o) of the Federal Act against Unfair Competition, UCA) |
What we do not do. We take no automated decisions with legal effects on you: for applications too, a person always decides. We do not ask for sensitive data (for example health, religion, political opinions): you can leave photos and such details out of your CV, we do not need them. We do not sell your data. We do not link the hod_vid code to your name.
Giving your data is optional. If you refuse cookies, the pages still work. To book we need your name and email: without them Calendly cannot set the appointment. To apply we need your CV, portfolio and test: without them we cannot assess the application.
4. The cookie banner: how your choice works
The banner appears on the pages of agenzia.highondigital.net and jobs.highondigital.net. It has three buttons of equal weight, Accept · Refuse · Customise, and two separate permissions. The choice applies to the site where you make it: if you answer on one of the two sites, the banner asks again on the other.
- Statistics («counting visits»): on the Social Boost pages the CRM code, Google Analytics 4, the
hod_vidcode and Google Ads measurement without advertising cookies; on the application pages the CRM code. - Marketing and personalisation («recognising you»): together with «Statistics», personal recognition in the CRM and, on the Social Boost pages, the Meta pixel with sending from our server, Google Ads cookies and lists and the encrypted email of people who book.
If you have not answered yet, today on the Social Boost pages the tools start straight away, as if you had given both permissions (§3). One thing always waits for your yes: after a booking, your encrypted email to Google. On the application pages, instead, no measurement starts until you answer (§3).
If you refuse, even after the tools have started, from that moment and for later visits the page no longer loads Google and Meta tools and deletes the Google Analytics and Meta cookies, the hod_vid code and the CRM code. The refusal is recorded and we do not ask again at every visit. Some Google Ads and Meta cookies and storage remain in the browser, listed in the cookie policy: these pages no longer send them to Google or Meta, and you can delete them in your browser settings. What was already sent before your answer stays where it arrived, with the durations in §8; for what is in our CRM you can ask us to delete it (§9).
You can change your mind at any time from «Your cookie choices» at the bottom of every page. Withdrawing a yes works like a refusal.
5. Our emails: how to say no, and your latest choice
- Do not measure opens and clicks. Write to info@highondigital.net: from then on we write to you only from our mailbox, which does not measure opens and clicks. You can also turn off automatic image loading in your email software: opens are then not counted, clicks on links still are.
- Stop the emails about the call. At the bottom of the email with the prices and of the email after the call, a line explains how: open «Preferenze e tracciamento» (Preferences and tracking) and press «Conferma» (Confirm). From then on you no longer receive the reminder the day before or the email after the call. Calendly's emails and SMS do not depend on this choice: for SMS reply STOP.
- Unsubscribe from marketing emails. At the bottom of each one there is the «Non ricevere più queste email» (Stop receiving these emails) link: you open it and confirm with a button, no password needed.
- Object to direct marketing. You can ask us at any time not to use your data to offer you our services, including by replying to one of our emails.
If you change your mind, your latest choice applies. If you give us different choices at different times (in the cookie banner, in the booking-form box, from the link at the bottom of our emails), the latest always applies, and only to what that choice concerns. For example: if you refused cookies on the page and then, when booking, you tick the marketing email box, we write to you now and then, but cookies stay refused; if you then unsubscribe from the link in an email, we stop; if later you tick the box again, we start again.
6. Who we share data with
Within HighOnDigital, the data is seen by the people who work with the CRM. Outside, these providers receive it:
| Who | Seat | Role | For what | Their notice |
|---|---|---|---|---|
| Vercel Inc. | 440 N Barranca Avenue #4133, Covina, CA 91723, USA | Processor (acts on our behalf) | Hosting the agenzia and jobs pages and the CRM; technical logs | vercel.com/legal/privacy-policy |
| Supabase Pte. Ltd. | 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513. Our data is in the Zurich region, Switzerland | Processor | CRM database and private area for application files (CV and video) | supabase.com/privacy |
| Resend (Plus Five Five, Inc.) | 2261 Market Street #5039, San Francisco, CA 94114, USA. Our emails leave from its infrastructure in the Ireland region (EU) | Processor | Sending the CRM's emails and telling us whether they were delivered, bounced or reported as unwanted. Its open and click counter is off: our CRM measures those | resend.com/legal/privacy-policy |
| Calendly, LLC | 115 E Main St., Ste A1B, Buford, GA 30518, USA | Processor | Booking the call, confirmation email and, if you choose, SMS reminder | calendly.com/legal/privacy-notice |
| Google: Google Ireland Ltd (Gordon House, Barrow Street, Dublin 4, Ireland) and Google LLC (USA) | Ireland / USA | Processor for Google Analytics 4 and for the encrypted email of people who book; independent controller for Google Ads measurement | Visit statistics, ad measurement, visitor lists; video calls on Google Meet and reading who connected | policies.google.com/privacy · business.safety.google/adsservices |
| Meta: Meta Platforms Ireland Ltd (Merrion Road, Dublin 4, Ireland) and Meta Platforms, Inc. (USA) | Ireland / USA | Joint controller for collecting and transmitting pixel events; independent controller for later uses | Ad measurement and campaign audiences, including with the events our server sends to Meta | www.facebook.com/privacy/policy |
7. Data outside Switzerland and the European Union
The CRM, with the applications and their files, has its database in Switzerland (Zurich region). Google, Meta, Calendly, Vercel and Resend have their seat or servers in the United States.
The United States is recognised as a country with adequate protection only for companies certified under the Data Privacy Framework (Federal Council, decision of 14.08.2024 in force since 15.09.2024; European Commission, decision of 10.07.2023).
- Google LLC and Meta Platforms, Inc.: certified under the Swiss-U.S. and EU-U.S. Data Privacy Framework.
- Calendly, LLC and Vercel Inc.: state in their privacy notice that they are certified under the Swiss-U.S. and EU-U.S. Data Privacy Framework.
- Resend and Supabase: the safeguard is the standard contractual clauses approved by the European Commission (decision 2021/914), with the adjustments for transfers from Switzerland written in their data processing agreements.
8. How long we keep data
| Data | Where | How long |
|---|---|---|
Cookie of your cookie choice (nx_c) | Browser | 12 months |
CRM code in the browser (nx_v) | Browser | Up to 180 days, with a fixed expiry that does not renew at every visit |
| Visits, events and sources not linked to your record | CRM | 180 days per single row; after that only daily totals without codes |
| Visits, events and sources linked to your record | CRM | Up to 24 months per single row; after that only totals without codes |
| Opens and clicks of our emails, deliveries, bounces and reports | CRM | Up to 24 months per single row; after that only each email's totals |
| Price page openings in your record | CRM | Up to 24 months |
| Personal link to the price page | CRM | Valid up to 14 days after the call, or 30 days if no call is set; after that the page opens without your details |
| Data of people who book (including phone, answer to the marketing box and call outcome) and the emails we sent them | CRM | Until you ask us to delete them: we do not delete them when a time limit expires. You can ask at any time at info@highondigital.net (§9) |
| Register of choices (cookies, emails, unsubscriptions, marketing consents and their withdrawal) | CRM | For now with no expiry: it proves what you chose, and if you unsubscribe we need it so as not to write to you again |
| Applications (people not selected and the archive) | CRM and private file area | Until you ask us to delete them: we do not delete them when a time limit expires. You can ask at any time at info@highondigital.net (§9) |
| Applications of people selected | CRM | Until you ask us to delete them; invoices and accounting records 10 years, as the law requires (Swiss Code of Obligations, Art. 958f) |
| Uploaded files of an application not submitted | Private file area | 24 hours |
| Answers saved in the browser while applying | Browser | 24 hours after the last save, or until you submit |
hod_vid code and linked data | Browser | The cookie 6 months from the last visit; the local-storage copy until you delete it or withdraw consent |
Version of the opening seen (hod_hero) | Browser | Until you delete it or withdraw consent |
Google Analytics cookies _ga, _ga_* | Browser | 2 years from the last visit |
| Data in Google Analytics 4 | According to the setting of our Google Analytics property (Google allows 2 or 14 months) | |
Google Ads cookies _gcl_au, _gcl_aw | Browser | 90 days |
| Visitor lists in Google Ads | Up to 540 days from the last visit | |
Meta cookies _fbp, _fbc | Browser | 90 days |
| Audience lists in Meta built from our pages' events | Meta | 180 days |
| Google Ads and Meta local storage | Browser | No expiry of their own: they stay until you delete them in your browser |
| Vercel technical logs | Vercel | 1 hour to 30 days, depending on the project's plan |
| Data of people who book, at Calendly | Calendly | For as long as reasonably necessary for its purposes and obligations (Calendly's notice) |
9. Your rights
You can ask at any time for:
- access to the data we hold about you (FADP Art. 25; GDPR Art. 15);
- correction of inaccurate data (FADP Art. 32; GDPR Art. 16);
- deletion (FADP Art. 32; GDPR Art. 17);
- restriction of processing (GDPR Art. 18);
- portability, meaning receiving the data you gave us in a readable format (FADP Art. 28; GDPR Art. 20);
- objection to processing based on legitimate interest (GDPR Art. 21).
Direct marketing. You can object at any time to the use of your data for direct marketing (GDPR Art. 21(2)). If you object, we stop (§5).
Withdrawing consent. You withdraw the banner consent from «Your cookie choices», as easily as you gave it; consent to marketing emails from the «Non ricevere più queste email» link. Withdrawal does not make unlawful what was done before.
How to exercise them: write to info@highondigital.net. We answer within 30 days. We may ask for proof of identity if we cannot attribute the requested data to you with certainty.
Complaint. You can contact the Federal Data Protection and Information Commissioner (FDPIC, Feldeggweg 1, 3003 Bern, www.edoeb.admin.ch). If you are in the European Union, the authority of your country; for Italy the Garante per la protezione dei dati personali (www.garanteprivacy.it).
10. Security
The pages are served only over an encrypted connection (https). Our cookies are marked Secure and SameSite=Lax. The register of choices can only be added to: no one can change or delete it. Visits in the CRM do not record the IP address. The links in our emails and on the price page use long random codes that cannot be guessed. Application files are in a private area: only people who work with the CRM open them, with links that expire after 15 minutes.
11. Changes
When we start processing data in a new way, we add it here and raise the version. The register at the top of this page says what changed and when.