Privacy policy

Information we use

We store your account identity, login sessions and the records you choose to import. Google and GitHub sign-in use basic identity and email. LinkedIn provides basic identity only; it does not provide your employment history.

• Gmail: filtered email text from your selected label or mailbox window.
• Google Drive: bounded text from direct Docs, Sheets and Slides in your selected folder. Sheets includes only the first sheet. We do not traverse subfolders or read binary files, comments or revision history.
• Google Calendar: titles and times of confirmed regular events in your selected calendar. We exclude private events, attendees, descriptions and locations.
• Notion: bounded text from pages you select and share with the connection.
• Slack: filtered messages from selected public channels you belong to. We do not collect direct messages, private channels, files or thread replies.
• GitHub: titles, states and dates of issues and pull requests you authored in selected public repositories. We do not collect code, comments, bodies or diffs.

Provider permissions can be broader than the collection you select in CentralBy. For example, a Google Drive read-only token can read accessible files, and a Gmail read-only token can read the mailbox. CentralBy applies the selected resource and date limits within the application. Sensitive-information filters are imperfect and may miss personal information.

Purpose and sharing

Connected data is used to import, organize and summarize your private work records. CentralBy does not sell connected account data, use it for advertising or use it to train general-purpose AI models. Hosting and database infrastructure on Railway process data to operate the development service.

CentralBy's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Optional AI

Default extraction runs locally on the server. External AI is disabled until it is configured and you give separate consent for selected sources and a budget. If enabled, bounded, cleaned excerpts are sent to OpenAI to generate or organize work summaries. Provider retention policies apply; disabling response storage does not guarantee zero retention. Calendar scheduling does not establish attendance or completed work.

Security and access

OAuth tokens, imported work text and library summaries are encrypted before storage. Passwords are hashed and login cookies are HttpOnly. Account identity, source names, timestamps and some scheduling metadata remain readable to the database operator. An administrator with both the database and encryption key can decrypt stored content. Encryption does not guarantee that sensitive information has been removed.

Retention

Import previews are valid for ten minutes. Imported source text is retained for up to 180 days after saving; cleanup runs during app and import activity. Library summaries and bounded excerpts remain until you delete them or disconnect the source. Expired encrypted data may remain in an inactive database until cleanup runs. Database backups and storage snapshots can retain copies separately.

Your controls

You can pause daily collection, change the selected source, edit or delete imported memories, and disconnect an account from CentralBy. Disconnect removes the local tokens, collection schedules and associated imported records. Deleting or disconnecting does not delete upstream emails, documents or messages.

Drive and Calendar disconnect remove only the local service connection; they do not revoke the shared Google application grant. Remove CentralBy from your Google account's third-party access settings to revoke that grant. Revocation can affect all connected Google services. Other upstream revocation attempts may fail; the connection screen reports their status. For account deletion or data requests, contact us below.

Development service and changes

This is a development service. Features and supported provider access may change. Email verification and password recovery are not yet available. Material changes to data handling will be reflected in this policy and, where needed, new consent.

Contact

CentralBy · refresh
jh.ham@refresh.cv