Privacy notice
In short
- We collect what it takes to run a shared close calendar, and nothing for advertising. We do not sell data.
- It is stored in the EU, in Frankfurt.
- The time you record is visible only to you. Why somebody is on leave is visible only to them, whoever approves their leave, and the administrators.
- Usage is counted without saying who did what, and you can ask not to be counted at all.
- Close your account whenever you like. Accounts nobody uses are deleted after a year, with two warnings first.
Who we are
Period End Timetable is run by Tamás Halász, a private individual based in Hungary, under the name ENYO Technologies (“we”, “us”). Our postal address is Egressy út 52–54, 1149 Budapest, Hungary. Write to us about anything in this notice at info@enyotechnologies.com, or by post. We have not appointed a data protection officer; that address reaches the person responsible.
We have two roles, depending on the data:
- We decide what happens to your account, how the service is secured, our usage analytics, and our billing relationship with your organisation. For these we are the controller.
- Your organisation decides what goes into its calendar: its periods, tasks, notes, sign-offs, leave records and who is on the team. For that content we act on its instructions, as its processor, under the data processing terms in section 8 of our terms. Questions about it go to your organisation’s administrator first, and we help them answer.
What we collect
| Data | What it is | Where it comes from |
|---|---|---|
| Account | Email address, first and last name, display name, password (stored only as a hash), when you signed up and last signed in. If you turn on two-step sign-in, the key your authenticator app shares with our sign-in provider. If you sign up by email after following a campaign or another site’s link, that site’s name | You, or Apple, Google or Microsoft if you sign in with them |
| Organisation and team | Organisation name and plan, your role, the markets and regions you cover, invitations (name, email address, role) | You or your administrator |
| Close content | Periods, tasks, processes, notes, due dates, statuses, sign-offs (who signed off and when), comments on tasks, reminders, favourites, and settings such as holidays and the working week | You and your colleagues |
| Task history | What happened to each task and who did it: when it was added, its status changed or its details were edited, with the person’s name and the time | Recorded by the service as it happens |
| Leave (Attendance) | Where your organisation uses it: the days you ask for, half days, the kind of leave, an optional note, the decision and who made it, your allowance, and who approves your leave | You, your approver and your administrators |
| Your time records | Stopwatch and focus sessions you record against a task: start, end and duration. Only you can see them | You |
| Presence | While you are online, colleagues in your organisation see your initials, the page you are on and the task you have open. Nothing of it is stored | The app, live |
| Usage analytics | Which features are used, never what is written in them. See Usage analytics | The app |
| Billing | Plan, number of seats, subscription status, and the references Paddle gives the customer and the subscription. Card and bank details stay with Paddle | Paddle |
| Email delivery | Recipient, subject and delivery status of invitations, reminders, leave notices and account emails | Our email provider |
| Technical | IP address, browser and device type in our providers’ server logs | Your browser |
| Support | Whatever you write to us | You |
Why we use it, and on what legal basis
Each use rests on one basis under Article 6 of the GDPR.
| Purpose | Data used | Legal basis |
|---|---|---|
| Running the service: accounts, calendars, sign-offs, comments, task history, reminders, live updates | Account, organisation, close content, task history, time records, presence | Contract, Art. 6(1)(b). For close content and task history, also your organisation’s instructions |
| Leave records, where your organisation uses Attendance | Leave | Your organisation’s instructions, as its processor. Your organisation, as your employer, is responsible for the basis, including Art. 9(2)(b) for sick leave, which is health data |
| Keeping it secure: sign-in, access rules, limits, abuse prevention | Account, technical | Legitimate interests, Art. 6(1)(f) |
| Understanding how the product is used, to improve it | Usage analytics, hashed | Legitimate interests, Art. 6(1)(f). You can object |
| Deleting what nobody uses any more | Account, organisation, sign-in times | Legitimate interests, Art. 6(1)(f): keeping no more than is needed |
| Service emails: confirmations, password resets, invitations, reminders and leave notices | Account, email delivery | Contract, Art. 6(1)(b) |
| Billing and tax, through Paddle | Billing | Contract, Art. 6(1)(b), and legal obligation, Art. 6(1)(c) |
| Answering you | Support | Contract, or legitimate interests |
We do not send marketing email, sell data, or use it for advertising.
Usage analytics
We count how the product is used without learning who used it. The counts go to TelemetryDeck GmbH, Augsburg, Germany, which hosts in the EU.
What is counted: accounts and organisations created, a colleague joining, an invitation sent, a plan changing, a session starting, the page moved to, the name of a feature used (for example “task completed”), set-up finished, a plan limit reached, and the code of an error. Each carries your plan and role, the app version, your language, time zone, operating system family, light or dark mode, whether the app is installed, and, once at sign-up, the site or campaign you arrived from. That is never kept in your browser: it travels in the link into the app, and an account made by email keeps it with the account.
How you are kept anonymous: your account’s and your organisation’s IDs are replaced by a one-way hash, made with a secret held only in our database, before anything leaves. TelemetryDeck hashes them again on arrival. The counts are sent by our database server, not your browser, so TelemetryDeck never sees your IP address.
What is never sent: names, email addresses, task text, notes, comments, period names, leave, or anything about the time you record.
To object, write to info@enyotechnologies.com from your account’s address. From then on nothing about your account is counted.
What the app keeps in your browser
The app sets no cookies of its own and loads no other company’s scripts. It keeps these items in your browser’s storage, every one of them needed for the app to work as you asked.
| Item | Why | How long |
|---|---|---|
| Your sign-in session | Keeps you signed in | Until you sign out or it expires |
| Your preferences: theme, clocks, week start, filters, column order, collapsed sections | Remembers your choices on this device | Until you clear them |
| A running timer and time not yet saved | Survives a reload or a lost connection | Until saved |
| An offline copy of the app | Lets it open without a connection | Replaced at each update |
| An invitation link, and a note to set up your first calendar | Carries you through sign-up | Until the tab closes |
| Which organisation you last opened, and a note after you switch | Lets other open tabs notice the switch, and says where you arrived | Until you clear it; the note until the page reloads |
| A note when the app refreshes to a new version | Says which version you are now on, and keeps it from refreshing twice for the same one | Until the tab closes |
Clearing your browser’s data for the site removes all of them. The checkout page, which opens when an administrator subscribes, is the one place that loads another company’s code: Paddle’s checkout, under Paddle’s own privacy notice.
Who receives it
These companies process data for us under contract, and may use it only to provide their service to us.
| Recipient | What they do | What they receive | Where |
|---|---|---|---|
| Supabase | Database, sign-in, live updates, server functions | Everything stored in the app | EU (Frankfurt, Germany) |
| Cloudflare | Hosts and delivers the website and the app | IP address and request details | Worldwide network |
| Resend | Sends email | Recipient, subject and content of service emails | Sent from the EU; account data and logs kept in the US |
| TelemetryDeck | Usage analytics | Hashed counts only (see above) | EU (Germany, the Netherlands) |
These receive data as controllers in their own right, under their own privacy notices:
- Paddle, our reseller and merchant of record. Paddle sells the subscription to your organisation, takes the payment, issues the invoice and handles sales tax. It receives what you enter at checkout, and from us your organisation’s ID and the plan chosen.
- Apple, Google or Microsoft, only if you choose to sign in with them.
When an administrator fills in a market’s public holidays, our server asks Nager.Date for that country’s list. Only the country and the year are sent, and nothing about anybody.
Inside your organisation, colleagues see what the app shows them: names, roles, sign-offs, comments, each task’s history and who is online. A private task’s comments and history are seen only by whoever can see the task. With Attendance, every colleague sees that somebody is away and when, but not why. The kind of leave and its note are seen only by the person, whoever approves their leave, and the administrators. Administrators also see when each member last signed in. We disclose data to authorities only when the law requires it.
Transfers outside the EU
The app’s data is stored in the EU, in Frankfurt. Some of it reaches the US through Resend and Cloudflare’s network, and through the US parent companies of Supabase and of the sign-in providers. Where a recipient is certified under the EU–US Data Privacy Framework, that certification covers the transfer; otherwise the EU Standard Contractual Clauses in its data processing agreement do. Write to us for a copy of the safeguard that applies to a recipient.
How long we keep it
We keep data while it is needed for the service, and delete it when you close your account or your organisation is deleted.
| Data | Kept until |
|---|---|
| Your account | You close it, under My account. Your profile, private work, time records, leave records, memberships and analytics bookkeeping are deleted, and so are calendars nobody else is in |
| Accounts nobody uses | An account or a free calendar unused for twelve months is deleted, after emails thirty and seven days before. Accounts in a calendar that pays are not. A sign-up never confirmed goes after seven days |
| Sign-offs, comments and changes you made | They stay in your organisation’s close record with your name, because a signed-off close is a record your organisation relies on. The link to your account is removed. You can remove a comment of your own at any time |
| Task history | Deleted with its task. The newest 200 entries of each task are kept |
| Your organisation’s calendar | An administrator deletes the organisation |
| Invitations | Used, withdrawn or expired |
| Usage analytics | Held by TelemetryDeck in hashed form, which cannot be traced back to you |
| Billing | Paddle keeps invoices and payment records for as long as the law requires of it. Our own log of billing changes holds no personal details, and loses its link to your organisation when the organisation is deleted |
| Email delivery logs | Kept by Resend for its own limited log period |
| Support messages | Two years after the conversation ends |
Security
Every read and every write is checked by the database itself, against your organisation and your role, whatever the page asks for.
- Data travels encrypted (HTTPS) and is stored encrypted by our database provider.
- Passwords are stored only as hashes. Changing your email address needs confirmation from both the old and the new address.
- You can turn on two-step sign-in under My account: signing in then also needs a code from an authenticator app on your phone, and the database refuses anything from a session that has not given it.
- Roles limit what each person can do: administrator, editor, sign-off, read-only. Private tasks are visible only to whoever made them, and time records only to you.
- The app runs only its own code: a strict content security policy stops any other script from loading.
- The keys for email, payments and analytics are held in the server’s secret store, never in the page.
If a breach puts your data at risk, we tell the Hungarian authority, NAIH, within 72 hours and tell you without undue delay, as the GDPR requires.
Your rights
You can ask us to show, correct, delete, limit or hand over your data, and you can object to how we use it.
- Access: a copy of the data we hold about you.
- Correction: change your name, email address and password yourself under My account, or ask us.
- Deletion: close your account yourself under My account. Sign-offs, comments and changes you made stay in your organisation’s record, as described above.
- Restriction of how we use your data while a complaint is looked into.
- Portability: your data in a machine-readable file. Your organisation’s administrators can also download all of its content themselves, at any time, under Settings.
- Objection to any use based on legitimate interests, including usage analytics.
Write to info@enyotechnologies.com. We answer within one month, and tell you if a complex request needs up to two more. For content in your organisation’s calendar, we may first pass your request to its administrator, who decides on it.
You can also complain to the Hungarian data protection authority:
Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH)
1055 Budapest, Falk Miksa utca 9–11 · postal address: 1363 Budapest, Pf. 9
ugyfelszolgalat@naih.hu · +36 1 391 1400 · naih.hu
You may instead complain to the authority where you live or work, or go to court.
Children, automated decisions, and changes
The service is for finance teams at work and is not meant for anyone under 16. We make no decisions about you by automated means alone that have legal or similarly significant effects.
When this notice changes, the new version appears here with its date. If a change matters, such as a new recipient or a new use of your data, we tell account holders by email or in the app before it takes effect.