Privacy Policy — Testing Phase

Teemfix is run by Kristiano Ntemiri, a private individual in Switzerland. Contact: contact@teemfix.com

• For your account, this website, the contact form and feedback, I decide how data is used.
• For the data a venue enters about its team (schedules, time off, overtime, tips, checklists), the venue is the employer and is responsible for it. I handle that data on the venue's behalf. Questions about why your venue records something should go to your venue first; I will help where I can.

• Venue owners and admins: name, email, password (stored scrambled; nobody can read it), venue name and address.
• Team members, entered by the venue: name, email (optional), roles and departments, shifts, time-off requests with their type (day off, sickness, vacation or other) and any note, overtime requests and their payment status, tip shares and their payment status, checklist ticks.
• Account activity: when you last used the app, your language, and your sign-up and setup progress.
• Messages you send through the contact form or the feedback form.
• Technical data such as IP addresses and browser details, used by the hosting and security services in section 5.

No payment cards, no ID numbers. No advertising, no visitor analytics, and data is never sold.

Sickness: if a venue records time off as sickness, this may count as health data. Only the venue's admins see the type of leave; colleagues only see "On leave". Please do not write medical details in notes.

Team members' data is entered by their venue, not collected from them directly. A name and email are needed to create an account; everything else a venue records is up to the venue.

• To run the app: schedules, time off, overtime, tips, checklists, notifications and the related emails. Basis: the agreement with the venue and with you; for team data, the venue's own legal basis as employer.
• To keep the app secure: a robot check at sign-up, limits on sign-ups and emails, a leaked-password check, error alerts and security logs. Basis: legitimate interest in a safe service.
• To run the test: seeing which accounts finished setup, sending reminder emails to accounts that have not, and keeping a record of which reminders were sent. Basis: legitimate interest.
• To answer your messages from the contact and feedback forms.

Teemfix makes no automated decisions about people. Schedules, approvals and tip payments are always decided by the venue.

• Venue admins see all of their venue's data, including team emails and the type of leave.
• Staff see their own time off, overtime and tips, plus colleagues' names, roles and shifts in the schedule, and colleagues on leave as "On leave". Staff do not see colleagues' emails or type of leave.
• Public schedule link: a venue can share a link to a published week. Anyone with the link sees names and shifts without logging in. Share it only with your team.
• No venue can see another venue's data.
• I can see account and venue information to run the platform, and may access data when needed to fix a problem or answer a support request.

• Lovable: builds and hosts the app, sends login emails, and passes app emails to Resend.
• Supabase: database and login. Data is stored in the EU (Ireland).
• Cloudflare: delivers the website, protects it against bots (including a robot check on sign-up, password reset and invite links), and stores images.
• Resend: sends app emails from the EU (Ireland). Its records of sent emails are stored in the US, covered by the EU-US Data Privacy Framework and the EU Standard Contractual Clauses.
• Infomaniak (Switzerland): the contact mailbox.
• Have I Been Pwned: checks new passwords against known leaks. Only a short part of a scrambled version of the password is sent, never the password itself.

Some of these companies are based in, or have staff in, countries outside the EU and Switzerland, such as the US. Where data may leave the EU, Teemfix relies on the safeguards these providers offer, such as the EU Standard Contractual Clauses.

• Cookies: __cf_bm (Cloudflare bot protection, 30 minutes) and __dpl (hosting, keeps you on the current version of the site). Both are needed for the site to work.
• Browser storage: your login session, theme and language. All needed for the app to work.
• No tracking, advertising or analytics cookies.

• Account and venue data are kept while the venue uses Teemfix. Past shifts, time off, overtime, tips and checklist ticks are deleted 2 years after the date they relate to.
• A venue counts as no longer using Teemfix when it asks, or when no admin has logged in for 12 months. In that case the venue's admins get a warning email, and the venue's data is deleted 30 days later unless an admin logs in.
• Ask for deletion at any time; it is done within 30 days.
• When a venue removes a team member, their shifts, requests, tips and checklist ticks are deleted. Their login account stays until they ask for it to be deleted.
• Backups are kept for about 14 days.
• Messages sent through the contact form are kept only as long as needed to answer and follow up, and are deleted on request.
• During testing, data may occasionally be reset; reset data is deleted.

Accounts are for people aged 18 and over. Venues may list younger team members on the schedule without an email. They get no account and can see the schedule only through the public link.

You can ask to see, correct, delete or export your data, and to restrict or object to its use. Email contact@teemfix.com. If your request is about data your venue entered, it may be passed to the venue.

You can also complain to a data protection authority: in Switzerland the FDPIC (edoeb.admin.ch), in Greece the Hellenic Data Protection Authority (dpa.gr), or the authority in your country.

Connections are encrypted, each venue's data is kept separate, access is strictly limited, and the admin accounts behind Teemfix use two-factor login. If a data breach affects you, you and the authorities will be told as the law requires.

This policy will change as the app develops. Major changes will be announced in the app.