How to make most out of .ID?
How to make most out of .ID?

Support

_____
Getting started
How do I recover my .ID account?
>

First you'll need a smartphone with the .ID app installed.

Open the app and click Recover account option.

You will be asked to enter your recovery phrase which was given to you during the registration. Enter your email address and the words. Once done, click on Continue.

In case you don’t remember your recovery phrase, please contact the support for further assistance.

If the correct recovery phrase has been entered you need to enter new PIN1…

…and PIN2.

All done. You have successfully recovered your account.

What is eIDAS?
>

eIDAS is the most common name for the European Union regulation on electronic identification and trust services for electronic transactions in the European Single Market. It was established in EU Regulation 910/2014 of 23 July 2014.

eIDAS oversees electronic identification and trust services for electronic transactions in the European Union's internal market. It regulates electronic signatures, electronic transactions, involved bodies, and their embedding processes to provide a safe way for users to conduct business online like electronic funds transfer or transactions with public services.

Both the signatory and the recipient can have more convenience and security. Instead of relying on traditional methods, such as mail or facsimile, or appearing in person to submit paper-based documents, they may now perform transactions across borders.

The Regulation provides the regulatory environment for the following important aspects related to electronic transactions:

Advanced electronic signature

An electronic signature is considered advanced if it meets certain requirements:

  • It provides unique identifying information that links it to its signatory.
  • The signatory has sole control of the data used to create the electronic signature.
  • It must be capable of identifying if the data accompanying the message has been tampered with after being signed. If the signed data has changed, the signature is marked invalid.
  • There is a certificate for electronic signature, electronic proof that confirms the identity of the signatory and links the electronic signature validation data to that person.

Advanced electronic signatures can be technically implemented, following the XAdES, PAdES, CAdES or ASiC Baseline Profile (Associated Signature Containers) standard for digital signatures, specified by the ETSI.

Qualified electronic signature
Qualified electronic signature is an advanced electronic signature that is created by a qualified electronic signature creation device based on a qualified certificate for electronic signatures.

Qualified digital certificate for electronic signature is a certificate that attests to a qualified electronic signature's authenticity that has been issued by a qualified trust service provider.

Trust service is an electronic service that creates, validates, and verifies electronic signatures, time stamps, seals, and certificates. Also, a trust service may provide website authentication and preservation of created electronic signatures, certificates, and seals. It is handled by a trust service provider.

What are UETA and ESIGN laws?
>

The Uniform Electronic Transactions Act (UETA) is a United States law which purpose is to harmonize state laws concerning retention of paper records (especially checks) and the validity of electronic signatures.

The Electronic Signatures in Global and National Commerce Act (ESIGN) is a United States federal law passed by the U.S. Congress to facilitate the use of electronic records and electronic signatures in interstate and foreign commerce by ensuring the validity and legal effect of contracts entered into electronically.

UETA gives the legal recognition to electronic signatures, records and contracts in Section 7:

(a) A record or signature may not be denied legal effect or enforceability solely because it is in electronic form.

(b) A contract may not be denied legal effect or enforceability solely because an electronic record was used in its formation.

(c) If a law requires a record to be in writing, an electronic record satisfies the law.

(d) If a law requires a signature, an electronic signature satisfies the law.

UETA also provide the attribution and effect of electronic record and electronic signatures

(a) An electronic record or electronic signature is attributable to a person if it was the act of the person. The act of the person may be shown in any manner, including a showing of the efficacy of any security procedure applied to determine the person to which the electronic record or electronic signature was attributable.

(b) The effect of an electronic record or electronic signature attributed to a person under subsection (a) is determined from the context and surrounding circumstances at the time of its creation, execution, or adoption, including the parties' agreement, if any, and otherwise as provided by law.

ESIGN provides definition for the electronic signatures in Section 106

(5) ELECTRONIC SIGNATURE– The term 'electronic signature' means an electronic sound, symbol, or process, attached to or logically associated with a contract or other record and executed or adopted by a person with the intent to sign the record.

Similar to UETA ESIGN gives a legal recognition to electronic signatures and contracts

(1) a signature, contract, or other record relating to such transaction may not be denied legal effect, validity, or enforceability solely because it is in electronic form; and

(2) a contract relating to such transaction may not be denied legal effect, validity, or enforceability solely because an electronic signature or electronic record was used in its formation.

