Skip to content
Legal

Terms of Service

These terms govern the use of ALL access. They are written to be read: short sentences, no maze of defined terms, and they describe what the software genuinely does — including the parts that are not flattering.

Draft — not in force

This document is a draft. It has not been reviewed, and it is not in force.

It was written by an AI from what this software actually does, so that a qualified person has something concrete to review instead of a blank page. It is not legal advice, nobody has checked it, and until somebody has, nothing on this page is a commitment by anyone.

Some passages need a decision that cannot be read out of the code — a liability cap, the governing law, a retention period, the list of services that touch your data. Where such a value is still missing, this draft says nothing rather than inventing something plausible.

If you are evaluating us and you have reached this page, ask us for the reviewed version rather than relying on this one.

1. Who this agreement is between #

This is an agreement between ALL DIGITAL LLC, registration number 412686464, of Agmasheneblis Ave. 1–3, Kutaisi, Georgia ("we", "us"), and the organisation that opens an ALL access account ("you", "your organisation"). If you accept these terms for a company, you confirm that you are authorised to bind it.

An account is opened for one organisation, together with the people your administrators invite into it.

2. What ALL access is #

ALL access has two halves. In the cloud, a console where you manage sites, doors, cardholders, cards, access groups, time schedules, employees, attendance, leave and reports. On your premises, an edge agent that talks to your door controllers and relays what happened at them back to us.

We provide the software. The decision to open a door is made by your controller, on the credentials it holds, and it keeps making that decision when your internet connection or our service is unavailable.

The subscription does not include hardware, cabling, locks, power or installation labour. Section 3 says who is responsible for those.

3. Hardware, installation and your operator #

Controllers, readers, locks, power supplies, exit devices, and the work of installing and commissioning them are not part of the subscription and are not priced by it. They are supplied and installed either by you or by the operator who looks after your account, under a separate arrangement.

Provisioning — putting a controller on a network, giving it an address, registering it, and attaching doors and readers to it — is done by your operator rather than from your own console. Your console tells you who your operator is and how to reach them.

We are not responsible for hardware we did not supply, for how it was installed, or for whether an installation satisfies the building and fire rules that apply to your premises. That is a matter for you, your installer and the authority having jurisdiction over the building.

4. Accounts, administrators and roles #

Your own administrators create the accounts inside your organisation, build roles from a permission matrix, and decide what each person may see and do. There is no self-service signup: an account is opened for your organisation, and the people in it arrive by invitation from one of your administrators.

You are responsible for who you give an account to, for the permissions you grant, and for keeping credentials confidential. Every account should belong to one identified person — a shared login destroys the value of the audit trail that the rest of this document depends on.

Two-factor authentication is available on every account, and your administrators can make it mandatory for a role.

5. The trial #

A new account begins on a trial that runs for 14 days from the day it is opened. It is limited to 1 door and 10 employee records.

There is no free tier. When a trial ends the account does not become free, and it does not charge you: there is no card on file and nothing is taken automatically.

If the trial ends without a plan, the console locks. Your data is kept and stays exportable, your controllers are not switched off, and the cards already stored on them keep working. Nothing in this service ever stands between a person and the way out of a building.

A trial is arranged when your account is opened, by a person. The buttons on our website that offer one take you to a short form rather than to a signup page, because that is what actually happens.

6. Fees, VAT and invoices #

Plan prices are published on our pricing page. They are monthly, and they are gross: the price shown includes 18% VAT, and the page states how much VAT each price contains.

An invoice is issued for each period and is due 14 days after it is issued. Where an online card rail is enabled you may pay by card; otherwise you pay by transfer and the payment is recorded against the invoice.

A plan meters two things, and it is worth being exact about what they count:

  • Doors — the doors you have added to the system.
  • Employee records — people on file in the employees list, whether or not they are still active. Offboarding somebody does not release their place; deleting the record does.

Nothing else is metered. Console logins, cardholders and cards are not counted against any plan, and no plan limits the number of sites.

Reaching a limit stops you adding more. It never deletes, disables or hides what you already have.

7. If an invoice is not paid #

If a card payment fails we retry it on a fixed schedule before the subscription lapses. If it does lapse, the console locks in the same way as an expired trial: the data stays, the controllers stay configured and armed, and exit stays exactly as safe as it was.

We do not use software as a lever on the physical security of your building. There is no "switch the doors off" consequence of a billing dispute, and there never will be.

8. Your data, and your people's data #

The data in your account is yours. We hold it to run the service for you: in data-protection language your organisation is the controller and we are the processor. What is held, who can reach it, and how long it is kept are set out in our Privacy Policy, which forms part of these terms.

You are responsible for having a lawful basis for what you record about your employees and visitors, for telling them about it, and for answering their requests. The console gives you the tools — role-scoped access, a complete per-person file, an audit trail — but the duty is yours, and the law puts the burden of proving the basis on you rather than on us.

We do not sell your data, we do not profile your people for our own purposes, and we do not use any of it to train models.

9. Our access to your account #

