Privacy Policy
Last updated October 14, 2026
Slotwise is a team availability calendar: who works which days, and how much capacity the team has. This policy says what personal data it handles, why, who else touches it, and what you can do about it. Using Slotwise is also covered by our Terms of Service.
Who we are
Slotwise is run by Aerixity, the trading name of Dmytro Bobryshev, a sole trader registered in Slovakia (IČO 55150195). Our address and business IDs are on the provider information page. Write to hello@aerixity.com about anything in this policy.
We decide how your account data is handled, so we're its controller. What an organization's admins and members add to it, such as profiles, days and notes, we handle on that organization's behalf.
What we collect
- Your sign-in email: Slotwise signs you in with a link sent to it; there's no password.
- Your profile: name, photo, team, position, and, if you add them, phone number and a short bio.
- Availability: the status of each day, optional times and notes.
- Invitations: the email, team and position an admin invites someone with.
- Google Calendar, if you connect it: your Google account email; your events, read to find Busy time of half a day or more; and the events Slotwise writes for your time off. The access token is stored encrypted.
- Slack, if an admin connects it: the Slack workspace and channel names and the address Slotwise posts to, stored encrypted.
- Netcore, if you connect it: your Netcore account email, and a connection key stored encrypted. Slotwise sends Netcore your planned hours for each month since you connected, the month's target, the hours per MD, and your organization's name and your member ID in it.
- Billing, if you start Pro: your email, and the name, address and VAT ID you give at checkout. Card details go to Stripe and never reach Slotwise; we keep only your subscription's state and dates.
- Technical data: server logs, which leave out names, emails, notes and tokens; IP addresses, seen by our hosting and by the bot check on sign-in; and error reports, which help us fix what breaks.
How we use it
- To show the calendar and count the team's capacity.
- To send sign-in links and invitations.
- To sync your Google Calendar, post to Slack and send your hours to Netcore, when they are connected.
- To bill Pro and keep the invoices the law asks us to keep.
- To keep Slotwise secure, stop bots and fix errors.
We don't sell your data, show ads, or track you across other sites.
Legal basis
- Contract: running Slotwise for you and your organization, and billing Pro.
- Legal obligation: keeping invoices and payment records for tax law.
- Legitimate interest: security, bot protection and error monitoring.
- Your choice: connecting Google Calendar, Slack or Netcore. You can disconnect Google Calendar and Netcore at any time in Settings, and an admin can disconnect Slack there.
Who sees what
Everyone in an organization sees each member's profile, including email and phone, and everyone's availability. A note marked private is seen only by admins and the person it belongs to. Notes are never sent to Slack, Google Calendar or Netcore. Profile photos and organization logos are stored at a link that isn't listed anywhere, but that anyone who has it can open.
Services we use
- Supabase: database, sign-in and file storage, in the EU (Frankfurt).
- Vercel: hosting.
- Plunk: sends sign-in and invitation emails.
- Cloudflare Turnstile: checks that a sign-in comes from a person, not a bot.
- Sentry: error monitoring.
- Stripe: payments and invoices for Pro, only when you start it.
- Google, Slack and Netcore: only when you connect them.
Each handles data only to provide its service to us.
Cookies
Slotwise uses only the cookies it needs to work. There are no analytics or advertising cookies, and nothing is kept in your browser's local storage. Because every cookie is necessary, Slotwise doesn't ask for consent.
So the app keeps working without a connection, while offline mode is on your browser keeps a copy of the Slotwise pages you open and the files they need. They stay on your device and are removed when you sign out or turn offline mode off in Settings.
- sb-availability-auth*
- Keeps you signed in. Set by our sign-in provider, Supabase.
- Until you sign out, at most 400 days
- workspace
- Remembers which organization you're working in.
- 1 year
- theme
- Remembers your theme: light, dark or system.
- 1 year
- offline-mode
- Remembers that you turned offline mode off on this device.
- 1 year
- member-banner-dismissed, organization-banner-dismissed
- Remembers that you closed a notice, so it stays closed.
- 1 year
- slack-oauth-state, google-oauth-state, netcore-pairing
- A one-time security check while you connect Slack, Google Calendar or Netcore.
- 10 minutes
How long we keep data
- As long as your account and your organization exist.
- Deleting your account (Settings → Danger zone) deletes your profile and availability. Deleting an organization deletes everything in it.
- Disconnecting Google Calendar, Slack or Netcore deletes the stored access.
- Invoices and payment records are kept for as long as tax law requires, even after the account is deleted.
- Backups held by our database provider expire on their own schedule.
Outside the EEA
Some of the services above, such as Vercel, Sentry, Cloudflare, Stripe, Google and Slack, may process data outside the European Economic Area. They do so under the EU Standard Contractual Clauses or the EU–US Data Privacy Framework.
Your rights
You can ask to see, correct, export or delete your data, and to restrict or object to how it's used. You can do most of this yourself in Settings; for the rest, write to hello@aerixity.com. You can also complain to the Office for Personal Data Protection of the Slovak Republic (dataprotection.gov.sk).
Changes
When this policy changes, the date at the top changes. If a change affects what we do with your data, we tell organization owners first.