Privacy Policy

Weather data

Niyavo can show local weather conditions in your daily Counsel sheet to help personalize your activity recommendations. When you open the Counsel sheet for the first time, your device asks permission to share your approximate location. If you grant it, your latitude and longitude are sent to our backend server for the sole purpose of looking up current weather and air quality from OpenWeatherMap.

Coordinates are rounded to ~1 km precision before any caching. We do NOT store your individual location data, do NOT associate weather lookups with your account, and do NOT share location data with any third party other than OpenWeatherMap (per their privacy policy).

You can deny or revoke location permission at any time in your device settings — Niyavo's other features continue to work normally without weather data.

Calendar Integration

When you connect your Google Calendar, Niyavo accesses only your free/busy time data. We use the calendar.freebusy scope, which means Google's API does NOT return event titles, descriptions, attendees, locations, organizer information, or recurrence patterns. We see only the time ranges when you are busy.

What we never read: Event titles · event descriptions · attendees · locations · organizer info · recurring event details · calendar names other than your primary calendar.

Where this data lives: Anonymized busy time ranges are cached on our backend (encrypted database hosted on Supabase) for up to 30 minutes per data point. Cache rows are RLS-scoped — only your account can read your busy ranges. OAuth refresh tokens are encrypted at rest using Fernet symmetric encryption.

How to disconnect: Open Niyavo → Profile → Calendar Integration → Disconnect. This revokes Niyavo's access at Google AND deletes your cached data from our backend.

Sub-processors