Support and provisioning need access to your account, and we would rather you knew exactly what that means than found out later. An operator account on our side can, with the right permission, sign in to your organisation as one of your users, and can read your audit log.

Every one of those actions is written into your own audit log: the session starting and ending, each action taken during it marked with the operator account behind it, and an operator reading your log recorded in that same log. Your console carries a page that states this in the same words and links straight to the entries, so you can check it rather than take our word for it.

One thing we will not dress up: an operator signing in as one of your users is not something you approve in advance, it is not time-limited, and you cannot switch it off. During such a session the warning banner is on the operator's screen and not on yours — you see it afterwards, in the log.

Whether an operator may see whose card was presented at a door is a separate question with a different answer. That is off until one of your administrators turns it on, it expires by itself at the end of the period they choose, an operator cannot turn it on for themselves, and every name an operator reads is written to your log.

10. What you may not do #

The service is a record of who went where. That makes a short list of prohibitions worth stating plainly:

  • Do not use it to watch people in a way the law where you operate does not allow, or to record data about them that you have no basis to hold.
  • Do not use it to record biometric attendance. We do not build it, and we will not help you assemble it. Section 8 of the Privacy Policy explains why this is unlawful in Georgia rather than merely inadvisable.
  • Do not share an account between people, and do not give access to somebody who should not have it.
  • Do not attempt to reach another organisation's data, do not probe the service for weaknesses without our written permission, and do not interfere with the edge agent's ability to report what happened at a door.
  • Do not resell or re-provide the service to anyone else unless we have agreed it in writing.

11. Availability, maintenance and support #

We aim to keep the service available, and we will give notice of planned maintenance where we can. The service runs over the internet and depends on your connectivity and your hardware as much as on ours.

It is designed on the assumption that we will sometimes be unreachable. Your controllers keep deciding on the credentials they already hold, and the edge agent stores events and sends them when the link returns. An outage on our side should cost you a delay in reporting, not a locked-out employee.

12. Life safety: getting out is hardware, not software #

Read this section even if you read nothing else on this page.

Leaving a building must not depend on this service, on your internet connection, or on any software at all. Fail-safe egress — the exit device, the fire interface, the power arrangement that releases a door when it has to be released — is a property of the installed hardware and of nothing else.

You and your installer are responsible for ensuring that every door complies with the fire and building rules that apply to your premises, and that people can get out with this service switched off entirely. No configuration you make here, and no billing state of your account, will ever be allowed to stand between a person and the way out.

ALL access is not a fire alarm system, not an intruder alarm and not a life-safety system, and must not be relied upon as one.

13. Intellectual property #

The service and the software remain ours. You receive a non-exclusive, non-transferable right to use it for your own organisation for as long as your subscription is live.

Your data remains yours; nothing here gives us a claim over it. If you send us feedback we may use it to improve the product, and that does not change the previous sentence.

14. Confidentiality #

Each of us will keep the other's confidential information confidential, and use it only to perform this agreement. On our side that includes everything we see inside your account.

This does not prevent either of us disclosing something the law requires us to disclose, provided we tell the other where we are permitted to.

15. What we promise, and what we do not #

We promise to provide the service with reasonable skill and care, and that what our website says the product does is honest.

We do not promise that the service will be uninterrupted or free of errors, that it will prevent every unauthorised entry, or that it will capture every event. It is one control among the several a building needs, and it depends on hardware and networks we do not control.

Beyond what is stated here, the service is provided as it is.

16. Limitation of liability #

Neither of us is liable to the other for loss of profit, loss of business, or indirect or consequential loss.

Nothing in this agreement limits liability that the law does not permit to be limited — in particular liability for death or personal injury caused by negligence, or for fraud.

17. Term, suspension and termination #

The subscription runs from month to month unless we have agreed something else with you in writing. Either of us may bring it to an end; the consequence of that is a locked console, never a locked or an unlocked door.

We may suspend an account where it is being used in a way that breaks section 10, where payment is outstanding, or where we have to in order to protect the service or other customers. We will tell you why, and what would lift it.

18. Getting your data out #

While your account exists you can export your data from the console: timesheets, door events, reports, and a single file containing everything held about one person.

We would rather be your archive than your hostage. A locked or lapsed account keeps its data, that data does not become unreadable, and the fact that you have stopped paying does not delete your history.

19. Changes #

We will keep developing the service. Features will be added, and occasionally something will be replaced by something better. We will not remove a capability you depend on without telling you.

If we change these terms in a way that matters, we will say so and date the change. The date at the top of this page is the date it last changed.

20. Governing law and disputes #

If something goes wrong, write to us first. Most disputes are a misunderstanding and are cheaper to resolve in an email than anywhere else.

21. How to reach us #

Our contact page reaches a person. Our about page carries the registered entity, its registration number, its address and its telephone number, so that you can check who you are dealing with before you buy anything.

Draft — not in force

This document is a draft. It has not been reviewed, and it is not in force.

It was written by an AI from what this software actually does, so that a qualified person has something concrete to review instead of a blank page. It is not legal advice, nobody has checked it, and until somebody has, nothing on this page is a commitment by anyone.