This policy describes what the application Nabanita does with data it
receives from Google. The application is operated privately by Abhishek Chowdhury (the
"operator") for his own use and has one user: the operator.
What the application accesses
- Google Drive, read-only. The scope requested is
drive.readonly: the application can list and read the operator's files. It cannot
modify, move, share or delete them.
- No other Google data is requested — not Gmail, not Calendar, not Contacts.
What is stored
- An OAuth refresh token, kept on a private server controlled by the operator
and readable only by him. It is what allows the application to act without asking him to sign
in every time.
- File metadata and contents are read only when the operator asks the
application to work with a specific file. They are used for that task and are not kept in a
database or archive afterwards.
What is not done with it
- Nothing is sold, rented or shared with third parties.
- No advertising, profiling or marketing use.
- No Google user data is used to train or improve machine-learning models.
- No human other than the operator reads the contents.
Revoking access
The operator can withdraw access at any time, without going through this site: open
Google Account → Security → Third-party
access and remove "Nabanita". Access ends immediately; the stored token stops working.
Deleting data
To request deletion of the stored token and any cached file content, write to
hermes@aurelux.in. Deletion is completed within seven days
and confirmed by reply.
Changes
If this policy changes, the updated date at the top of the page changes with it.