Privacy Policy

Who runs Solara

Solara is operated by Nathan Watkins, the controller of the personal information described here.

For privacy questions or requests, email contact@n8builds.dev.

What Solara collects

• Account details. When you sign in with Google, Solara receives your Firebase account identifier, name, email address and profile image.
• Location. The place you choose for forecasts, stored as a city name and coordinates rounded to two decimal places (about 1 km). If you use your device location, it is rounded the same way before it is sent anywhere or saved. Solara does not track your location in the background.
• Preferences. Skin profile, activities, saved places, calendar planning hours, appearance, notification time and other settings.
• Google Calendar availability, only if you connect it: the times you are busy, read in your browser for planning and not stored by Solara. Solara never sees event titles, descriptions, locations or attendees. If you add a planned activity to your calendar, Solara creates that one event on a calendar you own.
• Scheduled activities, for events Solara added to your calendar: the event's identifier, start and end time, time zone, title and link, and which of your activities it is for, so Solara can show and manage it on all your devices.
• Calendar feed and notifications, if you turn them on: a private feed token and your device's push notification registration.
• Subscription records, if you subscribe: plan, status and the Stripe customer and subscription identifiers. Card details go to Stripe and never reach Solara.
• Optional analytics, only if you allow it: pages visited (without query strings), approximate device and browser details, and feature usage.
• Error reports, when something breaks: the error message and where in the code it happened, the page address without its query string, your browser, device type, language and time zone, and the app steps just before the error. Email addresses, account identifiers, tokens and locations are removed in your browser before a report is sent, and no IP address is stored with it.
• Technical data. Hosting and security services process your IP address and browser details to deliver pages and prevent abuse.

How Solara uses Google user data

Solara asks for Google permissions only for the features below, and only when you use them.

• Google Sign-In (openid, email, profile): your Google account identifier, name, email address and profile image. Used to create and secure your Solara account and to show who is signed in. Stored in Firebase Authentication while your account exists.
• Google Calendar free/busy (calendar.freebusy), only if you connect a calendar: the start and end times of your busy periods. Used in your browser to schedule lower-UV windows around your commitments. Never stored on Solara's servers and discarded when you close the page. Solara cannot read event titles, descriptions, locations or attendees with this permission.
• Google Calendar events you create (calendar.events.owned), only when you choose to add a window to your calendar: Solara creates that event on a calendar you own and marks it as created by Solara. Solara stores the event's identifier, time, title and link of events it created, so it can show them as scheduled and let you open, move or remove them. To keep them up to date, Solara looks up only events it created; it does not read, change or delete any other event.

Solara does not sell Google user data, does not use it for advertising, and does not use it to train artificial intelligence or machine learning models. Google user data is not shared with anyone except the service providers listed below that run Solara's features, and only as needed for those features. No person at Solara reads your Google user data unless you ask for help with it, it is needed for security, or the law requires it.

You can disconnect Solara from your Google Account at any time in your Google Account connections, which stops all further access. Deleting your Solara account removes the Google account details Solara stores.

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

Why it is used, and the legal basis

• To provide the service you asked for (performance of a contract): forecasts, recommendations, syncing your settings, calendar feeds, notifications and subscriptions.
• With your consent: device location, Google Calendar access, push notifications and optional analytics. You can withdraw consent at any time, which does not affect processing that already happened.
• Legitimate interests: keeping Solara secure, preventing abuse and fixing problems, including the error reports above, which is why they do not depend on the analytics choice.
• Legal obligations: keeping payment records for tax and accounting.

Solara does not sell your information or use it for advertising.

Solara recommendations are planning estimates and are not medical advice.

Service providers

These providers process information on Solara's behalf or when you use a feature:

• Google Firebase (Google LLC): sign-in, database, hosting, cloud functions, push messaging and App Check, which uses Google reCAPTCHA to check that requests come from the real app. reCAPTCHA runs only after you sign in; the Google Privacy Policy and Terms of Service apply to it.
• Google Calendar API and Google Identity Services: only when you connect a calendar.
• Google Analytics: only after you allow analytics. Google signals and ad personalization are turned off.
• Open-Meteo: receives rounded coordinates to return forecasts, and the place names you type into a location search, as you type, to suggest matching places.
• OpenStreetMap Nominatim (OpenStreetMap Foundation): receives rounded coordinates when you use your device location, to find the nearest city name.
• Stripe: processes payments when subscriptions are enabled.
• Sentry (Functional Software, Inc.): receives the error reports described above, in the United States.

Some providers process data in the United States and other countries. Where required, transfers rely on the providers' standard contractual clauses or equivalent safeguards.

How long information is kept

• Account details and preferences: while your account exists.
• A guest plan (used without signing in): only in your browser, until you sign in (it then moves into your new account, or is removed if the account already existed) or clear your browser data.
• Scheduled activities: until you remove the event or it is deleted in Google Calendar; once an event ended more than 30 days ago, Solara deletes its record the next time you open the app; and always when you delete your account.
• Calendar availability: only in your browser for the current session; never stored by Solara.
• Push registrations: until you turn notifications off or delete your account.
• Payment records: as long as tax and accounting law requires, even after account deletion. Stripe keeps its own records under its privacy policy.
• Analytics: for the retention period set in Google Analytics, at most 14 months.
• Error reports: 30 days in Sentry.
• Hosting and security logs: for the periods set by Google Cloud.

Storage on your device

Solara keeps your preferences, a cached forecast, your theme, your analytics choice and which offers you dismissed in your browser's local storage so the app works quickly and remembers your choices. These are needed for the service and are not used for tracking.

If you use Solara without signing in, your plan (place, skin type and activity) is kept only in this browser and is never sent to Solara. Place search and forecasts still come from Open-Meteo and OpenStreetMap as described above.

Google Analytics cookies (_ga and _ga_*) are set only after you allow analytics and are deleted when you decline.

Your rights

Depending on where you live, you can ask to access, correct, export or delete your information, object to or restrict processing, and withdraw consent.

Use the Account data controls page while signed in to download a copy of your data or delete your account, or email contact@n8builds.dev.

You can disconnect Google Calendar at any time in your Google Account connections, rotate or revoke a calendar feed in Settings, and turn notifications off in Settings or your browser.

Deleting your account removes your Solara preferences, scheduled activities, calendar feed and notification registrations, and cancels an active Solara subscription. Events already in your Google Calendar stay there until you delete them.

You also have the right to complain to your local data protection authority.

Security

Solara uses access controls, encrypted connections, a strict content security policy and private capability tokens, but no internet service can guarantee absolute security.

Children

Solara is not directed to children under 13 (or the higher age required where you live) and does not knowingly collect their personal information.

Changes

Material changes will be reflected by updating the date on this page and, when appropriate, by an in-product notice.