Privacy policy
Updated
Who we are
In short: Ruslo is a personal task manager; write to us at hello@ruslo.day.
Ruslo is a personal task manager at https://app.ruslo.day. The service is run by Mazurenko Danyil, sole proprietor (FOP) registered in Ukraine. For questions about your data, write to hello@ruslo.day.
The main points
In short: you see your tasks, and AI sees them only if you connected it yourself.
- Ruslo's data is stored in Ukraine.
- Ruslo has no language model of its own.
- AI sees your tasks only when you yourself have connected Claude or another MCP client.
- Areas hidden from AI are not visible to any MCP tool.
- Analytics receive neither the content of your tasks nor personal data.
- You can export all your data as one file at any time.
What data we store
In short: your email, your settings and everything you write in Ruslo.
- Email, time zone, language, interface theme and accent, plan and sign-up date.
- Your password, if you set one — only as an Argon2 hash.
- Everything you write in Ruslo: areas, groups, projects, headings, tasks with notes and checklists, tags, repeats, reminders, the backlog, “My meetings”.
- Your work profile, day plan, plan blocks and focus sessions.
- Access rules for Claude, Claude's proposals and the change log.
- Events of connected calendars: title, start, duration, repeat, “all day” and “busy/free”.
- We do not store the description, location or attendees of events.
- Service records of sign-in sessions, connected MCP clients and their write calls.
- Push notification subscriptions of your devices.
Where the data is stored
In short: on a server in Ukraine; outside Ukraine the data passes only through the services named here.
- Hosting: a server in Ukraine.
- The app server and the PostgreSQL database with the main copy of your data run there.
- The MCP server
mcp.ruslo.dayruns on the same server. - A copy of your data is also kept in your browser, so Ruslo works offline (see “Cookies and browser storage”).
Outside Ukraine your data passes only through these services:
- Cloudflare — delivers the site and the app, forwards the app's requests to the server (with your data and cookies), sends the emails with codes and forwards the emails to hello@ruslo.day.
- PostHog (EU Cloud region) — errors and a few events without task content (see “Analytics and errors”).
- Google — only if you sign in with Google or connect a Google calendar.
- Anthropic — only through your own Claude, if you connected it.
- The push service of your browser — reminders with the task title, if you turned notifications on.
- Your Obsidian vault — if you connected it, a copy of the data goes wherever it is hosted.
How we protect data
In short: HTTPS only, tokens and sessions only as hashes, calendar keys encrypted.
- The site and the api work only over HTTPS, the api with HSTS.
- Sessions, OAuth tokens for Claude and one-time card tokens are stored only as hashes.
- ICS links and Google tokens are encrypted with a separate key.
- Server secrets live only in environment variables on the server.
Sign-in and sessions
In short: sign in with a code from email, a password or Google; we count failed attempts.
- You can sign in with a code from email, with email and password, or with Google.
- The code from email has 6 digits, lives 10 minutes and allows 3 attempts.
- There is no password reset by email: sign-in with a code replaces it.
- A password must be at least 10 characters long.
- To protect sign-in, we count failed attempts and code requests per email address and per IP address.
- A browser session lasts until you sign out; the session cookie is renewed at most once a day and expires after up to 400 days.
Emails from Ruslo
In short: we send only emails with codes; Cloudflare delivers them.
- Ruslo's emails are sent by Cloudflare Email Service from
hello@ruslo.day. - For now Ruslo sends only emails with a code: to sign in or to confirm an action in the account.
- Cloudflare forwards emails sent to hello@ruslo.day to the operator, who replies from their own mailbox.
- Neither the address nor the code appears in server logs or in PostHog.
- The reply to a code request is the same for a known and an unknown address.
Claude and other MCP clients
In short: Claude sees and changes only what you allowed, and every change it makes can be undone.
- You connect Claude to Ruslo yourself, through OAuth 2.1 with PKCE.
- When connecting, you see which access scopes the client asks for: read the profile, tasks, calendar, change tasks, the plan, propose changes and so on.
- You decide what exactly Claude may change: the presets “Careful”, “Normal”, “Trust” or the “Detailed” table.
- Every action has a level: “allowed”, “propose” or “forbidden”.
- Only you accept or reject Claude's proposals.
- Only a person accepts the day plan; the model cannot accept it with any tool.
- Every change by Claude is written to the log, and you can undo it within 60 days.
- When plans appear, the log will be kept for 14 days on the free one.
- More than 20 tasks, projects or headings at once — only as a proposal.
- Too many changes per minute pause Claude's writes; only you can lift the pause.
- An area hidden from AI is not visible in any MCP read; Claude sees its blocks in the plan as “Busy”.
- A connected client is shown in the “Assistant” settings, and access is revoked with one tap.
- An access token lives 1 hour, a refresh token 30 days.
- What Claude reads — tasks, the plan, the review, the log, calendar events (except hidden areas) — is passed to Anthropic through your own Claude.
- How Anthropic processes this data is set by your terms with Anthropic.
“Tidy” in the backlog
In short: this feature is off for now, and backlog text goes nowhere.
- “Tidy” can suggest a clearer wording for a backlog entry: to do so, the Ruslo server sends the entry's text to the Claude API (Anthropic) with Ruslo's key, not with your Claude.
- For now the feature is off: there is no key on the server, so nothing is sent.
Google: sign-in and calendar
In short: Google is involved only if you sign in with it or connect a calendar yourself.
Sign-in with Google
- Ruslo asks Google only for
emailandprofile. - We do not store Google sign-in tokens.
- A Google account with the same verified email is joined to the existing Ruslo account.
Reading your calendar
- Connecting a calendar is a separate consent with
calendar.readonlyaccess. - We read events only from the calendars you chose; after consent only the primary one is on.
- We read a window from yesterday to 30 days ahead.
- Events are needed so the day plan does not put tasks on busy time.
- Through MCP your Claude sees these events if you gave it calendar access.
The “Ruslo” calendar (focus blocks)
- If you turn on focus blocks, Ruslo asks for
calendar.app.createdaccess. - With it, Ruslo sees and changes only the calendars it created itself, not yours.
- Ruslo creates the “Ruslo” calendar and writes the blocks of the accepted plan there, with task titles.
- Tasks of hidden areas are written as “Busy”, without a title.
- Ruslo does not touch your own events.
Storage and revoking
- The Google refresh token is stored encrypted.
- Tokens, email and event titles do not go into server logs.
- “Disconnect Google” revokes the token at Google, removes the “Ruslo” calendar and moves the calendars and events to the trash.
Limited Use
Ruslo's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
ICS subscriptions
In short: Ruslo only reads a calendar added by an ICS link, and encrypts the link.
- You can add a calendar by an ICS link; Ruslo only reads it.
- The link is stored encrypted.
- We store the same event fields as for Google.
- There are no Microsoft calendars through Microsoft sign-in for now.
Notifications
In short: reminders with the task title go through the push service of your browser.
- Reminders come through the push service of your browser.
- A reminder contains the task title.
- An account has up to 10 push subscriptions; a new one replaces the oldest.
Obsidian vault
In short: if you connected your vault, the copy of the data in it is yours.
- If you connect your Obsidian vault, Ruslo writes a full copy of the account's data there, into the
ruslo/folder. - We store the vault's address and access code encrypted.
- The copy in the vault is yours.
Telegram and email to the Inbox
In short: there are no such channels for now.
- For now Ruslo does not take tasks from Telegram or forwarded emails.
Analytics and errors (PostHog)
In short: only errors and a few events, without task content, email or location.
- Errors and a few app events go to PostHog, in the EU Cloud region (
eu.i.posthog.com). - The PostHog library is loaded from PostHog's server only if a project key is set on the server.
- The app sends only errors, page speed (web vitals) and these events: a failure of local saving or of starting the sync, opening a “Help” article, an introduction step, a step of signing in with a code and the result of an export.
- There is no automatic collection of clicks, session recordings, heatmaps or page views.
- Before sending, we remove email addresses, quoted text, field values and URL parameters from errors.
- Location by IP is turned off.
- Events are tied only to the internal account id, never to the email.
- The server sends only the error type and stack, without the message text, request bodies, variables, cookies or headers.
- Analytics does not store your IP address.
Cookies and browser storage
In short: sign-in cookies, a random PostHog id and a local copy of your data; no advertising cookies.
Cookies
__Host-ruslo_session— the sign-in session; HttpOnly, Secure, SameSite=Lax.__Host-ruslo_csrf— protection against forged requests; Secure, SameSite=Lax.- Both cookies belong to
app.ruslo.day, because requests to the api go through the same domain. - If PostHog is on, its library keeps a random id and a session id in a cookie and in localStorage named
ph_<project key>_posthog. - Ruslo sets no advertising cookies.
Local storage (localStorage)
- Appearance:
ruslo:style,ruslo:theme,ruslo:accent,ruslo:theme-pending,ruslo:accent-pending. - Who signed in last (
ruslo.user: id, email, time zone) — to open Ruslo offline; erased on sign-out. ruslo.onboarded— short hashes of the emails of accounts that went through the introduction on this device.- Recent quick find tasks (
ruslo:quickFind:recent) and backlog drafts (ruslo.backlog.draft…) — erased on sign-out. - State of screens and the device:
ruslo:last-route,ruslo:closed-day,ruslo:focus,ruslo:focus-day,ruslo:matrix,ruslo-collapsed-groups,ruslo-area-fold,ruslo.onboarding.example.<id>,ruslo.singleKeys,ruslo.haptics,ruslo:push:*. - For the life of a tab (sessionStorage):
ruslo:quickFind:reloaded.
IndexedDB and cache
- The
ruslo-<account id>database — a local copy of your data and the queue of changes not yet sent. - It is deleted when you sign out of the account in the settings.
- The service worker caches only the app's files: code, styles, icons, the font and the page shell.
- The Onest font is on our server, not on Google Fonts.
How long we keep data
In short: the change log for 60 days, the trash for 30 days.
- The change log — 60 days.
- The trash — 30 days, then what was deleted is gone for good.
- A Claude proposal expires after 7 days; one tied to a date — at the end of that date.
Export and deletion
In short: you can take all your data with you as one JSON file.
- Export — one JSON file, straight from the settings.
- It contains the profile, settings, all your records, access rules, contexts, the backlog, the trash and the log for 60 days, without hashes and tokens.
- Export needs a recent sign-in (within 15 minutes).
- Account deletion in Ruslo itself is not turned on yet.
- Until then, write to hello@ruslo.day and we will delete the account by hand.
Your rights
In short: you view, change and take your data in Ruslo itself.
- You can view, change, export and delete your records in Ruslo itself.
- We do not sell your data and do not show ads.
Changes to this policy
In short: we will warn you about significant changes 14 days ahead.
- We will tell you about significant changes in the app and by email 14 days before they take effect.