Privacy Policy.

1. Who we are

Reassign is operated by Pogled Naprej d.o.o., Italijanska ulica 8, 1000 Ljubljana, Slovenia (registration no. 3654982000, VAT ID SI92786499). We are the data controller for the personal data described here. For anything about your privacy, email hello@reassign.ai.

2. What we collect

The short version: your day stays yours. We don't sell your data, we don't share it for advertising. We process it to run your planner, using the service providers described below and the integrations or AI clients you authorise. Here is what we collect and why:

• Your email address, so we can send your sign-in code and reach you about your account.
• Sign-in details from Google or Apple, only if you sign in with one. From Google: your name, email address, and profile picture. From Apple: your email address and, the first time only, your name if you choose to share it. Apple lets you hide your email; if you do, Apple shares a private relay address with us instead of your personal email. That relay address forwards email to you. Each one also gives us a stable identifier for your account with them, so we recognise you next time. We never see your Google or Apple password. See Signing in with Google or Apple.
• The day plans you create: your events (their title, time, and any notes you add), your areas and activity types, plus the timezone you set so your day shows in the right hours. We store these only to provide your planner, including saving and syncing your day and the features described below.
• Day notes, if you write them. When you review a past day with the AI command bar, you can note what went well, what did not, and one lesson. We store these notes with your account, and the AI sees them when you review that day again.
• Your AI instructions and saved preferences. The context you write for the AI in Settings, and any preference you ask the AI to remember. A remembered preference becomes one line of that same text, which you can edit or delete in Settings.
• Voice clips, only if you use voice input. Your browser streams the audio (up to about 60 seconds a clip) through Vercel AI Gateway to a speech-to-text provider, and the text goes back to where you dictate: the dial, the command bar, the Inbox quick-add, the notes of an event, or a calendar settings field. If the live stream fails, the recorded clip goes to the provider through our servers instead. To improve recognition, a voice clip also sends short word hints: the names of your areas, activity types, projects, and of events near today. We do not store the audio or the transcript. Our analytics record only its size, format and length.
• Files you attach in the AI command bar. Up to three photos or PDFs per request. The AI reads them to suggest plan changes for you. We do not store the files. Our analytics record only how many files you sent and their total size.
• Calendar and task data, only when you connect a service. We receive account identifiers and labels, calendar/list/team/project names and identifiers for source selection, and event or task content for sync: titles, descriptions or notes, dates and times, completion or workflow state, recurrence where supported, source links, and identifiers or update markers. We store imported items on your dial or in your Inbox, plus the connection and sync records needed to keep them current. Provider permissions can cover more data than you choose to import; selection and filtering happen within Reassign. See Connecting your calendars and tasks.
• Notification settings and device details, if you enable push alerts. We store your alert preferences and, for each device, its registration, any alert settings you set for that device only, delivery identifiers, a record of each send to it, and its recent activity. Notification content can include a block title and timing. See Block and break alerts.
• Cycle start dates, only if you opt in to the Cycle rhythm feature in the energy layer. This is health data, so it gets its own rules: see Cycle data.
• Basic technical and usage data: the kind a web app needs to load, sync, and stay secure (for example, device and browser type and approximate region).
• What you capture with the browser extension, if you install it: the address and title of a page you choose to save, and any text you had selected. Only ever on your say-so, never in the background. See The browser extension.
• Billing details for Pro, handled by Stripe. We receive a record that you paid and your plan status; we never see or store your full card number.
• A trial record. When you start your free trial, and again when you delete your account, we store a keyed hash of your email address and of any linked Google or Apple sign-in ID. The record does not contain your email or ID in plain text. See the trial record.

And we never use your day plans to train AI models. The providers below only ever touch your data to run Reassign for you, each bound by contract to protect it and use it for nothing else. It never leaves that circle without your say-so.

Planner access requires an account. Saved plans are linked to that account and stored on our servers. An internet connection is required to save changes.

3. Cycle data, if you opt in

The energy layer has an optional Cycle rhythm feature. It's off by default, and it stays off until you switch it on yourself, with a separate, explicit consent inside the app. Never opt in, and no cycle data about you exists anywhere in Reassign.

• What we store. The cycle start dates you log (with a time of day, if you set one) and your cycle settings: your typical length, and whether your cycles come naturally. That's the whole list. We never ask your gender, and we never infer it.
• What it's for. One thing: shaping your personal energy curve. The feature starts from a small, research-hedged dip around menstruation, and from there it learns only from your own logs and mood labels.
• Where it never goes. Cycle dates and settings are stored separately from your other planner data. Realtime notifications can identify that the cycle category changed, but do not contain cycle dates or settings. Cycle content is excluded from analytics and session replays, from every email we send, from AI processing, and from anything a connected AI assistant can read over MCP. Even an assistant you've granted full access can't see it.
• Deleting it. Turn the feature off and delete all your cycle data in one tap, right in the app: no email, no waiting. Deleting your account removes it too.

