Privacy Policy

Last updated: 25 September 2026

1. Who is responsible for your data

Tempari is operated by Mohammed Enqira El Yousfi, trading as Tempari, based in Denmark. In this policy, “we” and “us” mean that operator.

For questions about this policy or about your data, write to [email protected].

2. Two different roles

We handle personal data in two roles, and your rights are different in each:

• As controller, for the people who hold a Tempari account. That means the businesses that use the software and the staff they invite. This policy covers that relationship.
• As processor, for the customers who book appointments with those businesses. We hold that data on the business’s instructions. If you booked an appointment, the business you booked with is the controller, so ask them about your data first.

3. What we collect

• Account data: name, email address, username, password (stored hashed), language, timezone, and the businesses and locations you belong to.
• Business data: your locations, the services you publish, your availability, and the settings for each.
• Booking data: appointments made through your booking pages. This includes the attendee’s name, email address, phone number if given, and anything they enter in your booking form.
• Calendar data, if you connect a calendar. Section 4 describes this in detail.
• Technical data: IP address, browser and device information, and server logs. We keep these to run and secure the service.

We do not ask for special category data such as health information. Please do not enter it in free-text booking fields.

4. Google user data

Tempari lets you sign in with Google and connect your Google Calendar. This section explains what we access from your Google Account and what we do with it.

What we access

How we use it

• We read the start and end times of events on the calendars you select. We use them to work out your availability, so customers can only book times when you are free.
• We create, update and delete only the events that belong to Tempari bookings. We do not change or delete any other event.
• To keep availability fast, we may store a copy of events on your selected calendars. The copy holds each event’s times, and may also hold its title, description and location. It is used only to calculate your availability.
• We use your Google profile name and email address to create your Tempari account and to identify the connected calendar.

We do not use Google user data for advertising. We do not sell it. We do not use it to build user profiles for anything other than running Tempari. We do not use it to develop, improve or train generalised or non-personalised AI or machine-learning models.

Who can see it

Our staff do not read your Google user data. The only exceptions are:

• when you ask us to, for example in a support request;
• when it is needed for security, such as investigating abuse;
• when the law requires it;
• when the data has been aggregated and anonymised for internal operations.

We share Google user data only as needed to provide the service. This includes our hosting provider, which stores it under a written processing agreement (section 6). We never transfer it to data brokers or advertising platforms.

Storage, retention and deletion

• Google access tokens and the calendar data described above are stored in our database. It is encrypted in transit, and access to it is restricted.
• If you deselect a calendar, disconnect Google Calendar in Tempari’s settings, or remove Tempari’s access, we stop reading your calendar. We also delete the stored tokens and cached events for that calendar.
• Events already created for your bookings stay in your Google Calendar until you delete them.
• If you close your Tempari account, your Google data is deleted along with the rest of your account data (section 8).

You can remove Tempari’s access to your Google Account at any time at myaccount.google.com/permissions.

Limited Use

Tempari’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.

5. Why we use your data, and on what legal basis

• To provide the service. This covers creating your account, running your booking pages, syncing your calendar and sending the emails an appointment needs. Legal basis: performance of our contract with you.
• To keep the service secure and working. This covers logging, error monitoring, abuse prevention and backups. Legal basis: our legitimate interest in a service that stays up and is not abused.
• To meet legal obligations. This covers accounting records and responding to lawful requests. Legal basis: legal obligation.
• To see how the app is used. We count which pages and features are used, so we know what to improve. The counts are anonymous, and you can object at any time (section 9). Legal basis: our legitimate interest in improving the service.
• Anything optional, such as marketing emails. We do this only if you have given consent, and you can withdraw it at any time.

6. Who else sees your data

We share personal data with the suppliers that run the service for us, each under a written processing agreement:

• Our hosting provider stores the application and database in the European Union.
• Cloudflare provides DNS and carries traffic between your browser and our servers.
• Our email provider sends transactional emails, such as booking confirmations.
• Sentry (EU region, Germany) helps us diagnose errors. Personal details are removed from error reports before they are sent.
• PostHog (EU region, Germany) counts anonymous usage (section 9).

If you connect a calendar or another app, we also send that app’s provider the data it needs to work, such as the bookings we add to your calendar. The provider handles that data under its own terms.

We do not sell personal data, and we do not share it with advertisers.

7. Where your data is stored

Personal data is stored in the European Union. Some suppliers, such as Cloudflare, are US companies or may process data outside the EEA. Those transfers rely on the EU–US Data Privacy Framework, with the European Commission’s Standard Contractual Clauses as the fallback.

8. How long we keep your data

• Account data: for as long as the account exists, then for 30 days after it closes so you can export it. After that, it is deleted.
• Booking data: for 24 months after the appointment, then it is anonymised. The business that controls the data can ask us to delete it sooner.
• Server and security logs: 30 days.
• Records we must keep by law, such as invoices: for the period the law requires. Under the Danish Bookkeeping Act, that is five years.

9. Cookies and usage analytics

Tempari sets only the cookies it needs to work. There are no advertising cookies.

• Session and sign-in cookies keep you logged in and protect forms against cross-site request forgery.
• One cookie remembers which location you are working in.
• Other cookies remember your language and whether you have dismissed the timezone prompt.

These cookies are strictly necessary or functional, so we do not ask for consent to set them.

We count how the app is used with PostHog, on its EU servers in Germany. It sets no cookie and stores nothing on your device. Your IP address is discarded on arrival, and nothing is tied to your account. You can turn this off at any time under Settings → Usage analytics.

10. Your rights

Under the GDPR, you can ask us to:

• give you a copy of your data;
• correct it;
• delete it;
• restrict or object to how we use it;
• give you your data in a portable format.

Write to [email protected] and we will respond within one month. If you booked an appointment with a business that uses Tempari, contact that business. We will pass your request on to them.

You can also complain to your data protection authority. In Denmark, that is Datatilsynet (datatilsynet.dk).

11. Changes to this policy

We will update this page when the way we handle data changes. The date at the top shows when it last changed. If a change materially affects you, we will tell you by email at the address on your account.