Privacy Policy

Daysolvily (“the Service”, app.daysolvily.com) is operated by Tech Solvily LLC, a Virginia limited liability company (“we”, “us”), 701 E Franklin Street, Suite 105, Richmond, VA 23219, USA. This policy explains what personal data we process, why, and your rights over it. Questions: support@techsolvily.com.

Daysolvily is currently in open beta: anyone can create an account at app.daysolvily.com/signup. We describe the data handling of the beta product; material changes will be reflected here.

1. Who we are (data controller)

Tech Solvily LLC is the controller of your personal data. We are based in the United States; this policy is governed by the laws of the Commonwealth of Virginia, without prejudice to the mandatory rights you may have under CCPA (California), GDPR (EEA/UK), or LGPD (Brazil) — see “Your rights”.

2. Data we collect and why

Account. You sign in with Google. We receive and store your email address and name to identify your account. Stored in our database (Supabase), isolated to your account.

Google Calendar (read-only). Calendar access is not part of signing up: you grant it separately, if and when you choose to connect a calendar, and you may connect more than one Google account. With that authorization (scope calendar.readonly), we read your calendar events — title, start/end times, location, description, and attendees (name, email, response status) — to display your schedule alongside your tasks. Calendar events are read live and shown to you; we do not store your calendar events in our database. The Google OAuth tokens needed to read your calendar are stored encrypted at rest and used only to fetch your events on your behalf. You can revoke this access at any time from your Google Account.

Limited Use of Google user data. Daysolvily’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google Calendar data for advertising, do not sell it, do not transfer it to others except as necessary to provide the Service or as required by law, and do not use it to develop, improve, or train generalized AI or ML models.

Português (tradução de cortesia; em caso de conflito, prevalece a versão em inglês acima). O uso e a transferência, pelo Daysolvily, de informações recebidas das APIs do Google para qualquer outro aplicativo obedecerão à Google API Services User Data Policy, incluindo os requisitos de Limited Use (uso limitado). Não usamos dados do Google Calendar para publicidade, não os vendemos, não os transferimos a terceiros exceto quando necessário para prestar o Serviço ou quando exigido por lei, e não os usamos para desenvolver, aprimorar ou treinar modelos generalizados de IA ou de aprendizado de máquina.

Notion and HubSpot (with your authorization). If you connect Notion or HubSpot, you authorize us — via each provider’s OAuth — to read your tasks (titles, due dates, status, priority, and similar fields) and to write back changes you make in Daysolvily (marking a task done, changing its due date, creating a task). We do not copy your Notion/HubSpot task content into our database. We store only the minimum needed to track your time: the external task’s identifier plus your own time metadata (estimated minutes, scheduled time blocks, and focus sessions, which may include a snapshot of a task title). Your Notion/HubSpot OAuth tokens are stored encrypted at rest and are revocable by disconnecting the integration or from the provider.

Content you create in Daysolvily. Native tasks, habits, inbox items, focus-session notes, and similar content you enter are stored in our database, isolated to your account by row-level security.

Voice input (optional). If you use voice capture, the audio you record is sent to our server and transcribed by Groq; the resulting text is interpreted by Anthropic (Claude) to extract task details; and, for spoken replies, text is sent to ElevenLabs to generate audio. Your audio is not stored — it is passed to the transcription provider and discarded. If these services are unavailable, the app falls back to your browser’s built-in speech features.

Weather (optional). If enabled, your approximate location (latitude/longitude) is sent to weather services (wttr.in and BigDataCloud) to show local conditions. Not stored.

Security & usage logs. To operate and secure the Service we log access events: a masked IP address (e.g. 203.0.xx.xx), approximate city/country (derived from the IP via ipapi.co at the time of access), browser user-agent, device type, and the path accessed. We do not retain your full IP address.

Error monitoring. We use Sentry to capture application errors and a small sample of performance traces. Sentry is configured to not send personal data by default.

Bug reports. If you submit a bug report, its text — and your email address — are sent to Anthropic (to auto-classify the report) and recorded in our internal Notion workspace so we can act on it.

3. Service providers (subprocessors)

We share personal data only with providers that process it on our behalf to deliver the Service: Google (sign-in, Calendar), Supabase (database/storage, US), Vercel (hosting, US), Notion and HubSpot (only if you connect them), Groq, Anthropic, and ElevenLabs (voice features), Sentry (error monitoring), ipapi.co (IP geolocation), wttr.in and BigDataCloud (weather), and GitHub (private backups — see below). We do not sell your personal data.

4. Where your data lives, and backups

Your account data is stored in Supabase (US region) and served via Vercel (US). Each user’s data is isolated at the database level by row-level security. We keep a daily backup of your app content (tasks, habits, inbox, focus sessions) in a private repository. Backups exclude access logs, viewer-session logs, and OAuth tokens. Your data is processed and stored in the United States. If you access the Service from outside the U.S., you acknowledge that your data is transferred to and processed in the U.S., where data protection laws may differ from those of your jurisdiction.

5. Security

We protect your data with per-user database isolation (row-level security), OAuth tokens encrypted at rest, encrypted transport (HTTPS), and least-privilege access controls. No method of storage or transmission is perfectly secure, but we work to protect your information and to limit what we collect.

6. Retention

We keep your account data for as long as your account is active. Items you delete go to a trash and are permanently removed after 30 days. Access and session logs are retained only as needed for security and troubleshooting. You may request deletion of your account and associated data at any time.

7. Your rights

We process your data to provide the Service (performance of our contract with you) and, for optional integrations and voice features, on the basis of your consent, which you may withdraw at any time.

Depending on where you live, you have rights over your personal data. We honor these rights for all users regardless of location:

CCPA (California): the right to know what we collect, the right to delete, and the right to opt out of the sale of personal information. We do not sell personal information.

GDPR (EEA/UK) and LGPD (Brazil): the rights of access, rectification, erasure, restriction, portability, and objection, and the right to withdraw consent (for example, by disconnecting an integration or revoking access in your Google Account).

To exercise any of these, email support@techsolvily.com. We will respond within the timeframes required by applicable law.

8. Children

Daysolvily is not directed to children under 13 (or under 16 where applicable), and we do not knowingly collect their data.

9. Changes to this policy

We may update this policy as the Service evolves. We will change the “Last updated” date above and, for material changes, provide a more prominent notice.

10. Contact

Tech Solvily LLC — 701 E Franklin Street, Suite 105, Richmond, VA 23219, USA. support@techsolvily.com