Privacy notice.

Controller

TAKEHOST OÜ

Legal form

Private limited company

Registry code

17524902

LEI code

984500B3B0D694AFO595

Address

Harju maakond, Tallinn, Kesklinna linnaosa, Tornimäe tn 5, 10145, Estonia

Privacy contact

[email protected]

TAKEHOST OÜ, trading as lir.rent, decides what is recorded and why, so it is the controller for everything described here.

Account

Name, email address, whether that address has been verified

Credentials

A hash of your password, never the password itself

Sessions

Session token and expiry, IP address, user agent

Membership

Which organisation you belong to and your role in it

Organisation

Legal name, registry code, country, VAT number, abuse mailbox, announcing ASN

Access request

Email, organisation name, registry code, ASN, intended use

Quote request

Contact email, family, prefix size, quantity, regions, term

Leases

Orders, invoices, authorisation letters, ROA requests

Support

Tickets and the messages on them

Audit trail

Who changed what, when, and the record it applied to

An operator can attach an internal note to a support ticket. Internal notes are for the operator handling the case and are not shown in your view of the ticket.

Your account, your organisation profile, holds, orders and invoices are processed to perform the leasing contract and to bill for it. Without them there is no lease.

The audit trail and abuse handling rest on legitimate interest. Address space carries a reputation, so every state change on a lease is recorded with the person who made it and reports against leased space are investigated.

Invoices and the documents behind them are kept to meet a legal obligation, the accounting duties of an Estonian company.

Every state change is written as an audit event: the action, the record it applied to, the organisation, the person who acted and the time. Verification decisions, order activation, holds, geolocation publications and ticket changes all produce one.

Nothing in the application updates or deletes an audit event. It is written once and read afterwards, which is how a lease can be reconstructed later.

Mail is written to an outbox in the database before it is sent, and is held there until it is delivered. A queued message keeps its recipient, subject and body, along with how many delivery attempts were made and the last error if one occurred. That is what stops a failed connection from silently losing a verification message.

A session cookie is set when you sign in, and it is what keeps you signed in. It is needed for the dashboard to work at all.

Invoices and their source documents are kept for seven years, because Estonian accounting law requires source documents to be retained for that long.

Account, organisation, lease and support records are kept while the relationship runs and for as long as they are needed to answer a question about a lease that existed.

Verification is an explicit decision an operator takes and signs their name to in the audit trail. So is activating a lease, publishing a geolocation change and withdrawing a block. No decision about you is made automatically, and no profiling is carried out.

You can ask for a copy of what is held about you, ask for it to be corrected, ask for it to be erased, ask for processing to be restricted, ask for it in a portable form, and object to processing that rests on legitimate interest. Where a legal obligation applies, such as an invoice inside its retention period, that record is kept.

Two of those you can exercise yourself. Signed in, data and privacy downloads your account, your organisation and everything attached to it as one file, and files an erasure request as a support ticket an operator answers.

For anything else, write to [email protected] from the address on the account and say what you want done. You can also lodge a complaint with a data protection supervisory authority.

Reports about a leased block go to [email protected].