Operator and scope
Publication review required: the operator details are incomplete or contain example values. This document is not ready for publication until those details have been replaced and checked.
Eric Wündisch is the individual operator of Personal Integration Drive. The operator's address is Breite Str. 36, 14943 Luckenwalde, Germany. Contact details also appear in the Legal Notice.
This Privacy Policy describes access to, use of, storage of and disclosure of personal data and Google user data through the integration. Only the operator uses the integration and authorizes access to the operator's own Google account. It is not available to the public and has no public registration or third-party users.
The integration supports applications and automated workflows operated by the same individual. Its results may support activities with commercial objectives. The source files and published results currently contain only the operator's own personal data.
Google account authorization and permissions
Access requires authorization by the Google account holder through Google OAuth. The integration uses the scope https://www.googleapis.com/auth/drive.file to create files and access or manage specific files made available to the application through supported Google authorization mechanisms. These include files created by the application and files opened with or selected for it. This scope alone does not grant unrestricted access to every file in Google Drive.
Where the granted scopes and file permissions allow, the integration can read and download files, create new files, update existing files, delete files and manage relevant file metadata. These capabilities are available to applications configured and operated by the owner. Each workflow performs only the operations required for its configured purpose. A workflow may only read files even when additional operations are authorized.
Scopes configured for an OAuth application, scopes requested during authorization and scopes actually granted to an existing token are distinct and may differ. Introducing drive.file does not by itself revoke previously granted permissions. If an existing authorization also retains https://www.googleapis.com/auth/drive.readonly, it can allow reading and downloading files throughout the authorized account, subject to file permissions. That additional scope does not extend the file modification or deletion permissions provided by drive.file.
Owner confirmation required: confirm the configured and requested scopes and the scopes still granted to existing authorizations, including whether drive.readonly remains authorized.
Accessed files may include documents, structured data, images, media and configuration files. The integration may process their contents and metadata, such as file names, types and identifiers. Their contents and metadata may include personal data.
Processing and purposes
Applications hosted on OVH web hosting process the retrieved files as inputs to configured automated workflows. Processing may include reading, validating or transforming file contents and generating results. Multiple privately operated applications may use the same integration.
Google Drive serves as a source of files and may also receive newly created files or updates through authorized workflows. A workflow may modify file contents or metadata, or delete a permitted file, where that operation forms part of its configured purpose and the account authorization and file permissions allow it.
Google Cloud is used for Google API authorization and related services, not to host these applications. Google separately processes information needed to provide its account and API services under its own policies.
Google user data is not sold. It is not used for advertising, behavioral profiling or the creation of advertising audiences, or for purposes unrelated to the configured applications.
Storage, retention and deletion
Original files in Google Drive are distinct from copies retrieved by the integration. Source files are generally processed temporarily rather than stored permanently on OVH hosting. Applications may retain temporary intermediate files or generated outputs when needed for their workflows.
Retention depends on the application, the purpose of the processing and any applicable legal requirement. Some applications remove temporary results during subsequent processing or rotation cycles. There is no universal deletion deadline, and files are not necessarily deleted immediately after processing.
Authorization credentials and tokens are retained as needed to maintain authorized access. They must be revoked and removed when no longer needed, in accordance with Google's requirements. Technical logs and backups may have separate retention arrangements from working files and processed results.
Removing a retrieved copy does not delete the original in Google Drive. An authorized workflow may separately delete a file in Google Drive where the granted permissions allow it. Revoking authorization does not automatically delete copies already retrieved, processed results, logs or backups. Content already published on an external platform is also subject to that platform's retention and deletion processes.
Recipients and external publication
OVH provides the hosting infrastructure on which the applications process files. Google provides the authorized Google Drive API access. Source files are not intentionally transmitted to external AI processing providers as part of the described workflow.
Some applications generate content that the operator subsequently publishes through external platforms, such as Instagram. A configured application workflow may perform that publication when the operator explicitly authorizes it. This publication is separate from internal processing of source files. The platform receives the published content and handles it under its own policies. Publication does not imply that source files are sent to that platform.
Google user data is not sold or shared with third parties for advertising or marketing purposes. Any transfer of Google user data or derived content must remain within the disclosed, authorized functionality and Google's applicable Limited Use restrictions. Disclosure required by law or necessary for security must also satisfy those restrictions.
Publication review required: confirm the relevant OVH contracting entity, processing locations and any international transfer safeguards, together with the retention arrangements for technical logs and backups. These details must be completed before this policy is treated as final.
Security
The operator uses technical and organizational measures to protect application data and authorized access. Credentials are kept in protected, non-public locations. These measures reduce the risk of unauthorized access but cannot guarantee complete security.
Google's security requirements apply separately to the integration. This policy does not certify compliance with a security standard or replace those requirements.
Revocation and data protection rights
The account holder can revoke authorization through the Google Account third-party connections settings. Revocation prevents further access under that authorization and may stop dependent workflows. It is separate from deletion of information already retrieved or published.
Where applicable data protection law provides these rights, a person whose personal data is processed may request access, rectification, erasure, restriction or portability, or object to processing. Consent may be withdrawn where processing relies on consent, without affecting the lawfulness of earlier processing. A complaint may be made to the competent data protection supervisory authority.
Where the GDPR applies, processing necessary for the operator's application workflows and system protection may rely on legitimate interests under Article 6(1)(f), subject to the required necessity and balancing assessment. Processing required by an applicable legal obligation relies on Article 6(1)(c). Google OAuth authorization grants API access; it does not by itself establish a legal basis for every processing activity. Private access does not automatically make commercially connected processing exempt from data protection law.
Google API Services and Limited Use
Use of information received from Google APIs is subject to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including applicable Limited Use requirements.
These requirements cover both retrieved data and data derived from it. Uses must be limited to permitted application functionality. Transfers and human access are restricted to the circumstances allowed by those policies. The integration's private operation does not remove these obligations. No Google approval or verification is claimed.
Changes to this Privacy Policy
The operator may update this policy when applications, workflows or data practices change. The version on this website shows its own update date. New uses of Google user data require updated disclosures and authorization or consent where Google's policies or applicable law require them.
Contact
For questions about this policy or requests concerning personal data, contact Eric Wündisch at info@ericwuendisch.de.