Privacy Policy
This policy explains how Beetzee handles information when you use beetzee.cloud, including Google sign-in, connected Google services and Upload Link. Contact us at 1@beetzee.cloud with privacy questions or requests.
Information used by Beetzee
Depending on the features you use, Beetzee processes your account and contact details; project, booking, agreement and billing records; content and links you provide; and activity, device, network and diagnostic information needed to operate and protect the service. Session cookies keep you signed in and support security controls.
Google account connections
Google sign-in provides the account identity information used to sign you in, such as your email address, name and Google account identifier. Connecting an additional Google service requires its own authorization. Beetzee stores connection credentials on its server so an authorized connection can continue without repeatedly asking you to sign in. Beetzee does not receive your Google password.
For connected Calendar features, Beetzee accesses calendar and event information and performs the calendar actions you authorize in the application. Connected Drive features use file and folder information to provide the Drive functions you select.
Upload Link and Google Drive
The organiser connects their own Google account and selects a destination folder using Google’s picker. Beetzee uses that account’s authorization to create a Google resumable upload session for that folder. File contents travel directly from the sender’s device to Google Drive; the Upload Link file contents are not relayed through Beetzee’s web server.
Upload Link requests Google’s limited drive.file permission. It can access files and folders you explicitly select for this app, and files it creates. The organiser uses Google’s folder picker to choose the destination. A pasted folder URL alone does not grant access. This does not request access to every file in your Drive. Guests receive a restricted upload-session URL, not the organiser’s Google access token or a Drive-browsing interface.
Beetzee records the organiser, event title and optional event date, destination folder link and identifier, upload-link settings, and upload metadata such as filename, file type, declared size, timestamps and reported status. A hashed network identifier helps limit upload abuse. Infrastructure security logs may also contain IP addresses and request details. A reported completion status is not a guarantee that Google retained the file.
Anyone who receives an active public upload link may be able to submit files. Share it only with intended contributors and close it when collection is finished. The organiser controls the destination folder and its sharing settings in Google Drive. Uploading does not give guests permission to browse that folder through Beetzee.
Use and sharing
Information is used to provide the features you request, manage accounts and transactions, communicate service updates, troubleshoot problems and prevent abuse. Project information may be visible to the people you share it with and staff authorised to manage the relevant work. Files submitted through Upload Link are delivered to the organiser and may be accessible to people the organiser permits in Google Drive.
Service providers process information needed to deliver the service, including AWS for hosting, Cloudflare for web delivery and protection, Google for connected Google features, and applicable payment or communication providers when those features are used. Processing may occur outside your country. Information may also be disclosed when required by law or necessary to investigate abuse and protect users.
Google user data is used for the connected user-facing features and is not sold, used for advertising, or used to train general-purpose AI models. Beetzee’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Human access to Google data is limited to your specific permission, necessary security investigation, legal requirements, or permitted aggregated internal operations.
Storage, retention and your choices
Beetzee uses HTTPS and access controls, and stores Google connection credentials outside public web access. No service can guarantee absolute security. Records are retained as needed to operate the features you use, maintain required business records, investigate security issues and meet applicable obligations. Retention depends on the record and purpose; deleting an item may not immediately remove existing backups or required records.
You can revoke Beetzee’s Google access at Google Account connections. Revocation prevents further use of that authorization but does not delete files already delivered to Google Drive or records already held by Beetzee. Manage delivered files in Google Drive, or contact the organiser if you are a contributor.
For access, correction, deletion or removal of stored Google connection information, contact 1@beetzee.cloud. We may need to verify your identity and explain any records that must be retained. Do not send passwords or access tokens with your request.
Changes to this policy
Updates will appear on this page with an updated date. Material changes to the way connected Google data is used will be disclosed, and additional consent will be requested where required.