We process this data on the basis of your explicit consent (Article 9(2)(a) GDPR). Withdraw it at any time by turning the feature off. A standalone Consumer Health Data Privacy Policy covers this data for US state health-privacy laws.

4. How we use it, and on what basis

We use your data only to run and improve Reassign:

• to provide the service: sign you in, store and sync your days, and run the features you use (this is necessary to perform our contract with you);
• if you connect a calendar or task app, to show your events and tasks on the dial and write your edits back, and (unless you turn it off) to sort each imported item into the right area for you (necessary to provide the feature you asked for);
• to take payment and manage your subscription (also to perform our contract);
• to keep the service secure and working, and to understand how it's used so we can improve it (our legitimate interests);
• to give each person one free trial, including after an account is deleted and made again (our legitimate interest in preventing trial abuse);
• to contact you about your account or important changes. We don't send marketing email without your consent.

We don't sell your data, we don't use your day plans for advertising, and we never use them to train AI models. These commitments also apply to imported calendar and task data. Any successor must honour them; a transfer of Google user data in a merger, acquisition or asset sale requires your explicit prior consent.

5. Who helps us run Reassign

A few trusted providers process data on our behalf, under contracts that require them to protect it:

• Neon: hosts the Postgres database containing your account, saved plans, settings, and connected-service records.
• Ably: delivers change notifications to your signed-in sessions using account/channel identifiers, versions, changed-data categories, and sometimes block identifiers and date ranges. Those sync messages do not contain event text. Separately, when you enable push alerts, Ably handles device registrations and notification payloads, which can include block titles, reminder text and a link back to the planner.
• Vercel Blob: stores profile images and dial images generated for email digests.
• Stripe: processes payments. Your card details go directly to Stripe; we never handle them on this site.
• Resend: delivers sign-in codes, account email and the planner email digests you receive, which can contain information from your day, including imported events or tasks.
• Vercel: hosting and infrastructure that serves the site and app.
• AI processing through Vercel AI Gateway: Typesafe AI, Google and Anthropic provide classification and generation models; Anthropic reads the photos and PDFs you attach, with Google as a fallback. Live voice input streams to xAI through Vercel AI Gateway to turn speech into text, with OpenAI and Google as fallbacks, and OpenAI can also provide a fallback for processing your AI instructions. The provider used depends on the feature and its fallback configuration. Inputs can include event or task titles and notes, source names, your area and activity-type labels, the context or instructions you supply, your voice recordings and their word hints, and the photos or PDFs you attach. See AI processing for the features and controls. We do not use your planner or connected-service data to train AI models.
• PostHog: product analytics in the app (not on this site) that help us see how it's working and fix what breaks; more on this under cookies and analytics.

