Privacy policy

1. Operator and scope

RAM Studio Drive Sync is operated by RAM STUDIO LLC. It is a private automation used with accounts and Telegram channels the operator is authorized to access. These pages provide public information about the app; they are not a public backup portal.

For privacy questions or requests, email ramstudiouploadstorage@gmail.com.

2. Data the automation accesses

• Telegram data: selected channel identifiers, message identifiers and dates, archive filenames, sizes, file identifiers and the contents of attachments selected for backup.
• Google data: connected-account information returned for account identification, Drive file and folder names, identifiers, parent relationships, sizes, checksums, app-specific properties and the metadata needed to find, upload and verify backups.
• Authorization data: OAuth access and refresh tokens used by n8n to make authorized Google Drive API requests.
• Operational records: archive status, progress, retry counts, timestamps, error information and links to backup folders.

3. How data is used

Data is used to copy authorized Telegram attachments into the connected Google Drive account, unpack supported archives, preserve folder structure, verify upload integrity, resume interrupted work, avoid duplicate backups and report the result to the operator.

Google account information is used only as needed to identify or validate the connected account. Google Drive metadata is used to locate backup folders and compare uploads with the archive manifest. The current automation is not configured to publicly share Drive files or delete Google Drive backups.

4. Google permissions

The integration requests Google Drive permissions through Google’s OAuth consent flow. Depending on the configuration, Google may display broad permission to view, edit, create and delete Drive files. The backup workflows use the granted access for locating backup folders, uploading files and reading metadata for verification and retries. These public pages do not request a Google login or receive OAuth tokens.

5. Storage and retention

Downloaded archives and extracted files are processed temporarily on the operator’s Hostinger-hosted n8n server. Successful job files are removed after Drive verification. Failed extraction output may be removed; resumable downloads can remain during retries. Disk-space failures and exhausted retries can evict local job copies after the original Telegram files are confirmed available.

Backup files remain in Google Drive until the account owner deletes them or changes retention settings. Archive tracking records, error logs and Drive folder links can remain in n8n after temporary job files are removed, so the tool can track results and avoid duplicates. Retention of n8n records and host-managed logs is controlled by the operator’s configuration.

OAuth tokens are stored in the self-hosted n8n credential store. Revoking Google access stops future authorized access but does not, by itself, delete existing Drive backups or locally retained tracking records.

6. Transfers, service providers and human access

The automation transfers selected attachment content from Telegram, through the operator’s server, to Google Drive. Operational notifications sent to the operator through Telegram can include filenames, status, errors, progress and Drive folder links.

Google, Telegram and Hostinger process data needed to provide their respective services. The public information pages are hosted using OpenAI Sites; the website host may process ordinary connection and security logs such as IP addresses and browser information. Backup files and Google OAuth tokens are not sent to the public website.

RAM STUDIO LLC does not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models. Human access is limited to the operator’s authorized use and support with permission, necessary security investigations, or legal obligations. Other disclosures occur only with consent, as necessary to provide the stated backup features, or as required by applicable law.

7. Google API Limited Use

RAM Studio Drive Sync’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

8. Security

Access to the automation is controlled through the operator’s n8n instance and connected accounts. Public pages contain no backup files, OAuth secrets or Telegram session credentials. Connections to these pages use HTTPS. The operator should restrict server and n8n access, protect credentials and maintain appropriate backup and security settings. No online system can guarantee absolute security.

9. Your choices, revocation and deletion

• The operator can pause workflows or disconnect the Google credential in n8n.
• The Google account owner can revoke the app’s access from Google Account third-party connections.
• The account owner can delete backup files directly in Google Drive. This tool does not automatically remove Telegram originals.
• To request removal of automation-held temporary files, authorization records or tracking data, contact the operator at the email above and identify the relevant account or backup. Requests may require identity verification. Provider-held copies and logs are governed by the relevant provider’s controls and policies.

10. Public website and cookies

We do not add advertising, analytics trackers, contact forms or account sign-in to these pages. Fonts and icons are served with the site. Ordinary hosting, security and network processing may still occur under the hosting provider’s policies. Clicking a third-party link or emailing support uses the respective provider’s service.

11. Changes and contact

Material changes to data use will be reflected in this policy before the new use begins. Where required, the operator will provide notice and seek new consent. The effective date appears at the top of this page.

Contact: ramstudiouploadstorage@gmail.com.