ESIGN also sets requirements for contract and records retention. ESIGN Section 101(d) provides that if a law requires that a business retain a record of a transaction, the business satisfies the requirement by retaining an electronic record, as long as the record 1) "accurately reflects" the substance of the original record in an unalterable format, 2) is "accessible" to people who are entitled to access it, 3) is "in a form that is capable of being accurately reproduced for later reference, whether by transmission, printing or otherwise", and 4) is retained for the legally required period of time.

What makes .ID signatures ESIGN and UETA compliant?
>

When determining whether an electronic signature is compliant under the ESIGN Act, following requirements must be fulfilled:

Consent to do business electronically

All parties to an agreement or transaction must agree to conduct the transaction using electronic means. The ESIGN Act Section 101 expressly provides that the consumer has affirmatively consented to such use and has not withdrawn such consent.

.ID signatures cannot be created without prior user consent. Then requesting an electronic signature the user will be asked to confirm the signature by entering the PIN-code on their mobile phone. User can easily reject such request by cancelling the PIN-entry.

Intent to sign

Electronic signatures, like regular wet signatures, are valid only if each party intended to sign.

.ID signatures do not happen magically. They are created in the process where each signatory is actually intending to sign the document. Signatories can approve or reject the signature requests easily over the .ID app on their mobile phone.

Association of the signature with the record
An electronic signature must be connected or associated to the document that is being signed by indicating a process by which the signature was created or by creating a graphical or textual statement, which gets added to the signed record.

.ID uses ASiC-E signature container format (.asic) including the XAdES signature standard put down by ETSI to prevent tampering the original signed digital file and link signatures directly with the record.

Users cannot transfer the issued signature to any other document, because they are valid only together with the associated files.

One of the key differentiator of the .ID advanced electronic signatures is that we do not tamper with the original signed document. We do not add the watermarks, or handwritten signature images into the document, as it would make the signatures less secure (anyone can then make a screenshot of your signature and reuse it). Our signatures are mathematically connected to the original documents and only valid if the mathematic hash of the signed file matches with the hash stored in signatures.

Attribution

The electronic signature must be attributable to the person who is signing. The attribution of an electronic signature to a person will be determined based on the context and circumstances under which the document is signed. This can be done by a variety of means, such as documenting the communications and actions of the parties, or preserving an audit trail.

.ID signatures are created with the private key inside .ID app that is mathematically linked to the public key of the signatory, where a standard validation formula can be used to prove its validity.

The public key of .ID digital identity is mathematically tied with the identity verification session and the same identity verification session can be tied with only one .ID account.

.ID digital identity is linked to the device of the .ID holder, while the private keys are also generated and stored only in that device and are protected by PIN-codes that are set by the user.

Record retention

An electronically signed document must be in the form of an electronic record capable of retention by the recipient at the time of receipt. The sender or the information processing system must not inhibit the ability of the recipient to print or store the electronic record for later reference.

.ID uses ASiC-E signature container format (.asic) including the XAdES signature standard put down by ETSI to prevent tampering the original signed digital file and link signatures directly with the record. User can download the signature container any time over secure SSL encryption during the transit.

ASIC-E container content (files and signatures) can be validated any time using open source ASIC viewers.

In addition, user can always host the signed document container on secure .ID platform for previewing and downloading them later.

How do I sign documents on .ID platform?
>
Electronic signature signing

Signing documents or actually any kind of files is a simple process.

After you have signed in, simply click on the Upload & Sign Files.

Step 1. Choose a name for your signed document envelope

First things first - we recommend you to choose a name for your signed document envelope.

Step 2. Add file(s) you want to sign

As second step, you can add documents or files by simply dragging and dropping them into the designated box.

.ID supports all the most common document types, as well other file formats. It’s easy to sign contracts and Excel tables the same time.

There is a size limitation of 30MB per file.

Step 3. Add participants

Once you have the documents uploaded, it’s time to add participants. Simply click Add participants to get started.

Participant is a person who either needs to sign the document(s) or gets viewer access to the document(s).

Once you have all the participants in place, click Preview

Step 4. Sign

Before giving your signature you can double-check everything in Preview mode.

If you spot a mistake you can always click Edit and go back and fix those mistakes.

