Privacy Policy

Last updated: September 21, 2026

This Privacy Policy explains what information POPO processes, why, how long it is kept, and the choices you have. It applies to the POPO web application hosted at popsipopolo.com. POPO is operated by an individual operator; questions can be sent to daniel.czegledi@protonmail.com.

1. What POPO is

POPO is an AI assistant web application. You can chat with it, ask it to search the web, get weather, places and route information, and attach files (for example text, Markdown, PDF, Word, Excel/CSV and PowerPoint files) so that POPO can read, search, create, edit and export documents for you. It is a private application built for the personal use of two authorized adult users; it is not a public or commercial service, and access to the application itself requires the access password.

2. Information POPO processes

• Conversations. The messages you send, POPO's answers, the conversation title, and limited metadata such as which tools were used and the sources cited in an answer.
• Files you attach. The files you upload to a conversation, their file names, and basic metadata such as type and size.
• Files POPO creates or edits for you. New or edited documents, spreadsheets and presentations, together with the version history POPO keeps so that edits can be tracked and repeated requests are not applied twice.
• Location, only when your browser allows it. If you grant your browser's location permission, POPO may use your approximate device location to answer weather, places and route questions. If you deny the permission, no device location is sent.
• Technical and operational data. Server logs and performance measurements (for example timings, error types and which service produced an answer) used to keep the service running. POPO's performance telemetry is designed not to contain the text of your questions or answers.

POPO has no public registration and does not ask you to create an account. It does not collect your name, email address or payment information in order to use the application; the access password is what grants access.

3. Google Workspace and Google API data

Which Google data POPO accesses

POPO's Google Workspace integration runs through a dedicated Google account operated for POPO. Using that account, POPO requests the following Google API permissions:

• Google Drive — files created by the app (drive.file): to upload a file you attached so Google can convert it into a Google Docs, Sheets or Slides file, to export that file back (for example as DOCX, XLSX, PPTX or PDF), and to delete it afterwards. This permission only covers files POPO created or opened; it does not give POPO access to other Drive files.
• Google Sheets: to read cell values, formulas and sheet structure of a spreadsheet you attached or asked POPO to create, and to write or clear cell values when you ask POPO to change it.
• Google Docs: to read the text and structure of a Word document you attached and to apply the text edits you ask for.
• Google Slides: to read and replace text in a presentation you attached, within the Drive file access described above.

POPO does not ask its users to sign in with their own Google account, and it does not access anyone's personal Gmail, Calendar, Contacts or Drive contents.

Why POPO accesses this data

Google Workspace data is accessed only to perform the file task an authorized user asked for in the conversation — reading or searching a document, spreadsheet or presentation, making an edit, or exporting a copy — and to show the result. It is used only as far as that requested function needs, and it is never used for advertising, for credit or lending decisions, or to train generalized AI or machine learning models at POPO.

Content that is needed to fulfil the request — which can include text read from your Google Workspace files — is passed to the AI model that prepares POPO's answer, because that is how POPO answers questions about a file. This transfer happens only where it is necessary for the requested functionality. Which providers can receive it, and on what basis, is described in section 6.

Temporary Google Docs, Sheets and Slides copies

Some operations can only be done by Google's editors. For these, POPO uploads a copy of your attached file to Google Drive, where Google converts it into a native Google Docs, Sheets or Slides file. These converted files are working copies: the file kept by POPO for your conversation remains the authoritative version, and edited results are exported back into it.

These temporary provider-side copies exist only to perform the requested functionality. A working copy is reused while the conversation exists, so that repeated requests do not create duplicates. When the conversation is deleted, its working copies enter POPO's cleanup queue for deletion from Google Drive. Deletion is attempted straight away, but it is not instantaneous: if Google is temporarily unreachable, the deletion request is kept in the queue and retried until it succeeds.

4. File reading, creation, editing and export

