Your Data & Privacy
Presently started with exploring what could be shown with readonly calendar access at random one-off snapshots in time. This is still the default "lite" workflow for the schedule-data-curious. It doesn't need to remember anything about you between visits, and it's frankly much less to maintain.
Eventually, "pro" was developed for more regular schedule checking & editing on the fly. That unavoidably means securely storing and managing user preferences + calendar authentication tokens. However, the more involved setup unlocks some powerful customisation features and UX upgrades.
Presently "lite" is just a static website
All your data is processed and stored in your browser.
There's no database copying your calendar details - it's all on whatever device you're using to access this site.
Your Google account provides a cookie for your browser to remember that you've already authorised Presently to read data from your calendar. For that reason, you need to enable 3rd party cookies on your browser for Presently to work properly (Google alone is that 3rd party.) You also have the option to store your toggled calendars preference in a 'toggledCalendars' cookie. For example, this saves you having to re-select your partner's calendar after refreshing the page.
Presently "pro" stores the bare minimum
- Auth token refresh data is stored so your calendar(s) can be read & edited without needing to re-authorize Presently with every action.
- Your Presently-specific preferences (e.g. event templates, toggled calendar ids etc.) have to be stored somewhere.
- No data is transferred to third parties.
Presently’s use and transfer of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
Google Calendar is a trademark of Google LLC.