Last updated:
1. Introduction
This Privacy Policy explains how 1C Cloud Exporter («Application»), developed by zmaxb, accesses, uses, stores, transfers, and handles the deletion of user data.
1C Cloud Exporter is an extension for 1C:Enterprise that uploads files generated by configured report distributions to the Google Drive account authorized by the user. Depending on the export settings, it creates new files or updates existing files accessible to the Application.
The Application operates within the user’s 1C:Enterprise environment. It communicates directly with Google’s authorization services and Google Drive API without routing exported files or OAuth credentials through servers operated by the developer.
This Privacy Policy covers the Application’s Google Drive integration. The user or the organization operating the relevant 1C:Enterprise information database manages its infrastructure, access permissions, source data, and backups.
2. Google Account Authorization
The Application uses Google OAuth 2.0 to obtain the user’s permission to access Google Drive.
Sign-in and consent take place through Google’s authorization pages. The Application does not request, receive, or store Google account passwords.
The Application requests the following Google OAuth permission:
https://www.googleapis.com/auth/drive.file
This permission allows the Application to work with files it creates and other specific files that the user makes accessible to it through Google’s supported authorization mechanisms. It does not provide unrestricted access to all files in the user’s Google Drive.
During authorization, the Application processes temporary authorization codes and receives OAuth access and refresh tokens. These tokens allow it to perform authorized operations and renew access without requiring the user to sign in for every export, while the authorization remains valid.
Users may revoke the Application’s access through their Google Account settings, as described in Section 8.
3. Data Access and Processing
Files and Google Drive metadata
The Application reads the contents and names of report attachment files supplied by the configured 1C:Enterprise report distribution process and uploads them to Google Drive.
The information contained in these files depends on the reports selected by the user and the data in the relevant 1C:Enterprise information database. Files may contain personal, business, financial, or other confidential information.
The Application performs the following operations:
- Creating new files and uploading their contents to Google Drive.
- Searching for files accessible to the Application by name and destination folder.
- Updating the contents of an accessible file with a matching name when the replacement option is enabled.
- Processing file and folder identifiers, file names, MIME types, file sizes, and other metadata returned for these operations.
Entering a destination folder identifier does not give the Application unrestricted access to every existing file in that folder.
The current Google Drive integration does not download the contents of existing Drive files, delete Drive files, or change their sharing permissions.
Exports run when the configured report distribution is executed, including scheduled execution where configured in the user’s 1C:Enterprise environment.
Google account information used for connection checks
When the user checks a Google Drive connection, the Application requests the Google Drive user information associated with the authorized account to verify that the connection is working.
The response may include the user’s display name, email address, profile photo URL, Google Drive permission identifier, and technical fields identifying the user resource.
The current connection-check procedure checks whether the request succeeds. It does not parse or save the profile information returned in a successful response in the Application’s database records, and it does not download the profile photo.
This information is received within the user’s 1C:Enterprise environment and is not transmitted to the developer by the Application.
4. Purpose of Data Use
The Application uses the data described in this Privacy Policy to authorize and maintain a Google Drive connection, upload report files, locate and update accessible files when configured, verify the connection, and diagnose export errors.
Google user data is not used by the Application for:
- Advertising, targeted marketing, or advertising profiles.
- Analytics or tracking unrelated to the Application’s functionality.
- Selling personal information or providing it to data brokers.
- Credit scoring or lending decisions.
- Training artificial intelligence or machine learning models.
5. Data Storage
The Application stores the following information within the user’s 1C:Enterprise information database:
- OAuth access tokens, refresh tokens, and access-token expiration information associated with a configured connection.
- Connection settings, including the OAuth Client ID and Client Secret.
- Export settings, including the associated report distribution, connection, destination folder identifier, and file replacement option.
- Export history, including operation dates and times, operation identifiers, references to the report distribution and connection, destination folder identifiers, operation results, and error descriptions.
Error descriptions may include request URLs, Google API error messages, parts of error responses, and technical execution details.
File identifiers and metadata returned during an export are processed to complete the operation. In the current version, the identifier returned after a successful file upload is not stored as a separate field in the export history.
Uploaded file contents are stored in the authorized Google Drive account. The Application does not copy those contents into its export history.
Original report attachments, temporary files, and database backups may also remain within the user’s infrastructure, depending on the underlying 1C:Enterprise configuration and administrative settings.
The Application does not send copies of OAuth tokens, exported files, or export history to the developer.
6. Data Transmission and Security
The Application sends authorization requests and file operations directly from the user’s 1C:Enterprise environment to Google’s OAuth services and Google Drive API.
Requests to these Google endpoints use HTTPS to protect data in transit. No intermediary server operated by the developer is involved in this exchange.
OAuth credentials and technical records are stored in the user’s 1C:Enterprise information database. Access to them depends on the database, application, operating system, and infrastructure permissions configured for that installation.
The current version does not apply separate application-level encryption when writing OAuth token values to the database. Encryption of the database, storage devices, and backups depends on the protections configured in the user’s infrastructure.
Users and their system administrators must restrict access to credentials and diagnostic records to authorized personnel and maintain appropriate database security, encryption, and backup protections.
7. Data Sharing and Disclosure
The Application transfers file contents and the metadata required for export directly to Google Drive. OAuth credentials are exchanged with the relevant Google services to obtain, renew, and use authorized access.
The Application does not transmit Google user data to advertising networks, data brokers, analytics services, or artificial intelligence services. It does not sell or rent Google user data.
The Application does not provide the developer with automatic access to the user’s Google Drive files, OAuth credentials, or locally stored export records.
Authorized users, system administrators, and infrastructure providers selected by the user or organization may have access to locally stored information according to the permissions and service arrangements of the relevant 1C:Enterprise environment.
The underlying 1C:Enterprise report distribution system may separately deliver the same source reports by email, FTP, or local or network folders when those delivery methods are enabled. These deliveries are separate from the Google Drive integration and follow the user’s report distribution settings.
Google processes information it receives according to its applicable privacy policies and service terms.
8. Data Retention and Deletion
Locally stored credentials and records
OAuth tokens are retained in the user’s 1C:Enterprise information database to support configured exports until they are replaced or deleted. Token expiration or revocation does not itself remove the corresponding database records.
The current version does not automatically delete stored tokens or export history after a fixed retention period. The administrator of the relevant information database determines retention periods and manages the cleanup of credentials, connection settings, export records, and related local files.
Users may request deletion of locally stored Application data from their database administrator. The developer does not have remote access through the Application to perform that deletion.
Stopping exports and revoking Google access
To stop future exports, disable the relevant export configuration or report distribution with the assistance of the database administrator.
To revoke the Application’s authorization, open the following page, select the relevant Application connection, and remove its access:
Revoking authorization prevents further use of the revoked access. It does not automatically delete locally stored tokens, export history, source reports, or previously uploaded Google Drive files. Local cleanup must be handled separately by the database administrator.
Removing or disabling the extension is not a substitute for revoking authorization in the Google Account. The administrator should verify which local records have been removed during any extension removal process and address remaining data separately.
Google Drive files and backups
Previously uploaded files remain in Google Drive until they are deleted or otherwise managed by the user or an authorized administrator. The Application does not automatically delete them when access is revoked or the extension is removed.
Where database or file backups exist, copies of Application data may remain in those backups after deletion from the active system. Backup retention and deletion are managed under the policies of the user or organization operating the infrastructure.
9. Google API Services User Data Policy
The Application’s use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including the Limited Use requirements.
Google user data is used only for the user-authorized functionality described in this Privacy Policy: maintaining the Google Drive connection, exporting files, checking connection availability, and diagnosing related errors.
The Application does not use or transfer Google user data for advertising, data brokerage, credit decisions, or artificial intelligence model training.
10. Third-Party Services
The Application integrates with Google’s OAuth authorization services and Google Drive.
Use of Google services is subject to the Google Privacy Policy and applicable Google service terms.
Any future integration with additional cloud storage providers that changes the handling of user data will be described in an updated Privacy Policy before that processing is introduced.
11. Changes to This Privacy Policy
This Privacy Policy may be updated to reflect changes in the Application, its functionality, or its data processing practices.
The latest version will be published on this page with an updated revision date.
Before introducing access to additional types of Google user data, or using Google user data in a new way or for a new purpose, the developer will disclose the change and obtain user consent before the new processing begins.
12. Contact
For questions about this Privacy Policy or the Application’s data processing practices, please contact:
Developer: zmaxb
Website: https://zmaxb.com
Email: zmaxbraun@gmail.com
For access to or deletion of data stored in a particular 1C:Enterprise information database, contact the administrator responsible for that database.
Please do not include Google account passwords, OAuth tokens, Client Secrets, or confidential report contents in email inquiries.