Privacy policy
This policy explains what personal data is collected on the Linda Passion Life website, what it is used for and what rights you have. It follows the EU General Data Protection Regulation (GDPR).
1. Data controller
The controller decides how your data is handled and is who you contact about your rights.
| Name | Lindapassionlife Oy |
|---|---|
| Business ID | 3548423-6 |
| Address | Veitikantie 42-44 a9, 96100 Rovaniemi, Finland |
| [email protected] | |
| Phone | 0400 408 812 |
No separate data protection officer has been appointed, and none is required for operations of this size.
2. What data is collected
2.1 Contact form
When you fill in the contact form, the data collected is what you write into it:
- name
- email address
- phone number (optional)
- your answers about what made you curious, what you want in your life and what this opportunity could make possible for you
- your selections about your life situation, your openness to entrepreneurship and how you would prefer to be contacted
Some of the questions touch on your personal circumstances. Write only as much as you want to, none of the open fields is required. Please do not enter health information or other special categories of personal data; they are not processed here.
2.2 Server logs
The hosting service records technical log data such as your IP address, browser type, the page requested and the time. This happens automatically on every website and is used only to keep the service working and secure.
2.3 Advertising measurement, with your consent only
The site uses the Meta Pixel to see which Facebook and Instagram ads bring people here. If you accept it, the pixel tells Meta about the page load, the page address, your IP address and your browser, and sets an identifying cookie in your browser.
If you accept the pixel and send the contact form, Meta is additionally told that the form was submitted. The content of the form, your name and your contact details are not passed to Meta, they go only to email.
Event data reaches Meta by two routes: directly from your browser through the Meta Pixel, and additionally server-side through Meta's Conversions API. The server-side route is implemented with a Meta Conversions API Gateway, which in turn is implemented through a service called Bïrch. The same event therefore also passes through Bïrch before it reaches Meta. Meta recognises the two copies as one event.
The data passing through the gateway may include your IP address, the page address, the event name and time, technical details about your browser and device, and the Meta identifiers _fbp and, where applicable, _fbc. The content of the form, your name and your contact details are not passed along this route either.
The data may be processed in the systems of Bïrch and of the technical service providers it uses before it is passed to Meta Platforms Ireland Limited. Bïrch uses, among others, Amazon Web Services in its infrastructure.
Neither the pixel nor the server-side route starts before you have given your consent. Nothing at all is sent to Meta or to the gateway before you choose, and if you decline neither is started. You can change your choice at any time on the cookie policy page, which also describes the cookies in detail.
2.4 Watching the video
The video on the page is embedded from YouTube. The embed is not loaded when the page opens, only when you press play. Before that, nothing is requested from YouTube and nothing is written to your browser.
Once you start the video, YouTube learns that it was watched, receives your IP address and browser details, and may store its own identifiers in your browser. The video is embedded from youtube-nocookie.com, which limits cookies used for advertising. If you would rather avoid this, simply don't start the video; everything else on the page works exactly the same.
2.5 What is not collected
There is no other visitor analytics and there are no ad networks. The site sets no cookies beyond the Meta Pixel cookies described above, and the video embed contacts YouTube only once you start the video. See the cookie policy for details.
3. What the data is used for, and on what basis
| Purpose | Legal basis |
|---|---|
| Replying to you and discussing your enquiry | Consent, you send the form on your own initiative. You can withdraw consent at any time. |
| Keeping the site running and secure, and preventing abuse | Legitimate interest, the site has to work and stay safe. |
| Measuring advertising: which Facebook and Instagram ads bring people to the site (Meta Pixel and Conversions API) | Consent, given in the cookie question. You can withdraw it at any time, which stops the tracking. |
The controller does not make automated decisions about you or profile you. Meta, however, also uses the data the pixel collects for its own purposes, including ad targeting and profiling, if you have consented to the pixel. That is described in Meta's privacy policy.
Your data is never sold. Contact form data is never passed on for marketing purposes.
4. How long data is kept
- Contact form data: at most 12 months from our last contact, after which it is deleted. If you ask for deletion sooner, it is deleted on request.
- Server logs: according to the provider's own retention policy, typically days or weeks.
- Meta Pixel cookies:
_fbpthree months,_fbcthree months. Meta decides its own retention. If you withdraw your consent, the cookies are deleted from your browser immediately. - Event data passing through the Conversions API Gateway: retention is decided by Bïrch and Meta in their own systems. The controller does not store this data itself.
- Your cookie choice: in your browser's own storage, until you change it or clear your browser data.
5. Who processes the data
The controller handles the data personally. In addition, the following services act as processors and may not use the data for their own purposes:
| Service | Role |
|---|---|
| Cloudflare, Inc. | Hosting and delivery of the site (Cloudflare Pages). Processes server logs. |
| Resend (Plus Five Five, Inc.) | Delivering form submissions by email. |
Google Ireland Limited (YouTube) is responsible for video playback. It is not a processor either: it decides for itself how it uses the data it collects. This concerns only visitors who start the video — before that, nothing is sent to YouTube.
Meta Platforms Ireland Limited stands in a different position: it is not a processor, because it also uses the data the pixel collects for its own purposes. For the collection and transfer carried out by the pixel, the controller and Meta act as joint controllers; Meta alone is responsible for what it does with the data afterwards. This concerns only visitors who have accepted marketing cookies.
The server-side delivery of events uses a Meta Conversions API Gateway, implemented through the Bïrch service. Marketing-related data may therefore pass through the systems of Bïrch and of the technical service providers it uses, such as Amazon Web Services, before reaching Meta. This too concerns only visitors who have accepted marketing cookies.
The gateway was put in place through Meta's partner network when the Meta data source was set up. The role of Bïrch in the sense of the GDPR, and the contractual arrangements around it, are being clarified, and this policy therefore makes no claims about them. This section will be updated once they are confirmed.
6. Transfers outside the EU
Yes, they happen. Cloudflare is a US company, so server log data may be transferred to the United States. The same applies to the email delivery service Resend, which delivers the contact form messages. If you have accepted marketing cookies, the data collected by the Meta Pixel and the Conversions API is transferred to Meta and its US parent company as well. If you start the video, data collected by YouTube may be transferred to Google's US parent company.
The server-side route also passes through a server located in the United States: the Conversions API Gateway in use receives the events in a data centre on the US west coast, with a second US cloud service configured as a fallback.
The transfers rely on the EU–US Data Privacy Framework and on standard contractual clauses approved by the European Commission.
7. Cookies
The site has one tracking cookie, the Meta Pixel, and it is loaded only with your consent. Nothing is written to your browser before you choose. The typefaces store nothing: they are served from this same site. The exception is the YouTube video: if you start it, YouTube may store its own identifiers in your browser. The cookies, how long they last and how to change your choice are described in the cookie policy.
8. Security
The site runs over an encrypted HTTPS connection. Messages arriving through the form are treated confidentially, and only the controller has access to them. Email accounts are protected with a password and two-factor authentication.
9. Your rights
You have the right to:
- know whether data about you is being processed, and to receive a copy of it
- have inaccurate data corrected
- request that your data be deleted
- restrict or object to processing
- receive the data you provided in a portable format
- withdraw your consent at any time, withdrawal does not affect the lawfulness of processing carried out beforehand
Exercising these rights is free of charge. Send your request to the email address in section 1. You will get a reply within one month at the latest.
If you believe your data has not been handled properly, you can lodge a complaint with the Finnish Data Protection Ombudsman: tietosuoja.fi/en.
10. Changes to this policy
If how the site works changes, this policy is updated and the date at the top changes. Significant changes are announced on the site.
← Back to the home page