Privacy Policy

Tempora ("Tempora", "we", "us") is a property of ByteTech OÜ, a company registered in Estonia. This Privacy Policy explains what information we collect when you or your organization ("Agency") uses Tempora, why we collect it, and the choices you have.

1. What we collect

• Account and Agency data: name, email address, password (stored securely by our authentication provider, never in plain text), agency name, and role (owner, admin, or employee).
• Workforce data your Agency enters: employee names, contact details, job titles, departments, shift schedules, attendance/check-in records, and certification records (type, issue date, expiry date, and any file or reference number you attach), and employee requests (time off, shift swaps, schedule changes, and shift preferences).
• Sick leave and medical certificates: when an employee reports sick leave, we store the dates, an optional note, and the shifts they were taken off. If their Agency requires it, the employee can also upload a medical certificate. This is health data, a special category under the GDPR, so we apply extra safeguards: it's visible only to the employee and their Agency's owners and admins, it is never included in emails, certificate files are kept in private storage and opened only through links that expire after a few minutes, and certificates and notes are deleted when the employee's data is erased. Employees never need to share a diagnosis.
• Location at check-in: if an Agency sets a work-site location for a department, the employee's browser-reported location is recorded at the moment they check in or out, and only if they allow location access in their browser. It's used only to flag check-ins made away from the work site; Tempora does not track location at any other time.
• Billing data: if your Agency subscribes to a paid plan, payment processing is handled entirely by Stripe. We store only the resulting subscription status, plan, and Stripe customer/subscription identifiers — we never see or store your card details.
• Usage and log data: basic technical logs (timestamps, IP address, browser type) generated automatically by our hosting provider for security and reliability purposes, and error reports (what failed and where, configured not to attach IP addresses or user details) to help us fix bugs.
• Website analytics: we use Plausible Analytics to count page visits (for example, which pages are viewed and where visitors came from). Plausible uses no cookies, doesn't collect personal data, and doesn't track you across other websites; we only see aggregate numbers. We also use two tools from our hosting provider, Vercel: Web Analytics, to count visitors and page views, and Speed Insights, to measure how quickly pages load (for example, loading times and the type of device and browser). Neither uses cookies or identifies you.
• Website monitoring and improvement (optional): if you accept cookies, we use Microsoft Clarity on our public website to understand how visitors use it, for example where they click and scroll and where they get stuck, so we can fix problems and improve the pages. Clarity records interactions with our web pages (mouse movements, clicks, scrolling, the pages visited, device and browser type, approximate location) and shows them to us as heatmaps and session replays. Text typed into forms is masked. Clarity is never loaded inside the Tempora app, and app pages are masked, so your Agency's data, worker data and client data never reach it.
• Product and website analytics (optional): if you accept cookies, we use HeyCatch on our website and inside the Tempora app to understand how they are used and which channels bring new customers. HeyCatch records the pages you view, the buttons and links you click (including their visible text), how you arrived (referrer and campaign tags), your device and browser type, your IP address and the approximate location derived from it. When you are signed in as an Agency owner or admin, these visits are linked to your Tempora account ID and email address. If you decline cookies, HeyCatch sends nothing from your browser.
• Account milestones: when an Agency account is created, starts a trial or subscription, or cancels it, our servers send that event to HeyCatch with the account ID, the owner's email address and the plan, so we can understand which channels lead to paying customers. These events contain no workforce data and do not depend on the cookie banner, since no cookies are involved.
• AI assistant messages: if you use the in-app assistant, your questions are sent to Google's Gemini API, along with your role and Agency name, to generate an answer. The assistant can't see your Agency's records, and we don't store the conversation. Please don't include personal data about other people in your questions. The assistant on our public FAQ page works the same way: your questions are sent to Google's Gemini API to generate an answer, we don't store the conversation, and we use your IP address only to limit how many questions one visitor can send.

2. How we use it

We use this data to:

• Provide and operate the scheduling, check-in, certification-tracking, and billing features of Tempora.
• Send transactional emails: shift notifications, check-in reminders, certification expiry alerts, and request/approval notices.
• Process payments and manage subscriptions through Stripe.
• Maintain the security, integrity, and availability of the service.
• Respond to support requests sent to us directly.

We do not sell your data, and we do not use employee data collected on behalf of an Agency for advertising purposes.

3. Legal basis (GDPR)

For users in the European Economic Area, we process personal data on the following legal bases: performance of a contract (providing the service your Agency subscribed to), legitimate interest (securing and improving the service, and understanding which channels lead to new customers through the account milestones described in section 1), and, where applicable, consent (e.g. optional communications, and the optional cookies and analytics you accept in the cookie banner). You can object to the account milestones at any time by contacting us.

