{"id":6573,"date":"2026-08-05T11:10:44","date_gmt":"2026-08-05T08:10:44","guid":{"rendered":"https:\/\/uhmu.fi\/uncategorized\/gdpr-privacy-notices-a-guide-for-businesses-in-finland\/"},"modified":"2026-10-12T11:47:06","modified_gmt":"2026-10-12T08:47:06","slug":"privacy-notice","status":"publish","type":"post","link":"https:\/\/uhmu.fi\/en\/data-protection\/privacy-notice\/","title":{"rendered":"GDPR privacy notices: a guide for businesses in Finland"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n
\n

At a glance<\/h2>\n
    \n
  • A privacy notice explains how a business uses personal data. The GDPR requires clear information, but it does not prescribe a document called a \u201cprivacy notice\u201d or require people to accept one.<\/li>\n
  • For each purpose, identify the lawful basis, the data used, recipients, retention criteria and the rights that apply. Keep the explanation specific to what the business actually does.<\/li>\n
  • Give the information when collecting data directly. If data comes from elsewhere, provide it within a reasonable period and generally no later than one month, subject to earlier-contact and other rules.<\/li>\n
  • Businesses of every size have transparency duties. The under-250-person exception in GDPR Article 30 concerns certain internal processing records, not privacy notices.<\/li>\n
  • Publish the notice where people can find it and link to it when collecting data. Update it before introducing a new purpose or other change that affects what people have been told.<\/li>\n<\/ul>\n<\/div>\n\n

    A privacy notice is the explanation a business gives people about its use of their personal data. Customers, employees, job applicants, website visitors and business contacts may all be affected. The GDPR calls this the duty to provide information; a privacy notice is the practical way most organisations meet that duty in a clear, documented form.<\/p>\n

    This guide explains what to include, when to provide it and how to keep it accurate. A generic template cannot establish whether your processing is lawful.<\/p>\n\n

    What a privacy notice does\u2014and does not do<\/h2>\n

    GDPR Articles 12\u201314 require information to be concise, transparent, intelligible, easily accessible, clear and free of charge. The GDPR does not prescribe a document name or standard form. The important question is whether people receive the required information in a usable way.<\/p>\n

    A notice describes processing. It does not create permission to process personal data, and it is not a consent form. Do not make people accept the notice as a condition of contact or service. If consent is the lawful basis for a particular purpose, ask for that consent separately, in a way that meets the GDPR\u2019s consent requirements. Other processing may rely on another lawful basis.<\/p>\n

    The controller generally decides why and how personal data is processed and is responsible for providing the information. A processor handles data on the controller\u2019s behalf and has its own GDPR duties, but does not automatically have the controller\u2019s notice obligation. Roles depend on what each organisation actually does.<\/p>\n

    Information about an individual is personal data even in a business-to-business setting. A named employee\u2019s work email, direct phone number, job title or correspondence may identify that person. A business therefore needs to consider how it informs professional contacts, not only consumers.<\/p>\n\n

    What to include in the notice<\/h2>\n

    Articles 13 and 14 set out the information required for data collected from the person and data obtained elsewhere. The lists largely overlap; Article 14 also requires data categories and sources. Explain your own purposes and data flows rather than copying a bare statutory list.<\/p>\n

      \n
    1. Controller and contact details.<\/strong> Give the controller\u2019s name and contact details. Include the representative\u2019s details where a representative has been appointed, and the data protection officer\u2019s details where one is required or appointed.<\/li>\n
    2. Purpose and lawful basis for each use.<\/strong> Explain each purpose in concrete terms, such as delivering orders, managing customer accounts, recruitment or sending a newsletter. Match every purpose to its own lawful basis under Article 6. A contract basis does not automatically cover every use of a corporate contact\u2019s data just because that person works for a customer or supplier. Where the basis is legitimate interests, state the interests pursued. If a purpose relies on consent, say so.<\/li>\n
    3. Data categories and sources.<\/strong> Describe the kinds of data involved, such as contact details, order history or billing information. When you obtain data indirectly, identify its source and, where relevant, whether it came from a publicly accessible source. For Article 14 notices, explain the categories of data received.<\/li>\n
    4. Recipients.<\/strong> Name recipients where practicable, or describe categories such as payment providers, delivery companies or IT service providers. Distinguish processors from organisations that receive data for their own purposes where relevant.<\/li>\n
    5. Transfers outside the EEA.<\/strong> Explain intended transfers to countries outside the European Economic Area or to international organisations, including whether a European Commission adequacy decision exists. Where you rely on safeguards, such as standard contractual clauses, describe them and explain how people can obtain a copy or where they are available. The notice must reflect the transfer arrangement actually used.<\/li>\n
    6. Retention period or criteria.<\/strong> State how long data is kept, or the criteria used to decide. Avoid a bare promise to keep data only \u201cas long as necessary\u201d: explain what necessity means in practice, such as a statutory recordkeeping period or the duration of an account followed by a defined review or deletion process.<\/li>\n
    7. Rights and how to exercise them.<\/strong> Explain applicable rights, including access, rectification, erasure, restriction, objection and portability where the conditions are met. Tell people they may complain to a supervisory authority. If processing relies on consent, explain how it can be withdrawn and that withdrawal does not affect earlier lawful processing.<\/li>\n
    8. Whether providing data is required.<\/strong> When collecting data directly, explain whether providing it is a statutory or contractual requirement, or necessary to enter a contract. State whether the person is obliged to provide it and the possible consequences of not doing so. This helps distinguish optional information from what is needed for the requested service.<\/li>\n
    9. Automated decisions.<\/strong> If Article 22 applies to a solely automated decision with legal or similarly significant effects, provide meaningful information about the logic involved and the significance and envisaged consequences for the person. A vague statement that \u201cautomated processing may occur\u201d is not enough.<\/li>\n<\/ol>\n\n

      When and where to provide it<\/h2>\n

      When you collect data directly, provide Article 13 information at that time. A prominent, accessible link can form part of a layered explanation. Place it beside the relevant contact form, application, sign-up or checkout so people can open the information before submitting data.<\/p>\n

      If you obtain personal data from elsewhere, Article 14 generally requires information within a reasonable period and no later than one month after obtaining the data. If you use the data to contact the person sooner, provide the information at the latest when you first communicate with them. If you plan to disclose it to another recipient, inform the person no later than the first disclosure. Article 14 has defined exceptions, including where the person already has the information or providing it proves impossible or would involve disproportionate effort in specified circumstances. Do not assume that posting a notice on a website alone automatically meets the duty.<\/p>\n

      A short collection-stage message can identify the controller, immediate purpose and link to the full notice. Keep the full notice accessible from relevant pages, commonly in the website footer, and link it again where people submit information.<\/p>\n

      Use language your audience can understand. English alone may not be sufficient for people served in Finnish or Swedish; consider who uses the service and in what language.<\/p>\n\n

      Keep the notice tied to real practices<\/h2>\n

      Check the basis against the actual activity. For example, processing a consumer\u2019s delivery address may be necessary to fulfil their order, while retaining invoices may serve a legal recordkeeping obligation. Legitimate interests require a separate assessment of necessity and the balance with the individual\u2019s interests and rights; merely naming that basis in the notice is not enough.<\/p>\n

      Assess separate requirements too. Non-essential cookies and similar tracking technologies generally require consent; mentioning them in the notice does not replace it. Keep consent choices separate from the information explaining how data is used.<\/p>\n

      Where the Article 21 right to object applies, bring it explicitly to the person\u2019s attention, clearly and separately from other information, by the first communication at the latest. If someone objects to processing for direct marketing, stop using their data for that purpose.<\/p>\n

      Workforce data is also subject to Finnish rules. Employers should check the Act on the Protection of Privacy in Working Life alongside the GDPR. A separate employee notice can explain recruitment, payroll, time recording and employment records more clearly than a general customer notice.<\/p>\n

      The Article 30 record of processing activities is an internal compliance document, not normally published. The under-250-person exception is narrow: it does not cover processing that is not occasional, is likely to result in a risk to individuals\u2019 rights and freedoms, or involves special-category or criminal-offence data. Articles 12\u201314 have no general small-business exemption.<\/p>\n\n

      Review and update the information<\/h2>\n

      There is no universal annual deadline. Update the notice when a relevant change makes it inaccurate or incomplete, such as a new purpose, system, recipient, source, transfer or retention approach. Tell people about a new purpose and relevant additional information before further processing begins.<\/p>\n

      Keep dated versions and compare the notice with actual forms, systems, supplier arrangements and internal processing records. Map the data and purposes, identify the controller and recipients, choose a lawful basis for each purpose, set retention criteria, then write for the people concerned.<\/p>\n\n

      Frequently asked questions<\/h2>\n
      \n
      Does every business need a privacy notice?<\/summary>

      Where the GDPR applies, controllers must provide the required information unless a specific exception applies. There is no general exemption based on business size. The narrow Article 30 exception for some small organisations does not remove transparency duties.<\/p><\/div><\/details>\n

      Do customers have to consent to the privacy notice?<\/summary>

      No. A privacy notice explains processing; it is not itself a request for consent. Choose a lawful basis for each purpose. Where consent is the basis, request it separately and make withdrawal possible.<\/p><\/div><\/details>\n

      What is the difference between a privacy notice and a record of processing activities?<\/summary>

      The notice is information for people whose data is processed. The Article 30 record is an internal compliance record describing processing activities, with limited exceptions. One does not replace the other.<\/p><\/div><\/details>\n

      Is a privacy policy in the website footer enough?<\/summary>

      A footer link helps, but for direct collection provide the information at collection and link the notice at the relevant form. For indirectly obtained data, follow Article 14\u2019s timing and exceptions.<\/p><\/div><\/details>\n

      How often should a privacy notice be updated?<\/summary>

      There is no fixed annual interval under the GDPR. Review it when processing changes. If you intend to use data for a new purpose, inform people before that further processing begins.<\/p><\/div><\/details>\n<\/section>\n\n

      If you are preparing a notice, it may help to check it against the business\u2019s actual systems, contracts and data flows. See more about data protection and GDPR services for businesses<\/a>, including data processing agreements<\/a>. Contacting me does not commit you to engaging my services.<\/p>\n\n

      \n

      Sources and further information<\/h2>\n