Purpose of the integration
A business can optionally connect its own Google account so DCORP Invoice & Stock can save supported DCORP-generated receipts and documents to that user's Google Drive.
Permission requested
DCORP requests the following Google Drive OAuth scope:
This is a per-file permission. DCORP uses it to create or manage files associated with the application. DCORP does not request broad access to all unrelated files stored in the user's Google Drive.
Google account information used
- The Google account email address used to identify the connected account.
- OAuth access and refresh credentials required to maintain an authorized connection.
- Metadata and content for DCORP-generated or explicitly app-associated files handled through the integration.
How the data is used
- To connect the correct Google account to the requesting DCORP business.
- To save supported DCORP-generated receipts and documents to that Google Drive account.
- To reconnect to the authorized Drive service without requiring the user to sign in for every permitted operation.
What DCORP does not do
- DCORP does not request permission to read every unrelated file in the user's Google Drive.
- DCORP does not sell Google user data.
- DCORP does not use Google user data for advertising.
- DCORP does not use Google user data to build advertising profiles or for unrelated analytics.
Disconnecting Google Drive
A user can disconnect or revoke the Google connection. Revoking authorization prevents future Drive API access using that authorization. Users can also request deletion of eligible stored Google connection information through our Data Request page.
Security
OAuth credentials used for server-side Drive operations are intended to be kept in protected server-side storage and are not displayed as ordinary user-facing data in the customer application.
Related policies
For the complete explanation of data access, storage, sharing, retention and deletion, read the DCORP Privacy Policy.