The forgotten calendar assistant
Fictional example: Nora connected a travel-planning service to her calendar for a trip. The trip is over and she has removed the app. During an account review, she discovers that calendar access is still listed. She no longer needs it, so she revokes the permission in the official account settings. Another connection is also her usual way of signing in to a document service. There, she first works out how she will continue accessing her files before disconnecting anything.
Separate three different relationships
Installing an app on a device, signing into it through another account and granting access to account data are different actions. They may occur together, but they do not have to. Signing in with Google, for example, does not automatically give an app access to all your email. Read the details: which service connects to which account, what information is mentioned and which actions are permitted? Labels vary between providers. Use the current description shown in the account you are actually reviewing.
Make a manageable inventory
Start with one important account, such as your main email account. Navigate to its settings yourself instead of following a warning link in a message. For unfamiliar entries, note only the service name, purpose and question to resolve; do not copy credentials into your notes. Separate services you intentionally use, connections you no longer need and entries you cannot yet identify. Investigate unclear names using your own records and official help. An unfamiliar developer name by itself is not proof of misuse.
Disconnect without locking yourself out
For an unnecessary data permission, use the provider’s access-removal control. If the connection is also your usual sign-in method, first check the other service for a supported alternative or an account-closure process if that is what you want. Remove connections individually and then check important functions. Remember subscriptions managed separately from account access. Disconnecting an app does not automatically cancel a contract or necessarily delete the account held with the other provider. Treat these as separate decisions and keep relevant confirmations.
Understand what revocation cannot do
Removing permission stops further access through that connection, but it does not automatically retrieve information already sent to the other service. Stored copies need to be addressed through that provider’s deletion options and privacy information. If you discover actual unauthorised activity, simply tidying the list is not enough: review account security alerts and recovery options. Report suspicious services through official controls. Periodic reviews are useful housekeeping, but they do not replace secure sign-in methods, appropriate account recovery and up-to-date devices.
Your checklist
The checkboxes are for your own reference. No entries are sent to us. To keep a copy, print the page or save it as a PDF using your browser menu.
Common questions
Is deleting the app from my phone enough?
Not necessarily. Installing software and granting account permissions are different actions. Also review connections in the relevant online account’s settings.
Are all connected apps risky?
No. Many connections provide functions you deliberately use. Check whether the provider, permissions and current purpose make sense, instead of judging only by the number of entries.
Does revoking access delete my data?
Not automatically. Revocation concerns access through the connection. Data already stored by the other provider may need a separate deletion request under that service’s process.
Sources and further information
Primary sources from public authorities, consumer organisations and providers. A source may be in another language; follow the guidance that applies to your service and where you live.
- Google: Manage links between your Google Account and apps from other developersSource review date:
- Google: Share some access to your account data with apps from other developersSource review date:
- Cybermalveillance.gouv.fr: Se protéger sur les réseaux sociauxSource review date:
