This policy applies to url2supernote (“the app”), open-source software developed by Steve Xuereb (“the developer”, url2supernote@steve.mt) and published at github.com/stevedotmt/url2supernote.
Who runs the app
The app is not a hosted service. Each person who uses it (the “Owner”) runs their own copy with their own Telegram bot and their own Google Cloud OAuth client. The developer does not operate a server that receives, stores or processes any Owner's data, and has no access to it. When the developer runs the app for himself, he is the Owner.
Google user data the app accesses
The app requests one Google OAuth scope,
https://www.googleapis.com/auth/drive.file. It accesses:
-
the ID and name of the single Google Drive folder the Owner picks in
the Google Picker during setup (normally the Supernote's
INBOX); - the names of files the app itself created in that folder, to avoid delivering the same article twice.
The app does not access the Owner's other files or folders, contacts, email, calendar or any other Google data.
How the app uses it
The app uses this access only to create EPUB files, built from web pages the Owner sends to their Telegram bot, in the folder the Owner picked. Nothing is used for advertising, profiling, analytics or training of machine-learning models.
What is stored, and where
- OAuth credentials. The refresh token, the OAuth client ID and secret, and the folder ID are stored only in the Owner's own deployment, as environment variables or, on Google Cloud Run, as the Owner's own Secret Manager secrets. They are never sent to the developer.
- Articles. The app keeps no database. An article is held in memory while its EPUB is built, written to the Owner's Drive folder, and discarded.
- Logs. The app logs delivery outcomes, including the URL of each article and error messages, to the standard output of the Owner's deployment. Logs contain no Google access tokens, and are kept according to the Owner's hosting provider.
What is shared
The app does not sell, rent or share Google user data. It sends data only to services needed for it to work, all chosen by the Owner:
- Google, to authorize and to upload EPUB files to the Owner's Drive;
- Telegram, to receive the Owner's messages and reply with the result of each delivery;
- the websites of the articles the Owner sends, which the app fetches from public addresses.
The developer does not receive or read any Google user data.
Google API Services User Data Policy
url2supernote'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.
Retention and deletion
The Owner can stop the app and delete its credentials from their deployment at any time. To revoke the app's access to Google Drive, remove it at myaccount.google.com/permissions or delete the OAuth client in the Google Cloud console. EPUB files the app created stay in the Owner's Drive until the Owner deletes them.
Children
The app is not directed at children under 13.
Changes
If this policy changes, the new version will be published on this page with a new date, and the history is available in the project repository.
Contact
Questions or requests: url2supernote@steve.mt.