When you are ready click Sign or wait for other people to sign first.

Once you click Sign, you’ll be prompted a screen both on your desktop as well on mobile app.

In order to Sign you need to enter your PIN2 on your mobile device.

Before you enter your PIN2 make sure the 4 digit control codes are matching. This is required to make sure you are going to sign the correct document.

Once you have entered your PIN2 your document is signed. You can see the time stamp and other relevant information here.

You can also add additional signers and viewers if this is something you want to do.

Document with more than one signature cannot be deleted anymore.

.ID is built in a way to provide a trustless service. As we are using EU signature format the signed file comes in Asic format. This envelope includes the signed documents and files, signature data and identity data. And you are welcome to store it on your own hard drive. It’s still valid and legally binding.

Congratulations!

You have successfully signed your document.

What is ASiC signature format?
>

TL;DR ASiC is a compressed file format that contains the original signed files and digital signatures in one convenient package. It’s the only EU approved format to package files and electronic signatures together.

Associated Signature Containers (ASiC) specifies the use of container structures to bind together one or more signed objects with either advanced electronic signatures or timestamp tokens into one single digital container.

Under the eIDAS regulation , an associated signature container (ASiC) for eIDAS is a data container that is used to hold a group of file objects and digital signatures and/or time assertions that are associated to those objects. This data is stored in the ASiC in a ZIP format.

European Commission Implementing Decision 2015/1506 of 8 September 2015 laid down specifications relating to formats of advanced electronic signatures and advanced seals to be recognised by public sector bodies pursuant to Articles 27 and 37 of the eIDAS-regulation.

