Acropolis privacy policy

Acropolis is a new tab extension for Chrome and other Chromium browsers, made by Yury Molodtsov. It has no servers and no user accounts. It runs in your browser and talks directly to the services below. Nothing is sent to me or to anyone else.

Google Calendar

If you connect Google Calendar, Acropolis asks Chrome’s built-in Google sign-in, or Google’s own sign-in window where Chrome’s isn’t available, for read-only access to your calendars (calendar.readonly). It uses that access only to show your events for today and tomorrow on the new tab page.

• Event titles, times, locations, meeting links and calendar links go straight from Google to your browser.
• Chrome keeps the access token, as it does for any extension that uses Google sign-in. With Google’s sign-in window, Acropolis keeps the token in the browser’s session storage, which is held in memory and cleared when the browser quits, and remembers your Google account’s email address in local extension storage so it can sign in again to the same account. Acropolis keeps a copy of your events in your browser’s extension storage so the page loads instantly. That copy stays on your device.
• Acropolis never sends your calendar data anywhere else. It doesn’t sell it, use it for advertising, or use it to train AI models, and no person reads it.
• Acropolis can’t create, change or delete events.

Acropolis’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Readwise, Instapaper, Matter, Shiori and Todoist

If you connect one of these services, Acropolis stores its access token or API key in your browser’s extension storage and sends it only to that service:

• Readwise: fetches your daily review, and the first documents in your Readwise Reader inbox.
• Instapaper: fetches your newest saved articles.
• Matter: fetches the top of your Matter queue. Chrome asks for permission to reach api.getmatter.com when you connect.
• Shiori: fetches the newest unread links in your Shiori inbox.
• Todoist: fetches your tasks due today and overdue, and marks a task complete when you click its circle.

Apart from completing a Todoist task when you ask it to, Acropolis only reads from these services. It doesn’t save, change or delete anything else in them. Your tokens, highlights, saved articles and tasks aren’t sent anywhere else.

Other features

• Weather: what you type in the city search goes to Open-Meteo to find matching places. The chosen city’s coordinates, or your approximate coordinates with Current location, go to Open-Meteo for the forecast, or to wttr.in when Open-Meteo can’t be reached. With Current location, coordinates also go to BigDataCloud to look up your city’s name; if your browser can’t provide a location, BigDataCloud estimates one from your network address instead.
• Icons: the web addresses of your bookmark tiles, and the sites of the articles shown from Instapaper, Reader, Matter and Shiori, go to Google’s favicon service to fetch their icons. If Google has no icon for a bookmark tile, Acropolis loads it from that site directly.
• Reading list: if you turn it on, Acropolis reads your browser’s reading list to show the newest unread pages, and marks a page read when you open it from the card. The list never leaves your browser.
• Bookmarks bar: if you turn it on, Acropolis reads your browser’s bookmarks to show them on the page. They never leave your browser.
• Now playing: if you turn it on, Acropolis checks which tab is playing audio and reads the track title, artist and artwork that page publishes, so it can show them and pause or resume playback. It doesn’t read anything else on the page, and the information stays in your browser.
• Search: what you type goes to your default search engine, or to the AI service you chose, only when you submit it.

What stays in your browser

Your note, your wallpaper image, cached calendar events, daily review, the cached lists from Instapaper, Reader, Matter, Shiori and Todoist, and your tokens for those services stay in your browser’s local extension storage. Your settings and bookmark tiles sync through your browser account if browser sync is on.

How your data is protected

• No servers. Acropolis has no backend, database or analytics. Your Google data never reaches me or any third party, so there is no copy of it outside your browser and Google.
• Encrypted in transit. Every request to Google and the other services goes over HTTPS (TLS). Acropolis makes no unencrypted requests.
• Minimum access. Acropolis asks only for the read-only calendar.readonly scope, and requests only the event fields it shows: title, times, location, meeting link, calendar link and your response status.
• Token handling. Chrome’s built-in Google sign-in (chrome.identity) issues and stores the Google access token. Where Chrome’s isn’t available, Google’s sign-in window issues a token that expires within an hour, and Acropolis holds it only in session storage. Acropolis never sees your Google password.
• Isolated storage. Cached events are kept in the extension’s own storage, which Chrome keeps separate from websites and other extensions. Only Acropolis’s new tab page can read it.
• Locked-down code. All of Acropolis’s code ships inside the extension and runs under Chrome’s Manifest V3 content security policy, which blocks remote code. Event text is displayed as plain text, never run as code.

How long your data is kept

• Acropolis fetches only today’s and tomorrow’s events. Each refresh, every five minutes while the page is open, replaces the cached copy, so earlier days are dropped automatically and no history builds up.
• The cache stays on your device until you disconnect Google Calendar, Google access is revoked, or you uninstall the extension. Each of these deletes it, as described below.
• Because no Google user data is ever sent to me, there is nothing for me to retain or delete on my side.

Removing your data

• To disconnect Google Calendar, open the Acropolis settings and click Disconnect. Acropolis asks Google to revoke the token and deletes the token, your account’s email address and the cached events at once. You can also remove access at myaccount.google.com/connections; Acropolis then deletes the cached events the next time it loads online.
• To remove a Readwise, Instapaper, Matter, Shiori or Todoist token, open the Acropolis settings and click Disconnect next to the service. Acropolis deletes the token and the cached list.
• Uninstalling the extension deletes everything it stored on your device.

Contact

Questions about this policy: yury@molodtsov.me