You once gave a platform access to business data: to deliver a dossier, let a colleague look on, or make a connection between two systems work. The question that remains: what happens if you never revoke it? The short answer is that nothing happens by itself. Access you have granted remains active until you revoke it yourself or the platform has reason to do so. There is no automatic expiration date that arranges for a connection to stop once the reason for it has disappeared.
That does not mean something immediately goes wrong. A platform that still has access typically uses it for exactly the purpose for which you gave it. The risk lies in the time that passes without you looking at it anymore: data that becomes outdated but remains visible, a former employee who can still log in on behalf of your company, or an overview of who has access to what from you that no longer matches reality. These are practical consequences, not a legal ruling on your situation — for that we refer you to the supervisory authority or a lawyer familiar with your case.
Why access does not disappear by itself
Most platforms are built so that access remains until someone actively terminates it. This is not negligence on the part of those platforms; it is simply the standard for data sharing between systems. A connection you set up for a one-time delivery technically remains as long as a connection you intended for years, unless you make the difference yourself. Those who do not know this easily assume that a task that is completed also takes the associated access with it. This is a misunderstanding that becomes especially visible the moment you want to check who exactly has access to which data.
What this can mean in practice
Suppose you once gave an advisor access to your business dossier for a one-time engagement. Without you revoking it, that access remains after the engagement is completed. The same applies to a connection between two internal systems that you once tested and then left as is, or to an employee who changed roles but was not logged out anywhere. In itself, this need not be a problem. It becomes more difficult the moment you need to be able to demonstrate who has access to which data from your company, for example during an audit or when drawing up a new dossier. Then it counts not only what you remember, but what actually still stands open.
The difference between closing an account and revoking access
Cancelling an account with a platform is not the same as revoking the access that platform once received to data elsewhere. The reverse also applies: you can revoke a connection without cancelling an account anywhere. These two are often confused, with the result that people think they are done while there is still an open access standing, or unnecessarily close an account when the problem was in a forgotten connection. If you want to know exactly what reglia does and does not do for you in this regard, you can read that at the page on how reglia handles your data.
How you maintain an overview of who has access to what from you
The practical solution is not complicated, but it does require a habit: periodically check which platforms and people have access to your business data, and actively remove what is no longer needed. For companies working with multiple compliance platforms, that overview quickly amounts to several separate lists that no one maintains systematically. A central overview of who uses which data from your business makes withdrawing a matter of a few minutes instead of detective work. That insight should deliberately be on the free side: you should always be able to see what happens to your data, without having to pay for it. More on how that is arranged can be read on the page on security and your data.
Where reglia helps and where it doesn't
Reglia does not explain which rule applies to your business and does not assess whether a particular access has been open too long. That remains the responsibility of the platforms themselves, your lawyer, or the competent supervisor. What reglia does do is maintain one business file that platforms read, and provide an overview of who is involved — so you can see for yourself what is open and withdraw it as soon as that is necessary. Each platform continues to work separately in this respect, even without reglia; reglia only adds the overview that would otherwise not be there.
If you want to see which platforms can currently be combined with each other via reglia and what each one handles itself, check out the overview of connected platforms. If your question is not among them, you will find additional explanation on the frequently asked questions page.