Last updated: May 5, 2026

Remove Dividends Inside From Your Google Account

To revoke Google Login access from Google, open your Google Account and review third-party connections. Find Dividends Inside in the list of connected apps and services and remove the connection.

Google's current instructions are available at Manage connections between your Google Account and third parties .

Removing the connection from Google prevents future access to Google Login data. It does not automatically delete the Dividends Inside account or portfolio records stored inside Dividends Inside.

Remove Dividends Inside From Facebook

To revoke Facebook Login access from Facebook, open Facebook and go to Settings & privacy, then Settings, then Apps and Websites. Find Dividends Inside in the connected apps list and remove it.

Removing the app from Facebook revokes future access to Facebook Login data. It does not automatically delete the Dividends Inside account or portfolio records stored inside Dividends Inside.

Unlink Google Or Facebook Inside Dividends Inside

A logged-in user can open account settings and unlink Google or Facebook from the linked accounts section. If the provider is the only sign-in method on the account, add another sign-in method before unlinking it.

Request Deletion Of Stored Data

To request deletion of account data stored by Dividends Inside, send a request from the email address connected to the account to info@dividendsinside.com, or submit a Support Center report while logged in.

Include the following details so the account can be identified:

• The email address used for the Dividends Inside account.
• Whether the account used Google Login, Facebook Login, email/password login, or more than one method.
• Whether the request is to unlink a login provider only or delete the full Dividends Inside account data.

What Deletion Covers

A full account deletion request can include the user account, OAuth login connection, preferences, portfolios, lots, holdings, imported records, support requests, and related user-owned records. Some operational records may remain for a limited time in backups, logs, security records, or where retention is required to protect the service or comply with legal obligations.