Withdrawing a connection in reglia itself is immediate: you switch off access and from that moment on the platform cannot read any new data from your company and product file. What can take longer, and where reglia has no control, is what the platform then does with the data it has already received or stored. These are two different things, and the confusion about this is precisely where many users run into problems.
So there is no fixed 'processing time' for withdrawing shared access in the sense of a waiting period or processing deadline: switching off the connection is an action you perform yourself and it takes effect immediately. The remaining question, which differs per platform, is how that platform handles data that was already there before you withdrew access. For that question, the platform itself is the right place to look, not reglia.
What exactly is withdrawn
A connection between reglia and a platform determines whether that platform is allowed to read your company and product file. As long as the connection is active, the platform can use the data in it for what it needs: an address for a shipping label, a Chamber of Commerce number for a registration, product data for a file. If you withdraw the connection, that access stops for new readings. What the platform has already retrieved and stored on its own system does not automatically fall under that. how reglia handles shared data explains what reglia does and does not do when sharing data, and where reglia's role ends.
This distinction is not intended to make things more complicated than necessary; it simply follows from how systems work. A file that has already been submitted to a supervisory authority, or an application that is already being processed, does not change once you withdraw the connection. For the deletion of data that a platform has already stored itself, that platform is the party you need to contact, possibly with the supervisory authority in the background if personal data is involved.
Where it often breaks down in practice
The most common assumption is that withdrawing access is the same as making data disappear from the platform. These are two different actions, and only the first is reglia's responsibility. A second point where it often breaks down: people withdraw access during an ongoing process, for example while a file is still being updated, and are then surprised that the platform did not receive the latest change. So it is better to withdraw the connection at a time when there is no pending action with that platform, or check first the answers to questions about access and withdrawal if you are in doubt.
A third situation that is often overlooked: multiple employees with their own login on the same business account. If you withdraw the connection on behalf of the company, it applies to everyone working under that account, not just yourself. For companies with multiple users, it is therefore wise to coordinate first to see who depends on what, before access disappears.
What you can control immediately
What is immediately clear is which platforms are currently connected and which part of your file they are allowed to read. This overview is not behind a paywall: access to information about who has which data, and the ability to change that, are part of reglia's free section. How this is technically and organizationally set up is described on the page about securing your data.
For the question of whether a platform is obliged to delete data at your request, and within what timeframe, the correct route is through the platform itself or, if you are in doubt about personal data, the competent supervisory authority. Reglia makes no substantive statement on this: that falls within the expertise of the platform or of a legal professional, not within the shell that manages the connections.
Would you like to see which platforms are currently under reglia and how connections work there, then please check which platforms there are and what each platform itself does with shared data.