Technical specification of ASiCs have been updated and standardized since April 2016 by the European Telecommunications Standards Institute in the standard Associated Signature Containers (ASiC)(ETSI EN 319 162-1 V1.1.1 (2016-04).

What makes .ID signatures eIDAS compliant?
>

According to eIDAS regulation, an advanced electronic signatures need to fulfil four criteria:

It is uniquely linked to the signatory
.ID signatures are created with the private key inside .ID app that is mathematically linked to the public key of the signatory, where a standard validation formula can be used to prove its validity.

It is capable of identifying the signatory
The public key of .ID digital identity is mathematically tied with the identity verification session and the same identity verification session can be tied with only one .ID account.

It is created using electronic signature creation data that the signatory can, with a high level of confidence, use under his sole control
.ID is linked to the device of the .ID holder, while the private keys are also generated and stored only in that device and are protected by PIN-codes that are set by the user.

It is linked to the data signed therewith in such a way that any subsequent change in the data is detectable
.ID uses ASiC-E signature container format (.asic) including the XAdES signature standard put down by ETSI to prevent tampering the original signed digital file.

How can I delete my account?
>

We honor your privacy and therefore you can delete your .ID account at anytime you wish.

Be aware that by deleting your account all your information will be erased and there’s no way to recover it at later stage.

In order to delete your account please follow the following steps.

  1. Go to .ID webapp - https://docs.agrello.io/login and log in using your .ID
Deleting electronic signature app account

2. Click on “My Account”

3. Go to subpage “Account”

4. Click on “Delete Account”

By clicking “Delete” your account with all the data will be deleted.

Please note, that in case you have digitally signed documents between two or more parties, those documents will not be deleted, as other parties still keep their copy.

How to verify my identity?
>

Easiest way to verify your identity is using .ID mobile application.

verifying digital identity

To start the identity verification click on the red button.

As a first step you need fill in your name, country and goverment issued ID type your are going to use for verification. It’s important to enter your name as printed on goverment issued ID.

In case of middle name(s), enter them into the surname field, separated with spaces, as it’s printed on your goverment issued ID

We have partnered up with identity verification company called Veriff to carry out the verification process itself.

During the process you need to take three photos:

  1. Selfie of yourself;
  2. Pictures of your ID;
  3. Selfie together with your ID;

Congratulations!

Verification process is almost done. It usually takes couple of minutes for us to complete the process. On rare cases it can take up to 24hours. If it takes more than that, please contact our support and we’ll look into that.

Common problems:

On some occasions the verification can return with negative response. Most common reason for that include some of the following items:

  • Your ID was outdated or not valid;
  • Pictures taken were not according the guidelines;
  • Pictures taken were out of focus or with a low quality;
  • ID used for verification was not supported.

Please try again by following the guidelines in detail.

How do I create .ID?
>

.ID can be used for verifying, authentication and digital signing. It’s your digital passport in your pocket.

Creating it is easy and takes less than 5 minutes.

  1. Download the app;
  2. Create an account;
  3. Create a back up;
  4. Select your PIN1 & PIN2;

Step 1. Download the app

.ID is supporting both iOS and Android and can be found from App Store and Google Play. We are currently not supporting Huawei appgalery and other marketplaces.

Scan the QR code for shortcut:

For iOS

For Android:

Step 2. Create an account

When creating account, you have two options.

You can either sign up with Google or use your own email address.

When signing up with your own email, you will need to verify your email address.

In case your are here for recovery or you want to connect another device, please check those following articles.

Step 3. Back up your account*

Backing up your account is part of the sign up flow for iOS. For Android, the back up can done later stage from the app settings.

Please back up you security phrase in a secure place, so no-one can access it. More about account recovery can be found from here.

Please note that Agrello doesn’t hold any keys that can possibly allow accessing or restoring your account. This recovery phrase is the only means of restoring your account. You should ideally remember this phrase or store it in a safe place, as it will allow yourself or anybody who knows it to re-create your account and get a full access to it.




Step 4. Select your PIN1 & PIN2

Second step would be selecting yourself a PIN1 & PIN2.

PIN1 is used for authentication as PIN2 is used for signing and confirming actions. Nobody except you should know those.

As for PIN1 you need to select a four digit code.

You have to enter it twice, second time for the confirmation purposes.

On iOS, after you have selected your PIN1 you will be offered an option to use biometrics instead to speed up the authentication process.

PIN2 is needed for signing and confirming actions. As actions confirmed with PIN2 can have legal results it has to be a different number than PIN1.

PIN2 needs to be a six digit number and it has to be entered twice, second time being a confirmation.

On iOS, after you have selected your PIN2 you will be offered an option to use biometrics instead to speed up the signing process.

You're all set!

Congratulations! You have created yourself .ID digital identity with basic verification level. Now you can log into .Doc’s portal and give electronic signatures.

In order to give advanced digital signatures you need to verify your identity. More detailed information can be found from here.

.ID for Google Docs
How do I install .ID for Google Docs?
>

.ID for Google Docs is available on the GSuite marketplace and anyone can install it for free like any other Google Docs add-on.

1. Open Add-on’s menu in your Google Docs editor

2. Search for .ID signatures in marketplace pop-up and click on the .ID signatures banner.

3. Click on the big blue Install button on next screen

4. Click Continue on the next screen

5. Choose the Google account you want to use

6. On the next screen, Google will explain what kind of permissions .ID add-on requires. Click Allow.

7. Congratulations! .ID for Google Docs is now installed and you can find it under the add-on’s menu

How to log in to connect .ID platform and .ID for Google Docs
>

After you have installed .ID for Google Docs, your next step is to connect add-on with your personal account in .ID platform.

1. Click on Sign with .ID menu link under Add-ons menu in your Google Docs

Note: on some occasions, you need to reload the document right after the installation of .ID add-on to see “Sign with .ID” link.

2. Click “Log in“ on the add-on sidebar

3. You are directed to the secure authentication screen of .ID platform. Insert your email and confirm log in in your .ID app

After you have confirmed the login, approve the permissions for Google Docs add-on.

4. Congratulations! Now your .ID add-on is connected securely to .ID platform

This is one-time only process to establish a secure connection between the add-on and .ID platform. This connection is kept alive until you press a small Logout icon in the upper right corner.
It might be a good idea to log out from add-on if you are using a shared computer.

How do I send the document to .ID platform for signing?
>

After you have connected .ID add-on with your personal account on .ID platform you are all set to send Google document for signing on .ID platform.

If you don’t have .ID sidebar open in your Google Docs, click on Sign with .ID menu link to open it up

1. To send a document to .ID platform, click on a Send button on add-on sidebar

When you click on Send button, .ID add-on will take the last version of your Google document and creates a PDF version of it and sends that to .ID platform for signing.

2. Your document is now waiting for you on .ID platform

3. Go to .ID platform to sign the document

Click on the “Go to …” button and .ID platform opens in new window. Log into the .ID platform and you are automatically directed to the signature container of your Google document.

4. Sign the document as usual

Read more about signing from here.

Getting started with .ID for Google Docs
>

.ID for Google Docs is a free add-on that connects your Google Docs editor with .ID digital signatures platform. It allows you to send your Google document to .ID platform for signing and requesting signatures from other people.

Step 1 - Get .ID for yourself

To get started with .ID for Google Docs, you need to have .ID app and account prepared.

Read more

  • How do I create .ID?
how to sign documents in google docs

Step 2 - Prepare a document in Google, install add-on, and send it to .ID platform

In Google Docs prepare the document as you would normally do and once you are ready to sign it, get the .ID add-on for Google from the GSuite marketplace.

Read more

  • How do I install .ID for Google Docs?
  • How to log in to connect .ID platform and .ID for Google Docs
  • How do I send the document to .ID platform for signing?

Step 3 - Sign document in .ID platform

.ID add-on will create a PDF version of your Google document and prepares a signature container with the PDF inside it in .ID platform. After you have send the document to .ID platform, head over there and sign the document as usual.

Agrello DLT token
What is Agrello Delta Token (DLT)?
>

DLT token is designed to be a voucher next to conventional financial methods to consume Agrello products and services.

DLT token is also used to reward parties that contribute to the operations and improvement of Agrello services.

DLT is a Blockchain based cryptographic token that can be exchanged for other cryptographic tokens and cryptocurrencies on 3rd party digital asset exchange sites.

DLT token is running on and secured by Ethereum public blockchain ERC-20 smart contract. For holding and managing DLT tokens, one has to have a Ethereum digital wallet that supports ERC-20 tokens. Contact address and details about the token itself can be found here: https://etherscan.io/token/0x07e3c70653548b04f0a75970c1f81b4cbbfb606f

How do I store DLT assets?
>

DLT tokens can be stored on a cryptocurrency/cryptotoken wallet. The wallet has a recipient address to which the tokens must be transfered to. In most of such wallets, the token account must be set up using DLT ERC-20 contract address, which is 0x07e3c70653548b04f0a75970c1f81b4cbbfb606f.

One of the most used services providing a personal cryptocurrency/ctyptotoken wallet is Metamask.

For this example we are using Metamask Mobile application.

Step 1: Install Metamask

In Apple App store or Google Play, look for Metamask. Install the .ID application and open it. You should end up in the wallet page, where there’s a button “+Add tokens”

Installing MetaMask




Step 2: Add DLT

Select Custom Tokens and start by entering DLT token address:

0x07e3c70653548b04f0a75970c1f81b4cbbfb606f

Step 3 - Receive tokens

Use your public address to direct tokens to your wallet.

Congratulations!

You are ready to store DLT tokens on your Metamask wallet. There are many other wallet providers on the market. With most of them the process is simlar.

Where can i trade DLT?
>

DLT is a Blockchain-based cryptographic token that can be exchanged for other cryptographic tokens and cryptocurrencies on 3rd party digital asset exchange sites.

Currently, DLT is being traded on following digital exchanges:

I’m missing my 2FA device
>

To deactivate the 2fa for the account we need to verify your identity first. Please follow the steps below:

  1. Install Agrello .ID app from Play Market or App Store (Android or iOS respectively);
  2. Create a new account (if possible use the same email you used for token platform);
  3. Verify your identity.

Please, let us know the verification is done and provide the next information:

  • your Name and Last Name you were using for the verification;
  • your email address connected to the Agrello token platform account
  • In case email connected to token platform is different from one connected to .ID please include both.

I don’t receive an SMS code and can’t log in to my Agrello token platform account.
>

The SMS auth was disabled for the platform in December 2017 and DLT investors were invited to use Google 2FA instead of SMS.

To deactivate the SMS auth for the account we need to verify your identity first. Please follow the steps below:

  1. Install Agrello .ID app from Play Market or App Store (Android or iOS respectively);
  2. Create a new account (if possible use the same email you used for token platform);
  3. Verify your identity.

Please, let us know the verification is done and provide the next information:

  • your Name and Last Name you were using for the verification;
  • your email address connected to the Agrello token platform account
  • In case email connected to token platform is different from one connected to .ID please include both.

Let's make something great together!

Get in touch with us