Privacy Policy
Effective date: 21 November 2026 (last updated 21 November 2026: password-only dashboard; Claude execution controls)
This policy describes how Research Bridge (the "app") and this website handle data. Research Bridge is a private tool operated by a single individual (the "operator") for their own research. It is not offered to the public, and the only Google account it is used with is the operator's own.
1. Google user data the app accesses
The app requests one Google OAuth permission: https://www.googleapis.com/auth/drive.file. Google limits
this permission to files and folders that the app created, or that were explicitly made available to the app (for
example, opened with it or selected for it). Other files in the Drive are not accessible to the app through this
permission.
The app is designed to operate only within its own research-bridge folder and its
inbox, results, cancel and brief subfolders. There, the app:
- reads task files (JSON, or Google Docs exported as plain text), cancellation markers, the project brief document;
- reads file metadata such as file IDs, names, sizes, checksums and modification times, to process each task exactly once;
- creates and updates its own folders and files: status files, structured result files
(
result.json), Markdown reports, small result attachments, rejection notices for invalid task files, and placeholder "slot" files.
The app never deletes, moves or trashes any Drive file, and it does not access Gmail, Calendar, Contacts, or any other Google service.
2. How the data is used
Drive data is used only to provide the app's single function: running the research tasks that the operator places in the folder, and returning the results to the same folder. It is not used for advertising, profiling, or any other purpose.
3. Where data is stored
The app runs on a private virtual machine in Google Cloud (United States region) administered by the operator. On that server it stores:
- a job database containing task contents, job status and history, results, reports, and a permanent library of research findings and the operator's notes on them;
- temporary working files for each job, and local copies of result files waiting to be uploaded;
- each version of the project brief;
- operational logs (the app's own log file is rotated at 5 MB with five older files kept; system logs on the server are rotated weekly and kept for about five weeks);
- an audit log of the operator's administrative actions and sign-ins to the server-side dashboard;
- the Google OAuth token, in a file readable only by the app's dedicated service account.
The service runs as an unprivileged, sandboxed account with no access to other data on the server. Its
management dashboard listens only on the server itself; the server's web server publishes it over HTTPS at
monitor.albertsstockhelper.com, where every page requires the dashboard's own password sign-in (with
rate limiting and lockout after repeated failures). Google sign-in is not used for the dashboard. This website
serves static pages only. Connections to Google, Anthropic and the dashboard use HTTPS, and Google Cloud encrypts
disks at rest.
4. Sharing and third parties
Data is not sold, rented, or shared for advertising. It is shared only as follows:
- Google: data is exchanged with Google Drive through the Google Drive API to read tasks and write results.
- Anthropic (Claude): while the operator has research execution started in the dashboard, the text of each submitted task (its title, goal, constraints, notes and acceptance criteria) and the project brief are sent to Anthropic's Claude service, through Anthropic's own Claude Code software and the operator's own Claude subscription, so that the research can be carried out. By default a job has no tools: it cannot read files on the server, search the web or run commands, and answers from the model's own knowledge. Each job is limited in time and number of steps. Claude Code reports the subscription's usage percentages back to the app, which stores them to pause work at the operator's chosen limits. Content sent to Anthropic is handled under Anthropic's applicable terms, privacy policy and the operator's account settings, which govern how long Anthropic keeps it and whether it may be used to improve Anthropic's models. The operator can stop Claude execution at any time from the dashboard.
- Legal requirements: data may be disclosed if required by law.
No other person or company receives data from the app.
5. Google API Services User Data Policy
Research Bridge's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data obtained through Google APIs is used only to provide the app's user-facing function described above. It is not used for advertising and is not sold.
Artificial intelligence. Research Bridge does not itself develop, improve or train artificial-intelligence or machine-learning models with Google user data. While Claude execution is started, task content from Drive is sent to Anthropic only so the requested research can be performed; Anthropic's handling of that content is described in section 4.
6. Retention and deletion
While the service is running, a cleanup runs once a day and applies these default periods (the operator can shorten or lengthen them):
- Job working files on the server are deleted after 30 days.
- Server-side copies of result files that have already been uploaded to Drive are deleted after 14 days.
- Detailed job event logs are deleted after 365 days.
- Logs of the dashboard (IP address, time and requested page) are kept in a separate system log for at most 30 days. Dashboard sign-ins and failed sign-in attempts (with IP address) are recorded in the audit log.
- Job results, reports, the research library, project-brief versions and the audit log are kept until the operator deletes them.
- Files in Google Drive remain under the Drive owner's control and are never deleted by the app.
Access can be revoked at any time at Google Account → Third-party apps & services. After revocation the app can no longer reach Google Drive. The operator can delete the server-side data and OAuth token at any time.
7. This website
This website consists of two static pages. It uses no cookies, scripts, analytics, trackers or third-party
resources. As with any web server, standard access logs (IP address, time, requested page and browser user agent) are
kept for security and troubleshooting. The same applies to the dashboard at
monitor.albertsstockhelper.com, which sets only the cookies needed for its own sign-in. These logs are
rotated daily and the previous 14 days are kept, so entries are deleted after about 15 days. They are not shared.
8. Children
Research Bridge is a personal tool. It is not directed at children and does not knowingly collect data from anyone other than its operator.
9. Changes
If data handling changes, for example if a different Google permission is needed, this policy will be updated before the change takes effect, and the effective date above will change.
10. Contact
Questions about this policy: albertseo206@gmail.com