Signing in with Google or Apple. Neither is on the list above, because neither processes data for us. If you sign in with one, it confirms who you are under its own privacy policy, and it learns that you used it to sign in to Reassign. We ask for the least each offers (your name and email, plus Google's profile picture) and we send neither of them anything about your day. You can link either one to an existing account from your settings. To cut the link from their side, remove Reassign under Sign in with Apple in your Apple Account settings, or under third-party connections in your Google Account. To have the link removed from our side, email hello@reassign.ai; deleting your account removes it too.

6. Connecting your calendars and tasks

Reassign connects to Google Calendar, Outlook Calendar, Todoist, Google Tasks, Microsoft To Do, Linear and TickTick when you authorise that connection. Signing in with Google or Apple does not by itself connect your calendars or task lists. Each integration has a separate connection flow, and your provider may require an organisation administrator to approve it.

Permissions and source selection are different. The provider's consent screen describes the access its API grants. Those permissions can apply across your account or workspace. Reassign lists available sources so you can choose what to sync, then applies those choices and its filters. Choosing a list or team in Reassign does not narrow the OAuth permission at the provider.

• Google Calendar: https://www.googleapis.com/auth/calendar.calendarlist.readonly lists your calendars for selection; https://www.googleapis.com/auth/calendar.events reads and changes calendar events for two-way sync. We also request openid, email and profile to identify and label the connected account, and offline access to keep syncing without repeated sign-in.
• Google Tasks: https://www.googleapis.com/auth/tasks permits reading, creating, editing, organising and deleting tasks and task lists. Reassign uses it to list your task lists and sync tasks from the lists you select. openid and email identify the connected account; offline access keeps the connection working. The Google Tasks API exposes due dates, not due times.
• Outlook Calendar: delegated Calendars.ReadWrite permission reads and changes calendar events; offline_access, openid, profile and email maintain and identify the connection.
• Microsoft To Do: delegated Tasks.ReadWrite permission reads and changes tasks and lists. User.Read reads the basic profile used to identify the account. We also request offline_access, openid, profile and email. Reassign syncs tasks from the lists you choose.
• Todoist: data:read_write grants read/write access to your task and project data. Reassign lists projects for selection and syncs tasks from the projects you choose.
• Linear: read and write grant access under the connected user's account. We read your user and workspace identifiers, account label, available teams and workflow states to set up sync. Imported issues are limited to those assigned to you in selected teams. Rechecking a previously linked issue can read its current assignment and content to detect reassignment, cancellation or archiving and remove it from your imported set.
• TickTick: tasks:read and tasks:write grant task read/write access. Reassign reads project information for selection and imports tasks from your chosen projects, including titles, notes, dates or times, completion and recurrence information used by sync.

What sync writes back. Depending on the provider and action, Reassign can create or update linked events and tasks, change completion or workflow state, and carry out supported removal actions. Titles, notes, due dates and completion sync for Google Tasks, Microsoft To Do and Linear; the working day, hour and duration you schedule in Reassign stay separate from their due dates. Todoist and TickTick also support timed tasks. Calendar edits require write access to the calendar. Provider features such as labels, attachments and project management are not all imported or synced.

Connection and sync records. We store account/source identifiers, encrypted access and refresh tokens where supplied, expiry and connection status, source selections, provider item identifiers, change markers, task snapshots and pending-write records as needed for reliable sync. These records let us match an item across both apps and recover interrupted updates. Google Tasks and Microsoft To Do tasks created through Reassign may carry a short reference in their provider notes to prevent duplicate creation; Reassign hides that reference in its own display.

Disconnecting, deleting and revoking. In Integrations, Disconnect account stops Reassign's sync and removes the connection credentials from our active database, but keeps previously imported blocks and source records. Deleting the connected source also removes its linked imported items from Reassign. Neither action deletes your original events or tasks at the provider. See retention and account deletion for removing the rest of your data, or email hello@reassign.ai for help.

Removing a connection in Reassign does not guarantee that the provider's own grant is revoked. To remove that grant, use Google Account connections, Microsoft account permissions for personal accounts, or Microsoft My Apps for work or school accounts. For Todoist, Linear and TickTick, use the provider's connected-app or integration controls, or contact that provider for revocation help. Revoking a grant at the provider stops authorised API access; it does not by itself delete data already saved in Reassign.

AI processing. If AI sync is enabled, imported event or task titles and notes, source names, category labels, defaults and your planning instructions or context can be sent through Vercel AI Gateway to the AI providers listed above. This classifies items into areas and activity types and applies your import preferences. Turn off AI sync during connection setup or in AI settings to keep ordinary sync without that AI refinement. Separately, when you use Ask AI, braindump, AI task breakdown, the Inbox quick-add, the Chrome extension side panel or address bar, the API, voice input, attached files or a day review, the request and relevant planner context can be processed by those providers. That context may include imported items, your saved AI preferences, a short summary of your recurring events from the last 30 days, and the day note of a day you review. For the Inbox quick-add and Inbox capture, it also includes the names of your connected task lists, so that AI can send an item to a list you name. For voice input, it is the short word hints described under What we collect. Turning off AI sync does not disable AI actions you deliberately request. Cycle dates and settings remain excluded.

Other ways imported content is used. Imported items become planner data. They may appear in your planner email digests and in push alerts you enable. An AI client you separately authorise can read or change them within its granted scope, as explained in Connecting an AI provider over MCP. Provider credentials are not shared with these clients or the AI models.

Google API data and Limited Use. Reassign's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. This applies to Google Calendar and Google Tasks data and data derived from them. We use it for the visible planner features described here, not advertising, sale to data brokers, credit decisions, or training general-purpose AI models. Transfers are limited to providing those features with your consent, security needs, legal obligations, or a business transfer with your explicit prior consent. Human access is limited to your affirmative agreement to inspect specific data, security or legal needs, or aggregated internal operations allowed by that policy. These restrictions also apply to our service providers and successors.

The connected services also operate under their own terms and privacy policies. Relevant developer terms include the Microsoft APIs Terms of Use, Doist Terms of Service, Linear Terms of Service, and TickTick Terms of Service.

Block and break alerts. When you enable notifications, Ably and your browser or operating system's push service deliver alerts to your registered device. Payloads can include a block title, reminder text and a destination in the app, so imported calendar or task titles can appear on your notification screen. We send them to each device where alerts are on, up to your 50 most recently active devices. You can disable alerts or individual categories in Settings → Notifications, for all devices or for one device, and manage notification previews through your device settings.

7. Connecting an AI provider over MCP

If you connect an AI assistant (an LLM, via an MCP client, such as ChatGPT from OpenAI or Claude from Anthropic) to your day, data is shared only because you authorised it on a consent screen, and only within the scope you granted: view your events and schedule (events:read), change them (events:write), or both. Within that scope it sees your events (their title, time, and any notes), plus the areas, activity types, and timezone they rely on, plus relevant source names. This can include imported calendar events, tasks, and Inbox items from the services you connected. Nothing beyond what you granted. The assistant, and the company behind it (such as OpenAI or Anthropic), then handles what you send under its own privacy policy rather than this one, worth a quick look before you connect.

We keep a small record of the connection itself: the app's name, the access you granted, and when you authorised it and last used it. You can revoke a connection at any time from Settings → MCP, and access stops straight away. A connected assistant can also pass along feedback for you, which we handle as described below.

8. The browser extension

The Reassign extension for Chrome puts your day on every new tab and lets you send a page, a link, or a piece of text you've selected straight to your plan. It reaches your day the way any other connected client does: through an OAuth grant you authorise on Reassign's connection flow, within the scope described in section 7. Remove the extension, or revoke it from Settings → MCP, and its access stops.

What it keeps on your device.

• Your connection to Reassign: the access and refresh tokens from that grant, when they expire, and which Reassign server they belong to. They sit in the browser's extension storage on that device and survive a restart, until you sign out or remove the extension.
• Your new-tab preference: which view the new tab opens on. This one goes in Chrome's synced extension storage, so with Chrome sync switched on it travels through Google to your other signed-in Chrome installs, under Google's terms rather than ours. It's a single setting. Your day is never stored there.
• Whatever a capture is holding at that moment: the title and address of the page you're about to save, and the undo behind a notification. This lives in session storage, clears when you close the browser, and a capture you leave untouched expires in a minute.

What it reads from your browser, and when. The extension has no standing access to your browsing. It can read a page's address and title only at the moment you ask it to: a right-click, the keyboard shortcut, or a click on its toolbar icon. Right-click a link instead and it reads that link's address. If you had text selected, that selection travels with the capture and becomes the block's name, which is the point of selecting it. It doesn't read pages you haven't captured, and it never collects your browsing history. What you type after the reassign keyword in the address bar is parsed on your device as you type; only the entry you actually commit is sent anywhere.

What it sends, and to whom. Only Reassign. Two kinds of request leave the extension, both to reassign.app: the sign-in exchange above, and the calls that read your schedule and add to it. What travels in those is what you chose to save: a title, any notes, the source address, a time, and a duration. The extension contacts no one else. It loads no third-party code, carries no advertising, and does no tracking of any kind.

The new tab is the Reassign app. Not a copy of it, not a cut-down view: the extension embeds the real app, so everything in this policy applies inside that tab exactly as it does at reassign.app, your session included. One difference is deliberate. The new tab is never session-recorded, because opening a tab isn't a decision to be watched. Error reports still reach us from it, so we can fix what breaks on the surface you see most.

9. Feedback and bug reports

When you send feedback or report a bug, we keep your message and a little context so we can reproduce and fix things: the type (a bug, an idea, or something else), the page or source it came from, and your browser, or, if you asked a connected AI assistant to send it for you, that assistant's name. If you're signed in, we link it to your account so we can follow up; if you're not, we keep only the reply-to email you choose to give us. We use this to diagnose problems and make Reassign better, and we delete it when you delete your account.

10. Cookies and analytics

We keep this light. The app uses the storage it needs to sign you in, remember your session, and remember app preferences. Saved planner data is tied to your account on our servers. To see how the app is holding up and fix what breaks, we also use PostHog for product analytics: a handful of usage events, error reports, and anonymised replays of how people move through the screens, with anything you type and your day's contents hidden automatically, so we see the path, not your day. It stays first-party, and none of it is sold, used for advertising, or used to follow you across other sites. One surface is carved out of the replays entirely: the browser extension's new tab is never session-recorded, as section 8 describes.

On this marketing site we measure visits with Vercel's privacy-friendly, cookieless analytics, which doesn't follow you across other sites. We don't load the Meta (Facebook) pixel or any advertising cookies here. If you reach us by clicking one of our ads, the ad network's click identifier may be carried through to the app so we can measure whether the ad worked. That measurement happens in the app, under the choices you make there.

Some pages include a YouTube video player using privacy-enhanced mode (youtube-nocookie.com). When the player loads, your browser connects to YouTube before you press play, sharing your IP address and browser request information. YouTube handles those requests and video playback under Google’s privacy policy.

11. How we protect your data

We treat your data, and especially sensitive data like your connected calendar and task items, with care, and we protect it with industry-standard safeguards:

• Encrypted in transit. Everything between your device and Reassign, and between Reassign and the providers above, travels over TLS (HTTPS). Your data is never sent in the clear.
• Encrypted at rest. Your day plans and account data are stored on infrastructure that encrypts data at rest.
• Connection tokens kept sealed. The credentials that link Reassign to a calendar or task app (and to any AI provider you connect over MCP) are stored encrypted on our servers, never exposed to your browser, and used only to run the features you asked for. Disconnecting removes the stored provider credentials; revoke the provider grant separately as described above.
• Least-privilege access. We request permissions needed for the features you connect. Provider scopes may cover an account or workspace; source selection and import filters limit what Reassign syncs, as described above. Access to production systems is limited to the few people who need it to operate Reassign, protected by strong authentication.
• Sign-in without passwords. We email you a 6-digit sign-in code, so there's no password for you to reuse or for us to leak. Sign in with Google or Apple instead and your password stays with them; we never see it. You can also add a passkey and sign in with Touch ID, Face ID, or a security key: the key itself never leaves your device, and we only ever store its public half.
• Analytics that don't see your day. Our product analytics automatically mask anything you type and your day's contents, so the people improving Reassign see the path through the app, not what's on your dial.

No system can promise perfect security, but we work to protect your data and we keep these measures under review. If we ever discover a breach affecting your personal data, we'll notify you and the relevant authorities as the GDPR requires.

12. How long we keep it

Your saved plans remain when your trial or paid access ends; losing planner access does not itself delete your account. You can delete individual plans while you have planner access, or choose Delete account in settings. The expired-access screen also provides account deletion. Account deletion removes account data and cancels any active subscription. We retain records we must keep for legal reasons, such as billing records required for tax and accounting. Contact us if you need help with deletion or retention.

Connected-service credentials are kept while needed for an active connection and are removed when you disconnect or delete it. Disconnecting retains imported planner data; deleting the source removes its linked imports and connection records. Account deletion removes your account's stored integration data as well. Revocation at a provider may first leave a disconnected or revoked source record in Reassign; use source or account deletion, or contact us, to remove retained copies. Records subject to legal retention obligations are kept only for that purpose.

Any feedback you've sent, and the records of AI providers you've connected, live alongside your account and go when it does. The same applies to your day notes, your saved AI preferences, and your device and alert records.

The trial record. To give each person one free trial, we keep a keyed hash of your email address and of any linked Google or Apple sign-in ID. For a Gmail address, we first remove dots and + tags, so these changes give the same result. The record does not contain your email or ID in plain text. This record has no link to your account, so it stays after you delete your account. We use it only to check whether a new account already had a trial. We delete it after 730 days with no new write to it. We rely on our legitimate interest in preventing trial abuse. You can object to it by emailing hello@reassign.ai.

13. Your rights

Under the GDPR you can:

• access the personal data we hold about you;
• correct data that's wrong or out of date;
• delete your data (“the right to be forgotten”);
• export your data in a portable form;
• object to or restrict certain processing, and withdraw consent where we relied on it.

Choose Delete account in settings or on the expired-access screen. For a copy, portable export, or help exercising your rights, email hello@reassign.ai. You also have the right to complain to your local data-protection authority; in Slovenia that's the Information Commissioner (Informacijski pooblaščenec).

14. International transfers

Some of our providers operate outside the European Economic Area. When data is transferred abroad, we rely on safeguards recognised under the GDPR (such as the European Commission's standard contractual clauses) to keep it protected.

15. Children

Reassign isn't directed at children. We don't knowingly collect data from anyone under the age of digital consent in their country. If you believe a child has given us data, contact us and we'll remove it.

16. Changes to this policy

We may update this policy as Reassign evolves. When we make a material change, we'll update the date above and, where it matters, let you know in the app or by email.

17. Contact

Email hello@reassign.ai, or write to Pogled Naprej d.o.o., Italijanska ulica 8, 1000 Ljubljana, Slovenia.

See also the Terms of Service.