This policy explains what personal data we collect and why, for AgentsPoppy (agentspoppy.com) and the apps we operate ourselves, including MailPoppy. We keep it deliberately small: we collect the minimum needed to run your account and take payment. It also says what our make-your-assistant studio does with data from your Google account, when you allow it.
Who we are
The data controller is Olly Digital, established in Amsterdam, the Netherlands (registered with the Dutch Chamber of Commerce, KvK no. 68745532). For any privacy question or request, contact us at support@agentspoppy.com.
The short version
We collect account and billing details — nothing more than we need to provide the service and charge for it.
For our BYO-AWS apps (like MailPoppy), your content lives in your own AWS account. Your emails, mailboxes, files and cloud resources never reach us — we can't read them.
If you let the studio use your Google account, what it makes and remembers lives in your own Google Cloud. Data from your Google account never reaches us.
We don't sell your data, and we don't use advertising or tracking cookies.
What we collect, and why
Account data
When you sign in (for the developer dashboard or admin tools) we receive your email address and basic profile from your chosen sign-in provider (Google). This is a separate sign-in from the studio’s, which is described under “Data from your Google account” below.Legal basis: performance of our contract with you.
Billing data
When you buy something, our payments provider Stripe processes your name, email, billing address, country, any VAT/tax identifier, and the transaction. Card numbers are handled by Stripe — we never see or store them. We keep the resulting invoice/transaction records. Legal basis: performance of our contract, and our legal obligation to keep tax records.
Purchase & entitlement records
A purchase creates a small record: an opaque buyer identifier, which product was bought, what it applies to (for example a domain name), and the subscription's status. Legal basis: performance of our contract.
Technical data
Like any website, our hosting logs technical information such as your IP address, browser/device type and requests, and we use strictly necessary cookies/tokens to keep you signed in and to protect the service. Our own analytics, TrafficPoppy, counts page views without cookies or local storage. It records the page’s address, the site you came from, your screen width, the family of your browser and operating system, and sometimes your country. It turns your IP address and full browser details into a one-way code that is replaced within a week, and stores neither. It sends nothing at all if your browser asks sites not to track you (Do Not Track or Global Privacy Control). Legal basis: our legitimate interest in running, securing and debugging the service.
What we do not collect
Your app content. With MailPoppy and other BYO-AWS apps, your mail and cloud resources stay entirely inside your own AWS account. We provision them there on your instruction; we do not receive, store, or have standing access to their contents.
Your assistant from the studio.What you choose on the make-your-assistant page (a face, a voice, a name, and the name you tell it) is kept in your own browser’s storage, on your device. It is never sent to us; clearing the site’s data in your browser, or “Start again”, removes it from the browser. If you give your assistant a home in your Google Cloud, your name is kept there too, as described under “Data from your Google account” below.
No advertising identifiers, no cross-site tracking, no sale of personal data.
Data from your Google account
This section covers the data our apps get from your Google account when you allow it — what Google calls Google user data. The place in our products that asks for it is the make-your-assistant studio at agentspoppy.com/crewpoppy/studio, which is part of AgentsPoppy: Google’s screen names the app “AgentsPoppy”. The studio asks only when you tap the button for it. Google shows each request on its own screen, and you can say no. No released version of the AgentsPoppy desktop app or the CrewPoppy phone app signs in to Google yet; this section will cover them before one does. Signing in to our developer dashboard is a different sign-in, described under “Account data” above.
What the studio asks for, and why
Your email address(Google’s “openid” and “email” permissions). The studio shows which Google account your assistant’s home was made with, and will not use a later permission given by a different account.
Google Cloud(the “cloud-platform” permission), when you tap the button that gives your assistant a home. Google’s permission is broad: for the hour it lasts, it lets the page see, change and delete anything in your Google Cloud. Google has no narrower permission that can make a project. This is everything the studio does with it. It looks for a project already made for your assistant, by the labels we give it. If there is none, it makes one, called “Poppy MemoryPoppy” after MemoryPoppy, our memory app, whose way of keeping memories it follows. Google makes you the owner of the new project, as it does for any project you create. The studio switches on Firestore, Google’s database, in that project’s free tier, with no billing account. It makes one database there, in Europe or the United States depending on your time zone (or uses the one already there), and writes two things into it: a small install record and your name. Later, when you ask to hear your morning, it reads your memories back from that database. The studio touches no other project, deletes nothing, and creates no key, service account or permission for anyone, us included.
Your calendar(the “calendar.events.owned.readonly” permission, which Google’s screen shows as “See the events on Google calendars you own”), asked for separately, when you tap the button that lets your assistant read it. It reads events only: it cannot see calendars other people share with you, and it cannot change anything. The studio reads your primary calendar only, and only when you tap: the past 30 days and the next 60 the first time, and on any later reading only what has changed since. For each meeting it keeps the title, the description, the start and end, whether it is all day, the place, the organiser’s email address and whether you organised it, the link to the event, how many other people are invited, and Google’s ids for it. For each other person in a meeting, it keeps their name and email address as your calendar shows them, so your assistant can tell you who you are meeting; it does not do this for meetings of more than 30 people. It also keeps a marker from Google of where it read up to. It does not copy meetings you had already declined, or out-of-office, focus-time, working-location and birthday entries. It never changes your calendar.
That is everything the studio asks Google for. It never asks for your mail, your files or your contacts.
What it is used for
Only for what you see in the studio: giving your assistant a home, remembering your name, and telling you your day. When you ask to hear your morning, the studio reads your memories back and puts the day together in your browser, with ordinary code, not an AI model, and shows it on the page. It is spoken only when you tap to hear it, by your browser’s own speech. Some browsers offer online voices as well as voices on your device, and the studio’s voice list does not yet say which is which; the voice it picks first can be an online one. With an online voice, your browser sends the words — which can include meeting titles, people’s names or email addresses, and places — to its maker’s speech service, under that maker’s own terms. If you would rather it did not, read the day on the page instead of tapping to hear it.
Where it is kept
In your own Google Cloud.Your name, your meetings and the people in them are kept as memories in the database in your project, together with the marker of where the calendar was read up to. This copy is made only when you tap to allow it; it is your assistant’s memory of you, kept in your project and nowhere else, and you can delete it at any time, as described below. We have no access to it.
In your browser.Next to your choices in the studio, your browser’s storage keeps which Google account and project your assistant’s home is in, and how many meetings and people were last read. Nothing from the calendar itself.
In the open page, briefly.The keys Google gives the studio (access tokens) are held only in the page’s memory. They are never saved, they are gone when you close the tab, and each one stops working within an hour. Each key opens only what it was asked for: the calendar key reads your calendar and nothing else, and the Google Cloud key is not used to read it. There is no long-lived key: to do anything later, the studio has to ask Google again.
Who receives it
Data from your Google account goes to these places, and no others:
Google.Your browser sends each request straight to Google’s own services, which hold your account, your calendar and your project.
Your own Google Cloud project, where the memories are written and stay.
Your browser maker’s speech service, only if you tap to hear your morning in an online voice, as above.
AgentsPoppy never receives it.Our servers never see your Google keys, your calendar or your memories. From the studio we get only what we get from any page on this site: the requests in our hosting logs, and a page view in TrafficPoppy, our own analytics, which records the page’s address and never anything you do on it. Google also counts some of the studio’s requests against our own Google Cloud project, so we can see how many requests were made, never what they carried.
We do not transfer or disclose your information to third parties for purposes other than the ones described here. We hold none of it, so we have none to sell, share or hand over.
What we never do with it
We never sell it, and we never use it for advertising.
We never pass it to data brokers or information resellers, and never use it to decide credit-worthiness or for lending.
We do not use data obtained through Google Workspace APIs, such as the Google Calendar API, to develop, improve or train generalized or non-personalized AI and/or ML models, and we never transfer it to anyone for that. The studio uses no AI model to read, sort or summarise it.
No one at AgentsPoppy reads it. We have no access to it.
How it is protected
Every request goes to Google over an encrypted connection (HTTPS). The keys stay in the page and are never saved, by us or by the page. Your memories sit in your own project, where Google encrypts them on disk. The studio gives no one else access to that project, us included.
How long it is kept, and how to remove it
We keep none of it, so there is nothing for us to delete. What is kept is yours, and stays until you remove it:
Stop all access at any time: remove AgentsPoppy at myaccount.google.com/permissions. Google then gives the studio no new key until you allow it again, and a key still open in a tab stops working within the hour at the latest.
Delete the memories. They stay in your project until you delete them, even after you stop access. You can delete single memories in the Firestore part of the Google Cloud console, or delete the whole project “Poppy MemoryPoppy” there; Google deletes a project fully 30 days later. The studio itself deletes nothing — it was built with no way to — so it cannot do this for you.
The studio does not keep your memories up to date by itself. It reads your calendar only when you tap. A meeting that changes, or that you decline, after the last reading stays in memory as it was then. When a later reading finds a meeting cancelled, it marks that memory as gone and drops its details, but keeps its title and start time; the people from that meeting stay in memory with their names and email addresses until you delete them.
Clear the browser.“Start again” in the studio, or clearing this site’s data in your browser, removes what the browser keeps. It does not touch your Google Cloud.
The keys are gone when you close the tab, and stop working within an hour anyway.
If this changes
Before we use data from your Google account in a new way, or in another app, we will update this section and ask for your permission again.
We rely on a small number of processors, each under a data-processing agreement:
Stripe — payments and billing.
Google (Firebase) — authentication, database and hosting for our own services. Nothing the studio reads from your Google account goes there.
Where a processor operates outside the European Economic Area (for example in the United States), transfers are covered by the appropriate safeguards, such as the EU Standard Contractual Clauses or an adequacy decision. Your own AWS account and your own Google Cloud are yours, not our processors.
How long we keep it
We keep account and purchase data for as long as you have an account with us, and afterwards only as needed to meet legal obligations — in particular, billing and tax records are retained for the period Dutch law requires (currently seven years). Technical logs are kept for a short period.
Your rights
Under the GDPR you have the right to access, correct, delete, restrict or port your personal data, and to object to certain processing. To exercise any of these, email support@agentspoppy.com. We hold no data from your Google account; “Data from your Google account” above says how to remove it yourself. You also have the right to lodge a complaint with the Dutch data protection authority, the Autoriteit Persoonsgegevens.
Buying third-party apps
Some apps in the AgentsPoppy directory are made and sold by independent developers. When you buy one, that developer is the seller and is responsible, as controller, for how they handle any data you give them; we act only as the payment facilitator. Their own privacy terms apply to that relationship.
Changes
We may update this policy; the "last updated" date above always reflects the current version. Material changes will be highlighted where we can.