This notice explains how personal data is processed on the Nettiteeri Oy website (nettiteeri.fi and nettiteeri.com), in the electronic signature and contract archive service at sign.nettiteeri.fi and in the integration service Teeri-Connect (connect.nettiteeri.fi). It is based on Articles 13 and 14 of the EU General Data Protection Regulation ((EU) 2016/679, “GDPR”) and the Finnish Data Protection Act (1050/2018).
Nettiteeri Oy is the controller for data about the use of the website, for enquiries sent to it and for the user accounts of the signing service (company employees who send signature requests and manage the contract archive). In Teeri-Connect it is the controller for the service administrators’ user accounts, for the data of the people who sign customer contracts and for the details of customer companies’ contact persons (section 3).
Signature requests and the contract archive
The signing service is Nettiteeri Oy’s own tool, which it operates. It is used by Nettiteeri Oy and by companies in which its owner is a shareholder and with which Nettiteeri Oy has agreed on its use; it is not offered to anyone else. Each company has its own contract archive. The controller for the personal data in a contract and its signature request is the company in whose name the request is sent and in whose archive the contract is stored. That company’s name is shown in the invitation email, on the signing page and on the certificate page of the completed contract.
Where the controller is a company other than Nettiteeri Oy, Nettiteeri Oy processes the data on that company’s behalf and on its instructions as a processor (Article 28 GDPR). Requests about such a contract are best sent directly to that company; Nettiteeri Oy forwards any requests it receives to the right controller.
A company’s contracts may be divided into units (departments). A user of the company sees only the contracts of the units the company has given them access to, and the company’s managers administer its units and access rights. Nettiteeri Oy’s administrators run the service but see a company’s contracts only if they hold a membership of that company, for example to provide support. Adding and removing such a membership is shown to the company’s managers in the company’s event log.
Nettiteeri Oy (business ID 3331525-2) also uses the service for its own contracts and is their controller. Other companies using the service are not listed in this notice: the controller of each contract is determined as described above.
2. Data processed in the signing service and its sources
A company uses the service to send a contract for electronic signature. Signers sign it through a personal link, and the completed contract is stored in the company’s archive and sent to all parties. Contracts signed elsewhere can also be stored in the archive.
Signers
Name, email address and language.
Signature request details: the contract, the sender, the cover message and the status of the request (sent, not delivered, opened, signed or declined).
Signature: the typed name, the acceptance and its time, or the fact that the signer declined and any reason given.
Identification and verification data: use of the signing link (and, where needed, the download link for the completed contract) and of the one-time code sent by email (for the sender of the signature request, signing in to the service), event timestamps, IP address, browser identifier (user agent) and document hashes (SHA-256).
Data contained in the contract document, such as the parties’ contact details and other information written into the contract.
The service does not collect personal identity codes. If the parties have written one into the contract document, it is processed only as part of the contract and within the limits of section 29 of the Finnish Data Protection Act.
Service users (company employees)
Name, email address, user role and company-specific access rights (the role in each company and the units the user has access to).
Login data: the password as a hash, the two-factor authentication (TOTP) secret and recovery codes in encrypted form, and for the passkeys the user has added, their public keys, names, the authenticator’s model (e.g. Windows Hello) where the passkey states it, and when each was added and last used. A passkey’s private key and the fingerprint, face or PIN that unlocks it never reach the service.
Session data: IP address, browser identifier and time of last activity.
Account management events: the invitation and its acceptance, changes to the name, email address, role and company-specific access rights, deactivation and reactivation, two-factor authentication resets, passkeys added and removed, and contracts and customer companies deleted by an administrator – what changed, who made the change and when.
Company management events: a company’s units, sender addresses, labels and contract templates added, changed or removed, and changes to its email settings (without keys or credentials) – what changed, who made the change and when – and the acceptance of the service’s terms of service and data processing agreement on the company’s behalf: the accepter’s name and email address at the time, when, and which versions. The acceptance is kept with these details for as long as the customer relationship lasts, also after the accepter’s user account is anonymised, and is deleted with the company’s data.
Sign-in and password events: signing in (with the password and a verification code, or with a passkey), a failed sign-in attempt (wrong password or verification code, a refused passkey, or a deactivated account; of repeated attempts, at most one is recorded per minute), use of a recovery code, a request for a password reset link, a password change with the reset link and setting up two-factor authentication – the time, IP address and browser identifier. The password or code entered is never stored, and nothing is stored for an email address that has no user account.
Actions taken in the service, such as signature requests sent and contracts stored in the archive.
Bug reports, suggestions and questions sent with the service’s form: the title and description the user writes, an optional screenshot, and the page address (without the search term), browser identifier and view size. A report is linked to the sender’s user account by the account’s identification number, and the sender’s email address is attached to it only for messages about how the report is handled; no name is attached.
Where the data comes from
The signer’s name and email address and the contract document are provided by the company sending the signature request, which has usually received them from the signer or the organisation the signer represents while preparing the contract. Identification and verification data is generated when the signer uses the signing link. Contracts signed elsewhere (for example, previously in the SignHero service) and their details are added to the archive by the company from its own records. User account data comes from the user and from the administrator or company manager who creates the account, and bug reports from the user. No data is collected from public sources.
3. Purposes, legal bases and retention periods
Sending signature requests and signing the contract
Data
The signer’s name, email address and language, the signature request details and the signature.
Legal basis
Entering into and performing a contract where the signer is a party to it (Article 6(1)(b) GDPR). Where the signer represents a company or other organisation, the controller’s legitimate interest in concluding the contract electronically and verifiably (Article 6(1)(f) GDPR).
Retention
A signed contract is kept as described under “Contract archive”. Data on requests that were left unfinished, cancelled, expired or declined, including their verification data, is deleted 12 months after the request ended (when it was cancelled, declined or expired). In a project contract only the copies left unsigned are deleted; signed copies are kept.
Identifying the signer and verifying the signature
Data
Use of the signing and download links and the one-time code, event timestamps, IP address, browser identifier and document hashes.
Legal basis
The legitimate interest of the controller and the contracting parties in being able to show who signed the contract and when, and that the document has not been altered, and to establish, exercise or defend legal claims (Article 6(1)(f) GDPR).
Retention
Verification data is kept together with the contract. The one-time code is valid only for a short time and cannot be reused. Its hash is deleted after a day, and only the fact that it was sent and confirmed is kept. The hash of an expired download link is deleted within a day.
Contract archive
Data
Signed contracts with their certificate pages, contracts signed elsewhere and imported into the archive, and details of their parties and signatures.
Legal basis
The controller’s legitimate interest in keeping the contracts it has concluded and evidence of them (Article 6(1)(f) GDPR), and the retention obligation under the Finnish Accounting Act (1336/1997) where the contract is part of the accounting records (Article 6(1)(c) GDPR).
Retention
For the duration of the contractual relationship and thereafter for as long as claims based on the contract can be made (Finnish Act on the Statute of Limitations of Debts 728/2003), as a rule 10 years after the relationship ends. A contract that forms part of the accounting records is kept at least as long as the Accounting Act requires, i.e. six years from the end of the year in which the financial period ended. The service does not delete signed or imported contracts automatically, as it cannot know when the contractual relationship ends: the service administrator deletes a contract separately once its retention period is over. The contract is deleted with its files, parties and verification data; the deletion leaves an entry in the user account and company management events that contains neither the contract's title nor the parties' details. When a customer company's agreement for the service ends, the administrator deletes all of the company's data at once: its contracts with their files, parties and verification data, signing requests, units, sender addresses, labels, contract templates, API keys, webhooks, access rights and the company's event log. The deletion leaves an entry in the administrator's management events with the company's name and the numbers of what was deleted, but no contract titles and no parties' details. If the company asks for its contracts in one file before the deletion, the file made on the server is deleted after delivery, or automatically 7 days after it was made.
Sending emails
Invitations and reminders, one-time codes, completed contracts and, if the sender so chooses, notices of a cancelled request are sent by email in the name of the company acting as controller, from the sender address of the unit the signature request was sent from or, if the company uses the service’s own sending, from the service’s address with replies going to the unit’s sender address. Sending involves the recipient’s name, email address and the content of the message, which may have the completed contract attached (or, for a contract too large to attach, a download link). Each message’s identifier from the sending service is stored with the recipient’s address. If a message (an invitation or a reminder, a one-time code or a completed contract) is not delivered or the recipient marks it as spam, Mailgun reports this to the service or, with OxiMailing, the service reads it from OxiMailing’s bounce, block and complaint lists hourly for a week after sending, and the fact and its reason (as given by the sending service or the receiving mail server) are stored with the signature request, so that the sender can check the address, send the message again or reach the recipient another way. The legal basis and retention period are those of the processing the message relates to.
Service user accounts and security
Data
The user’s name, email address, role and access rights, account management events, sign-in and password events, login and session data, and technical logs.
Legal basis
The legitimate interest of Nettiteeri Oy and the companies using the service in admitting only authorised users, protecting contract data and being able to trace afterwards who changed access rights and whether someone tried to get into an account without authorisation, for example by guessing the password or changing it with a reset link (Article 6(1)(f) GDPR). The events are visible to the service’s administrators (admins). Management events concerning a company (memberships, units, sender addresses, email settings, labels, contract templates and contract deletions) are also visible to that company’s managers.
Retention
A user account is kept as long as the user has access to the service. 12 months after the account is closed it is anonymised: the name, email address, password, authentication data (passkeys included) and access rights are deleted, and only the account’s identification number remains, because contracts’ verification data refers to it. The management, sign-in and password events concerning the account are deleted at the same time; in other accounts’ and companies’ events (such as the upkeep of units and contract deletions) the anonymised account is shown as the one who made the change. Sign-in and password events are in any case deleted 12 months after they happened; management events are kept as long as the account. When a customer company's data is deleted after its agreement ends (see “Contract archive”), the accounts of its users who have no access to another company are closed and anonymised at once. A passkey is deleted when the user removes it or when their password or two-factor authentication is reset. Session data is deleted when the session expires, and technical logs are kept for at most 3 months. A user’s name and email address may remain in a contract’s data for the contract’s retention period: as a party and on the finished contract’s certificate page if they signed a contract they sent themselves, and the email address also in the contract’s event history and delivery data as the recipient of the messages sent to them (the finished contract, a notice that a signer declined or that the request expired).
Bug reports and developing the service
Data
The report’s type, title and description, an optional screenshot, the page address, browser identifier and view size, and the sender’s account identification number, a link to the account in the service’s user administration and email address for messages about how the report is handled. A screenshot may show data in the service, such as contracts and their parties; the form lets the user cover it by drawing before sending, and we ask users not to leave unnecessary personal data in the image.
Legal basis
The legitimate interest of Nettiteeri Oy and the companies using the service in fixing the service’s faults, developing it based on users’ feedback and telling the sender how their report is being handled (Article 6(1)(f) GDPR).
Retention
Reports are stored in Nettiteeri Oy’s own ticket system, which runs in the same DigitalOcean hosting environment as the signing service (section 5); only the people at Nettiteeri Oy who maintain the service see them. No name of the sender is stored with a report. The email address is passed to the ticket system only so that the sender hears how their report is handled: a message is sent when the report is taken up, when a change is ready for testing, when the report has been handled (fixed or rejected) and when a reply visible to the sender is added. The address is deleted from the ticket system once the report has been handled. Otherwise a report links to a person only through the signing service’s own user data, so the link lasts as long as the user account’s data (see “Service user accounts and security”), and once the account is anonymised a handled report can no longer be linked to anyone. The sender sees their own reports, their status and the replies marked visible to them on the service’s Oma tili (My account) page. The report’s content (text, screenshot, page address, browser identifier and view size) is kept as long as it is needed to maintain and develop the service.
Using the website
Data
Server log data, such as IP address, time, requested address and browser identifier.
Legal basis
Legitimate interest in maintaining the website and investigating faults and misuse (Article 6(1)(f) GDPR).
Retention
At most 3 months.
Enquiries
Data
The name and contact details of the person getting in touch and the content of the message.
Legal basis
Legitimate interest in responding to enquiries (Article 6(1)(f) GDPR) or steps taken at the person’s request prior to entering into a contract (Article 6(1)(b) GDPR).
Retention
As long as handling the matter requires. If the enquiry leads to a customer relationship, the data is kept for its duration and thereafter as long as the Accounting Act requires.
The Teeri-Connect integration service
Teeri-Connect is Nettiteeri Oy’s integration service that moves data between customer companies’ systems, for example from accounting into the customer’s data warehouse or from a customer relationship management (CRM) system to a document generator. Nettiteeri Oy processes the data moved by the pipelines, such as accounting entries and the details of CRM contact persons, as well as the credentials for the customer’s systems and the email address of a credential link’s recipient, on behalf of the customer company as a processor under the data processing agreement made with the customer (Article 28 GDPR). Requests about that data are best addressed to the customer company. Nettiteeri Oy is the controller for the data described below. The service runs on the same server as the signing service (section 5).
Teeri-Connect: people who sign customer contracts
Data
The name, email address and language of the person who signs the service agreement and the data processing agreement on behalf of the customer company, the contract documents (PDF), which also contain the contact persons named in the contract, and whether the contract has been sent and signed. The data comes from the customer company. The contract is sent for signature through the signing service, where the data is processed as described in sections 2 and 3.
Legal basis
Nettiteeri Oy’s legitimate interest in making the contract with the customer company and keeping it as evidence (Article 6(1)(f) GDPR).
Retention
For the duration of the customer relationship. The signer’s name and email address are erased 3 years after the customer relationship ends, and the contracts and their files are deleted 10 years after it ends.
The name, role and email address of the customer company’s contact persons, and which of them Nettiteeri Oy notifies of disturbances. The data comes from the customer company, and Nettiteeri Oy’s staff enter it in the service.
Legal basis
Nettiteeri Oy’s legitimate interest in managing the customer relationship: notifying the customer of disturbances under the service agreement, asking the customer for credentials to its systems and otherwise keeping in contact with the customer (Article 6(1)(f) GDPR). Disturbances are notified by Nettiteeri Oy’s staff; the service sends no automatic alerts to contact persons.
Retention
For the duration of the customer relationship. The contact persons’ details are deleted 3 years after the customer relationship ends.
Teeri-Connect: administrators’ user accounts and security
Data
Only Nettiteeri Oy’s staff use the service. Name and email address, password as a hash, the secret and recovery codes for two-factor authentication (TOTP) in encrypted form, the public keys and names of passkeys and when each was last used, session data (IP address, browser identifier and time of last activity) and an event log: sign-ins and failed sign-in attempts, authentication changes and administrative actions (what was changed and which fields, not the fields’ values) with their time, IP address and browser identifier.
Legal basis
Nettiteeri Oy’s legitimate interest in letting only authorised people into the service, protecting customers’ data and being able to establish afterwards who did what and whether anyone has tried to access an account without authorisation (Article 6(1)(f) GDPR).
Retention
A user account is kept for as long as the person has a role in the service. The service has no function for deleting an account; the account is deleted manually when the role ends, and its passkeys and events are deleted with it. The event log is in any case deleted 12 months after each event. A session expires after 120 minutes of inactivity. The application’s error log, which may contain extracts of the data processed, is deleted after 14 days.
Teeri-Connect’s database is backed up to the server every night. These backups are kept for at most 12 months, and the server is also backed up weekly within DigitalOcean’s service (see “Backups”). Data deleted from Teeri-Connect may therefore remain in backups for at most 12 months and 4 weeks.
Backups
The signing service’s database is backed up daily and the backups are kept on the server. In addition, each backup is encrypted on the server and the encrypted copy is transferred to a storage service of Hetzner Online GmbH whose data centre is in Helsinki, Finland (section 5). Hetzner has no encryption key and no access to the backups’ contents. Database backups are kept for at most 12 months, and a copy deleted from Hetzner remains in the storage service’s daily snapshots for at most a further 10 days. In addition, the whole server, including the encrypted contract documents and the database backups kept on the server, is backed up weekly within DigitalOcean’s service, and each of these backups is kept for 4 weeks (section 5). Data deleted from the service may therefore remain in backups for at most 12 months and 4 weeks, contract documents (PDF files) for at most 4 weeks. Backups are used only to restore the service after a failure. See section 6.
4. Cookies and third-party content
The website itself uses no cookies and no analytics or advertising tools. The Spotify players on the home page are loaded from Spotify’s servers only when you click the load button shown in place of the player. When a player loads, Spotify may store cookies on your device and receives data such as your IP address and browser details. Spotify processes this data as an independent controller under its own privacy policy.
Loading the players is based on your consent (section 205 of the Finnish Act on Electronic Communications Services 917/2014 and Article 6(1)(a) GDPR).
When you load the players, the website stores your choice in your browser’s local storage (localStorage), so that the players load straight away on later visits as well. What is stored is only a note of your permission (named “nettiteeri.spotifyConsent”); it contains no identifier, stays in your browser and is not sent to us or to third parties. Nothing is stored before you ask for the players. The note is strictly necessary to provide the service you have explicitly requested, the players without being asked again, so it does not require separate consent (section 205(2)).
You can withdraw your consent at any time as easily as you gave it: the player sections on the home page and the button below offer Block Spotify players. Withdrawing deletes the note, and the players are no longer loaded until you ask again. The note is also deleted when you clear the site’s data in your browser. Spotify cookies already stored on your device can be deleted in your browser settings.
Spotify players are not loaded in this browser until you ask.
The signing service (sign.nettiteeri.fi) uses only cookies that are strictly necessary for it to work, such as session and security cookies, which do not require consent (section 205(2)).
5. Recipients and processors
The other parties to the contract. The completed contract with its certificate page is sent to all parties to the contract. The certificate page shows each signer’s name, email address, time of signing and method of identification, and the document hashes. Where a contract consists of several documents, the certificate page of each document also shows the names and hashes of all the contract’s documents. Where the same contract is signed separately with several people (for example, a project agreement), each gets their own copy and the signers do not see each other’s details.
The email sending service sends invitations and reminders, one-time codes, completed contracts and cancellation notices as a processor. Each company chooses its sending service: the service’s own Mailgun account (Mailgun Technologies, Inc., Sinch group, EU region), the company’s own Mailgun account, for which the company chooses Mailgun’s EU or US region, or the company’s own OxiMailing account (Oxemis, France). In the EU region, Mailgun’s messages are stored in the EU. See section 6.
The requesting company’s own system. If the company sends signature requests from its own system (for example, its ERP) through the service’s API, that system can read the state of the requests it sent, the signers’ names and email addresses, and each signer’s answer and when it was given. The service may also notify that system of changes in a request; a notification contains only the request’s and contract’s identifiers, the company’s own reference and the status. Notification delivery records are deleted after 30 days. The company is the controller of this data too.
Email service for system messages. Invitations, password reset messages and messages about how bug reports are handled are sent to service users through a processor: Mailgun Technologies, Inc. (Sinch), EU region. See section 6.
The backup storage service Hetzner Online GmbH (Industriestr. 25, 91710 Gunzenhausen, Germany) stores, as a processor, the encrypted backups of the signing service’s database in its data centre in Helsinki, Finland. The data stays in the EU and the EEA. Hetzner has no encryption key and no access to the backups’ contents (section 3).
The hosting provider DigitalOcean, LLC provides, as a processor, the servers on which the website, the signing service and Teeri-Connect run. The servers are located in Germany (Frankfurt, EU). The servers are backed up weekly within DigitalOcean’s service, and each backup is kept for 4 weeks in the same datacenter as the servers. See section 6.
Nettiteeri Oy processes other companies’ contract data on their behalf as the operator of the service (see section 1). Its administrators see a company’s contracts only as members of that company.
Authorities, where the law requires data to be disclosed.
Data is not sold or disclosed for marketing.
6. Transfers outside the EU and the EEA
Mailgun is a service of Mailgun Technologies, Inc., a US company in the Sinch group. The service’s own Mailgun account uses the EU region. If a company uses Mailgun’s US region on its own account, messages and delivery data are stored in the United States. In the EU region, too, data may be processed by the group’s US companies to provide the service. These transfers are based on the European Commission’s standard contractual clauses (Implementing Decision (EU) 2021/914), which are part of Mailgun’s data processing agreement.
The hosting provider DigitalOcean, LLC is a US company, although the servers are located in the EU (section 5). To the extent DigitalOcean processes data outside the EU and the EEA, its data processing agreement bases the transfer on DigitalOcean’s certification under the EU–U.S. Data Privacy Framework. If the framework is declared invalid or the certification is not renewed, transfers are based on the European Commission’s standard contractual clauses (Implementing Decision (EU) 2021/914), which are part of the same agreement.
The encrypted backups of the signing service’s database are stored in Hetzner Online GmbH’s data centre in Helsinki, Finland, and are not transferred outside the EU and the EEA (sections 3 and 5).
Spotify may transfer data outside the EU under its own privacy policy.
7. Your rights
Under the GDPR, you have the right to
know whether your data is processed and access it (Article 15)
have inaccurate data rectified (Article 16)
have your data erased (Article 17); this does not apply to data needed to comply with a legal obligation or to establish, exercise or defend legal claims, such as the verification data of a signed contract during its retention period
have processing restricted (Article 18)
object, on grounds relating to your particular situation, to processing based on legitimate interest (Article 21)
receive the data you have provided in a machine-readable format and transmit it to another controller where processing is based on a contract or consent and carried out by automated means (Article 20)
withdraw your consent at any time, without affecting the lawfulness of processing before the withdrawal (Article 7(3)).
Send your request to the controller (section 1). Requests about a contract are best sent to the company in whose name the signature request was sent. Requests are answered without undue delay and at the latest within one month (Article 12). Your identity may need to be verified before data is disclosed.
If you consider that the processing of your data infringes data protection law, you can lodge a complaint with the supervisory authority, which in Finland is the Data Protection Ombudsman (Article 77 GDPR, section 8 of the Data Protection Act):
Supervisory authority
Office of the Data Protection Ombudsman (Tietosuojavaltuutetun toimisto)
Providing the data is not a statutory requirement. However, your name and email address are necessary for signing a contract in the service: without them, the invitation and the one-time code cannot be sent. If you do not want to sign electronically, you can agree on another way of signing with the company that sent the request. A service user account requires a name, an email address and two-factor authentication. Browsing the website requires no data from you.
9. Automated decision-making
Your data is not used for automated decision-making or profiling that would produce legal effects concerning you or similarly significantly affect you (Article 22).
10. Electronic signature and verification
A signature given in the service is an electronic signature within the meaning of Article 3(10) of the EU eIDAS Regulation ((EU) No 910/2014, as amended by Regulation (EU) 2024/1183), a so-called simple electronic signature. It is not an advanced or qualified electronic signature within the meaning of the Regulation, and it does not rely on strong electronic identification (such as online banking credentials or a mobile certificate).
How the signer is identified
Each signer receives their own unique signing link by email, which expires and stops working once they have signed or declined.
On the signing page, the signer asks for a one-time code to the same email address. The code is valid for 10 minutes and works once, and it must be entered before the contract can be read and signed. Once the code has been confirmed, other signing links sent to the same email address open in the same browser session without a new code for 15 minutes from the confirmation.
The signer reviews the document, types their name and confirms that they accept the contract.
The signer is therefore identified by having access to the email address to which the signature request was sent. The service does not verify the signer’s identity against an official source.
If the sender of the signature request signs as well, they do so without a link or a one-time code, in the service they have signed in to with a password and an authenticator app code (TOTP) or with a passkey, and they confirm their password again when signing. The certificate page of the completed contract shows, for each party, how they were identified, and for the sender also which of the two ways they signed in.
What is recorded
The service records the signing events (opening the link, sending and confirming the one-time code or relying on an earlier confirmation in the same session, opening the document, signing or declining, and downloading the completed contract with a download link) with timestamps, together with the IP address and browser identifier of each event. A SHA-256 hash is calculated from the original document so that it can later be shown that the signed document is the same as the one sent for signature.
The completed contract and the electronic seal
When all parties have signed, a certificate page showing the parties, the signing times and the hashes is appended to the original document. The pages of the original document are not changed. The whole file is sealed with a PDF electronic seal (PAdES) using the certificate of the company that sent the signature request, and the completed contract is emailed to all parties and to the sender of the signature request. If the file is too large to attach to an email, a signer instead receives a personal download link that is valid for 30 days and opens only with a one-time code sent to the same email address; the service stores only a hash of the link. The sender finds the contract in the service’s archive.
The seal makes it possible to check that the PDF version it covers has not been altered after sealing and that the seal was created with the key of that certificate. The seal does not prove the signers’ identity, and it is neither an advanced nor a qualified electronic seal within the meaning of the eIDAS Regulation. If the company uses a certificate it created itself, a PDF reader may show the issuer of the seal as unknown, even though the integrity of the file can be checked. Timestamps are based on the clock of the service’s server; no qualified electronic time stamp is used.
Legal effect
Under Article 25(1) of the eIDAS Regulation, an electronic signature shall not be denied legal effect and admissibility as evidence in legal proceedings solely on the grounds that it is in electronic form or that it does not meet the requirements for qualified electronic signatures. In Finland, most contracts can be concluded in any form. The service is not suitable for legal acts for which the law sets specific formal requirements, such as the sale of real property or a will. The evidential value of a signature depends on the recorded verification data and the circumstances of the case.
Contracts imported into the archive
Contracts signed elsewhere, for example in the SignHero service, are stored in the archive as they are. Verification of their signatures relies on the records of the original service; this service does not add its own verification to them.
11. Changes to this notice
This notice is updated when the service or the law changes. The current version is always on this page, and its date is shown at the top.