Privacy Policy
To be completed and approved by the operator before publication: the full name and address of the data controller, the legal basis of processing, the hosting provider and location, the approved AI data recipients (exact endpoints) with their confirmed retention and training terms, the rules for human access to data, and the effective date. Until then this page is not a final policy, and connecting Google stays paused on production installations.
Who processes the data
Paulinka is a private assistant developed by Benjamin Romaniuk. Privacy contact: requests@paulinkai.pl. Each user has a separate installation with its own database; one installation's data is not accessible from another.
Google data and its purpose
You connect Gmail and Calendar yourself and separately. Declining one service does not block the other, and Paulinka uses only the permissions Google actually granted.
| Permission | What Paulinka does |
|---|---|
gmail.readonly | Reads messages, their metadata and the attachments you need, to prepare your briefing and answer your questions. It never sends, deletes, labels or changes messages. |
calendar.calendarlist.readonly | Lists your calendars so you can choose a private and a family calendar. |
calendar.events | Reads events in the selected calendars and — on your instruction — creates, changes and deletes events. Deleting, changing a whole series, attendees, reminders, notifications, visibility changes, other people's events and operations on several events require your separate confirmation, checked by the server. |
openid, email | Identify the connected Google account. |
Google data is used only for the features you use: briefings, answers and managing your matters. Paulinka does not use it for advertising and does not sell it.
Paulinka's use and transfer of information received from Google APIs (including Google Workspace scopes) adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google data is not used to create, train or improve general AI models.
Data flow
Google API → your installation's server → the assistant's tools → the AI model through an approved endpoint. Google access tokens never reach the assistant or the model. The refresh token is stored encrypted (AES-256-GCM) in the central OAuth broker or in the installation's database.
Artificial intelligence
The parts of your Google data needed for the current task reach an AI model only through an endpoint the operator approved. Every request to OpenRouter then sets: no data collection by the provider, zero data retention required, routing restricted to the approved endpoints and — by default — no fallback to another provider. Without such a configuration, AI processing of Google data is paused while every other feature keeps working. Browser and web-search tools are disabled in requests that contain Google data. Paulinka does not use Google data to train models; the AI recipients' terms are confirmed by the operator (see the box above).
Background activity
Once connected, Paulinka may, without you being present: prepare the daily briefing (04:00 installation time), run the configured proactive reviews, deliver reminders you set and retry revoking access at Google after a disconnect.
Retention
The periods below are technical defaults of an installation, not periods required by Google. Active tasks and the context you accepted are never removed because of their age.
| Data | Default period |
|---|---|
| Conversation history in the app | 180 days |
| Images sent in a conversation | 30 days |
| Briefings (except the latest) | 90 days |
| Matter conversations and operation context | 30 days |
| Assistant conversation memory (sessions and stored responses) | 30 days after last use |
| Trash and change logs | 90 / 180 days |
| Local backups | up to 30 days |
| Private offline copy on your device | 72 hours |
Disconnecting, deletion and export
You can disconnect Google at any time in “Your connections”. Disconnecting immediately blocks Paulinka's access and revokes it at Google; if Google is temporarily unavailable, the revocation is safely retried. When the same Google account is still connected to another Paulinka installation, revoking at Google is skipped so that installation is not disconnected — the status says so explicitly. You can also revoke access at myaccount.google.com/permissions. Deletion and export are described on Data Deletion.
Security
Connections use HTTPS, Google tokens are encrypted, and backups sent off the server are encrypted. The operator's diagnostic tools do not read conversation or message content.