For workforce data an Agency enters or its employees submit (schedules, attendance, certifications, requests, sick leave), the Agency is the data controller and Tempora processes that data on its behalf, under our Data Processing Agreement. The Agency, as the employer, is responsible for the legal basis of that processing. For sick-leave information and medical certificates this is typically the employer's obligations under employment law (GDPR Article 9(2)(b)). An Agency should only require medical certificates where the law that applies to it allows this.

4. Who processes your data

We use a small number of trusted subprocessors to operate Tempora, each bound by their own data protection terms:

• Supabase — authentication and database hosting.
• Vercel — application hosting and infrastructure.
• Resend — transactional email delivery.
• Stripe — payment processing and subscription billing.
• Cloudflare (R2) — storage of uploaded certification files and sick-leave medical certificates, isolated per Agency.
• Google (Gemini API) — answers to questions asked in the in-app assistant.
• Sentry — error monitoring.
• Plausible Analytics — cookieless, privacy-friendly website statistics, hosted in the EU.
• Google (Google Ads and Google Analytics) — measuring how our website is used and which of our ads lead to new customers. Their cookies are only set if you accept them.
• Microsoft (Microsoft Clarity) — monitoring and improving our public website with heatmaps and session replays. Only used if you accept cookies; never inside the Tempora app.
• HeyCatch, Inc. (USA) — product and website analytics, and the account milestones described in section 1. Browser analytics only run if you accept cookies. Data is processed in the United States; transfers from the EEA are covered by the EU Standard Contractual Clauses in HeyCatch's Data Processing Addendum.

5. Cookies

Tempora uses cookies that are strictly necessary for the service to work: to keep you signed in and to remember the language you chose. These are always on. Our basic website analytics (Plausible and Vercel Web Analytics) and page-speed measurement (Vercel Speed Insights) work without cookies.

Statistics and advertising cookies (optional). We advertise with Google Ads and use Google Analytics to see how our website is used and which ads lead to someone starting a Tempora trial. For that, Google can set cookies, but only after you click Accept in the cookie banner. If you decline, no such cookies are set; Google then receives only anonymous, cookieless signals (no identifiers) that it uses to estimate ad results in aggregate. You can change your choice at any time with Cookie settings at the bottom of our website. Google's own use of this data is described in its privacy policy at policies.google.com.

Monitoring and improvement cookies (optional). With the same Accept, Microsoft Clarity is loaded on our public website to help us monitor and improve it (see section 1). Clarity sets first-party cookies such as _clck (recognizes a returning browser, up to one year) and _clsk (links the page views of one visit, one day), and Microsoft may set cookies such as MUID and CLID on its own domains. If you decline, Clarity is not loaded at all; if you later change your choice to decline, Clarity stops using cookies. Microsoft processes this data as described in its privacy statement at privacy.microsoft.com.

Analytics storage (optional). With the same Accept, HeyCatch is turned on, on our website and in the Tempora app (see section 1). It stores a random identifier in your browser (local storage and a first-party cookie whose names start with ph_) to recognize a returning browser for up to one year, remembers your consent choice (__ph_opt_in_out_), and keeps a count of events sent in the current visit (heycatch_session_volume). Until you accept, HeyCatch stores and sends nothing; if you later change your choice to decline, it stops at once. HeyCatch processes this data as described in its privacy policy at heycatch.ai/privacy.

6. Security

Access to your Agency's data is isolated at the database level so that no other Agency using Tempora can see it. Passwords are never stored in plain text, all traffic is encrypted in transit (HTTPS/TLS), and payment details are handled exclusively by Stripe's PCI-compliant infrastructure — Tempora never receives or stores raw card numbers.

7. Data retention

We retain Agency and workforce data for as long as the Agency's account remains active. If an account is closed, we delete or anonymize personal data within a reasonable period, except where we are required to retain records for legal, tax, or accounting purposes.

8. Your rights

Depending on your location, you may have the right to access, correct, export, or request deletion of your personal data, and to object to or restrict certain processing.

An employee can request deletion of their personal data directly from their Profile page; their Agency's owner or admin reviews and carries out the deletion (name, email, phone, date of birth, any uploaded certification files and medical certificates, and any notes left with a sick-leave report are erased -- shift and certification history is kept, but anonymized, since Agencies have their own legitimate operational and compliance record-keeping needs). An Agency owner can also erase the entire Agency's account, once any active subscription has been canceled, from Settings: every teammate and employee's personal data is erased and every login revoked in the same way, and the Agency's own name is anonymized. Shift, schedule, and compliance records are kept on file, anonymized, rather than deleted outright, for the same record-keeping reasons.

For anything else, contact us using the details on our Contact page.

9. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above.

10. Contact

Questions about this policy or your data can be sent to office@bytetech.ee, or via our Contact page.