• Reading and searching. Text-based files are read and searched on POPO's server. For some searches over long documents, POPO uses the Google Gemini API's File Search feature, which indexes the text of attached files in a search store dedicated to that conversation. The store is deleted together with the conversation.
• Creating files. New documents, spreadsheets and presentations are created for the conversation and offered to you for download.
• Editing files. Edits are applied to a working copy as described above and saved as a new version of the file; earlier versions are kept as part of the conversation's file history.
• Exporting. You can export files, for example as PDF. An export is saved as a new file in the conversation.

5. Storage on POPO's server

Conversations, uploaded files, files POPO created, their version history and the identifiers that link a file to its Google working copy are stored on the server that runs POPO. Files and their metadata belong to the conversation they were attached to, and POPO only serves them within that conversation.

6. How information is shared

POPO does not sell your information and does not share it with advertisers. It is not, however, a self-contained system: to answer you, content from your conversation and from the files you work with — including content read from Google Workspace files — is sent to external providers and processed on their systems. POPO sends the minimum data needed for a request to the following service providers:

• Google — the Gemini API, which is the primary AI model POPO uses (answer generation, image and document understanding, and File Search) and which therefore receives the conversation content needed for your request; Google Drive, Docs, Sheets and Slides (the file operations described above); and Google Maps Platform services (places, routes and weather, which may receive your approximate location when you have allowed it).
• Z.ai (GLM models) — the fallback AI model provider, used to prepare an answer when the primary Gemini model is unavailable. When the fallback model is used, the conversation context needed for the answer, which can include content read from your files, is sent to Z.ai and processed there.
• Exa — a web search provider. It receives search queries derived from your question, not your files.

These providers process the data under their own terms and privacy policies, including their own retention practices; POPO cannot and does not promise that a provider keeps nothing. Information may also be disclosed if required by law. Google Workspace user data is transmitted to these providers only where that is necessary to perform the specific functionality an authorized user requested, to comply with applicable law, or as otherwise permitted by the Google API Services User Data Policy.

The statement that POPO does not use Google Workspace user data to create, train or improve generalized AI or machine learning models is about POPO itself. It is not a statement about what these independent providers do with data sent to them under their own terms.

7. Retention and deletion

• Conversations, attached files and created files are kept until the conversation is deleted. POPO does not currently delete conversations automatically after a fixed period.
• Deleting a conversation in POPO deletes its messages, its attached and created files, and their version history from POPO's database and file storage, and places the conversation's Google working copies and File Search store in the cleanup queue for deletion at Google, as described in section 3. Because that queue retries when a provider is temporarily unavailable, provider-side deletion follows the cleanup workflow rather than happening at a guaranteed instant.
• Data already processed by a third-party provider is subject to that provider's own retention practices.
• To request deletion of any information associated with your use of POPO, contact daniel.czegledi@protonmail.com.

8. Security

POPO is password-protected: the application and its data interfaces require the access password, which is what keeps this private application closed to everyone but its two authorized users. POPO also uses measures such as per-conversation ownership checks before a file can be read, edited or downloaded, and keeping Google OAuth credentials only on the server — they are never sent to the browser, shown to the AI model, or written into logs. No method of storage or transmission is completely secure, and POPO cannot guarantee absolute security.

9. Your choices and revoking Google access

• You can choose not to attach files or not to use file features.
• You can delete any conversation, which removes its data as described in section 7.
• You can deny or withdraw your browser's location permission at any time.
• If you have granted POPO access to a Google account, you can revoke it at any time from your Google Account's Third-party apps & services page. Revoking access stops further Google API access; files already created in that Drive remain there until they are deleted.
• You can contact us to ask about, or request deletion of, information related to your use of POPO.

10. Adults only

POPO is used only by its two authorized adult users. It is not directed to and is not intended for anyone under 18, and it is not made available to children.

11. Changes to this policy

This policy may be updated when POPO changes. The "Last updated" date at the top of this page shows the latest revision. Material changes to how Google user data is used will be reflected here before they take effect.

12. Contact

For privacy questions or requests, contact: daniel.czegledi@protonmail.com.

See also the Terms of Service.