Privacy policy

Selenio · last updated 26 October 2026

Selenio is a private, single-user automation. This policy explains what it does with data. It is short because it does very little.

What data is accessed

With the account owner's explicit consent, Selenio reads the Google Calendar that the owner has shared with it. The access is read-only: it can see event titles, times, locations and descriptions, and nothing else. It cannot create, edit or delete events, and it cannot read events on calendars that have not been shared with it.

How the data is used

Solely to work out which evenings are free, so that Selenio can suggest activities to the account owner. No calendar data is used for advertising, profiling, or any purpose other than that.

How the data is stored

Calendar data is not stored. It is read at the moment a suggestion is prepared and discarded afterwards. The only thing kept between runs is an OAuth refresh token, stored in a file readable only by the owner's account on the owner's own hardware (file permissions 0600).

Who the data is shared with

Nobody. Data is not sold, rented, published or shared with third parties. No analytics or advertising services are involved. Selenio runs on the owner's private hardware.

Third parties

Google provides the calendar API under its own privacy policy. Selenio's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Revoking access

The owner can withdraw access at any time at myaccount.google.com/permissions. Deleting the app there stops all access immediately, and the stored token becomes useless.

Data retention

No event data is retained. Removing the refresh token and any copies of it removes all remaining trace of the integration.

Contact

Questions about this policy: selenion@agentmail.to