← All policies

Privacy Policy

Last updated: October 15, 2026

1. Introduction

Welcome to FET Viewer ("we," "our," or "the application"). This privacy policy explains how we collect, use, and protect your information when you use our web application at fetviewer.com.

FET Viewer helps you visualize, filter, print and manage timetables generated by FET (Free Timetabling Software). Much of that work happens in your browser; some of it requires an account and our servers. This policy tells you which is which.

2. Information We Collect

2.1 Timetable data you provide

You may upload timetable files — FET's own .fet format, or CSV lists — containing:

• Subject names
• Teacher names
• Room assignments
• Student group information
• Time slots and schedules
• Activity tags and comments

A timetable you simply open is processed entirely in your browser. When you use a server-based feature it is transmitted to and stored on our servers — that covers saving a timetable to your account, backups, share links, embeds and digital-signage screens. The file check and the AI assistant work differently; sections 2.6 and 2.7 explain them.

2.2 Your account

Creating an account stores your email address, a username, your hashed password (we never see or store the password itself), your interface language, and the timestamps of your account activity. Timetables and other saved data are associated with your account. If you subscribe to a paid plan we also store your subscription record — see section 5.

If you use "Continue with Google" or "Continue with Microsoft", Google or Microsoft sends us your email address, your name and a fixed number for your account with them. For a school or work Microsoft account, it also sends the number of your organisation's directory. We keep the email address and these numbers to log you in and to show the connection on your account page. We do not keep your name. We never receive your Google or Microsoft password. We get no access to your email, files or contacts. You can disconnect Google or Microsoft on your account page.

When you create an account, we record where you came from, for example the file check page or a forum post. We use this only to learn which information helps people find FET Viewer. When you create an account, we store your country as a two-letter code. Our own server finds it from your IP address. We do not send your IP address to another company for this.

When you use the site, we record the pages and actions in our own activity log, with your IP address. We use it to keep the service safe and to count visits. We keep it for at most 365 days.

When you arrive from another website, we record that website's name, for example a forum. If the link has a campaign tag, we record the tag too. We do not record the full address of the other page.

2.3 Analytics, and your choice about it

We use Google Analytics and Microsoft Clarity to understand how the application is used, so we can fix problems and decide what to build next. These only run after you accept analytics cookies. If you decline, or have not yet chosen, no analytics script is loaded and no analytics cookie is set — the decision is enforced on our server, not only in your browser.

When they do run, they collect:

• Pages visited within the application and features used (e.g. filters applied).
• Time spent and interaction patterns within the application.
• Browser type, device type, and general location (country/region level only).

Analytics are never loaded on shared display surfaces (embeds, signage screens) or on a page opened through a share link, whatever your cookie choice — those pages set no cookies at all.

2.4 Advertising

Pages served to visitors who are not on a paid plan may carry advertising from Google AdSense. Google sets its own cookies for this and may use them to decide which advertisements you see; that processing is governed by Google's advertising policies. Paid plans carry no advertising. We do not give Google your timetable data or your account details for this purpose.

2.5 Local storage

We use your browser's local storage to save:

• Temporary cached timetable data (for quick re-loading).
• Display preferences and filter settings.
• Dismissed notifications and your cookie choice.

This data remains on your device and can be cleared at any time in your browser settings (clear the site data for fetviewer.com).

2.6 The FET file check

When you check a file on the Check a file page, your browser reads the file on your computer. Your browser then sends a summary of the file to our server. Our server does the calculation and sends the result back.

• The .fet file itself does not leave your computer.
• The summary we send to our server holds no names of teachers, rooms, subjects or classes. Our server refuses a summary that contains one.
• We do not store the summary, and we do not write its contents to any log.

If you check a timetable that is already saved on your account, our server makes the file from the data it already stores for you.

2.7 The AI assistant

The Check a file page and the timetable data screen have an optional AI assistant. It answers questions about FET and about your timetable. You choose where it runs:

• In your browser. The model runs on your computer, and nothing about your timetable leaves it. To start, your browser downloads the model from Hugging Face and GitHub, and those services see your IP address.
• On a model server on your own computer, such as LM Studio or Ollama. Your question and your timetable do not go to us.
• With your own key. Your browser sends your question directly to the AI company you chose. Your key stays in your browser; we never receive it.
• With our key, if your plan includes it. Your question goes to our server, then to one AI company — for example Google (Gemini), OpenRouter, Groq, Mistral or DeepSeek.

When a question goes to an AI company, it can include a summary of your timetable: the names of teachers, rooms, subjects and classes, the lessons and where they are placed, and the problems the check found. It never includes the .fet file itself. Before anything leaves your computer, the assistant asks you and shows what it will send. If you do not agree, nothing is sent. The AI company processes your question under its own terms, and we cannot control what it keeps.

Saved chats. If you are signed in, the assistant can keep your chats on your account. A kept chat holds your questions and the answers. This setting is on by default when the assistant uses an AI company, and you can turn it off. You can delete one chat, or all of your chats, at any time. We also delete the chats of a timetable when that timetable is deleted. Visitors who are not signed in keep no chat: it disappears when the page closes.

When we send a question with our key, we record which company and model answered and how many words (tokens) it used, but not the question. To improve the assistant, we also count words from questions it could not match. That count has no link to you or to your question.

When you are signed in, our activity log records how you use the assistant. It records the step, the screen and the model you chose, for example “set up a model” or “asked a question”. It never records your question, the answer, your key or the address of your own server.

2.8 The video on the home page

The home page shows our tour video as a picture from our own server. If you tap Play or a chapter, your browser loads the video player from YouTube (youtube-nocookie.com). YouTube then receives your IP address and can store data in your browser. Google's privacy policy applies to the player. Nothing loads from YouTube before you tap.

3. How We Use Your Information

3.1 Timetable and account data

Your timetable data is used to:

• Display your schedule, filter, search, print and detect conflicts.
• Save your timetable for later retrieval, or share it with people you choose, when you elect to use a server-based feature.

Your account data is used to sign you in, apply your plan's limits, send you the messages described in section 4, and support you when you contact us.

3.2 Analytics data

Where you have accepted analytics cookies, we use that data to:

• Identify and fix bugs and technical issues.
• Analyse feature usage to prioritise development and improve the experience.
• Improve the application's stability and performance.

4. Email we send you

4.1 Transactional email

We email you about your own account and activity: registration and password resets, subscription and payment confirmations and reminders, replies to messages you send us through the contact form, and notices about data that is about to expire. You cannot opt out of these while you hold an account — they are part of providing the service.

4.2 Product newsletters

Separately, we may email you occasional product announcements. Every one carries an unsubscribe link, and honours the one-click unsubscribe header your mail client may offer. You can also turn them off at any time under Email preferences in your account settings. Opting out stops product announcements only; transactional email continues.

4.3 How we measure a newsletter

So we can tell whether an announcement was useful, our newsletters contain a small invisible image and links that pass through our server. Together these let us record, for each recipient:

• whether and when the message was first opened, and roughly how many times;
• whether and when a link in it was clicked.

We do not record which individual clicked which specific link — link popularity is counted in aggregate across all recipients — and we do not store your IP address or browser details from these events. Open tracking is approximate by nature: many mail clients block or pre-fetch images, so an open can be missed or over-counted.

4.4 How long we keep it

Per-recipient sending and measurement records are deleted 180 days after a campaign finishes. Aggregate totals for the campaign survive, with no connection to any individual. Your opt-out record is kept for as long as you hold an account, because it is the record of your choice.

4.5 What we never do

We do not sell or share your email address, and we do not send marketing on behalf of third parties.

5. Payments

Paid plans are processed by iyzico, our payment provider. Card details are entered on iyzico's own secure payment form — we never receive or store your card number. We receive only the result of the transaction.

What we store is your subscription record: plan, billing cycle, start and expiry dates, status, and the provider's transaction reference, so we can show you your subscription and support you if something goes wrong. iyzico's handling of your payment data is governed by its own privacy policy.

Before you pay, we ask for your billing details: your name or the name of your school or company, and your street address, city, postcode and country. If you give them, we also store a VAT number. For a buyer in Türkiye, this can be the tax number (VKN) and the tax office, or the Turkish ID number (TC kimlik no).

We use these details to issue your invoice, to set the currency and the tax of your order, and to complete the payment. We send your name and address to iyzico with the payment. We do not ask for your phone number.

We keep a copy of these details with each payment, because an invoice must show the details of the day of the sale. We also keep your latest details on your account, so you do not need to type them again.

6. Data Sharing and Third Parties

6.1 Service providers

We share the minimum necessary with the providers that make the service work:

• Google Analytics and Microsoft Clarity — anonymised usage statistics, only where you accepted analytics cookies. Google privacy policy · Microsoft privacy statement
• Google AdSense — advertising shown to visitors who are not on a paid plan (section 2.4).
• iyzico — payment processing, with your name and billing address (section 5).
• Our e-invoice system and the Turkish Revenue Administration (GİB) — the details on your invoice, because Turkish law requires an electronic invoice for each sale.
• AI companies — only when you send a question through the AI assistant, and only after you agree (section 2.7).
• Our email delivery provider — the address a message is sent to, so it can be delivered.
• Our hosting provider — which stores the data described in this policy on our behalf.

6.2 No sale of data

We do not sell, rent, or trade your information. We do not share your timetable data or your account details with advertisers — the advertising described in section 2.4 is served by Google and uses only its own cookies.

Note that anyone holding a share link can see what that link is scoped to show, without an account — so treat a share link as you would a password. Data reached through a share link is not associated with the visitor's identity.

7. Data Security

We implement security measures to protect your data:

• Client-side processing: much of the timetable work happens solely in your browser.
• Transport security: everything is transmitted over HTTPS.
• Passwords are stored hashed, never in readable form.
• Share links and embeds carry unguessable keys, and you can revoke any of them at any time.

You are responsible for keeping your device, your browser and your password secure.

8. Your Rights and Choices

8.1 Cookie choice

Essential cookies keep you signed in and remember your interface preferences; the application cannot work without them. Analytics cookies are optional — the banner lets you accept or decline, you can change your mind at any time, and declining does not restrict any feature.

8.2 Accessing, correcting and deleting your data

You can:

• Edit your account details, or delete your account, from your account settings — deleting an account removes the timetables and other data belonging to it.
• Delete an individual timetable, backup, share link, embed or signage screen at any time.
• Turn product newsletters off under Email preferences.
• Clear the site data for fetviewer.com in your browser to remove everything stored locally.
• Ask us for a copy of your data, or ask us to correct or erase it, by writing to info@fetviewer.com.

8.3 How long we keep things

• Timetables you save to the server: on the free plan, for the number of days shown on the Pricing page after they were last edited (120 days today); on a paid plan, for as long as your subscription is active.
• Newsletter sending and measurement records: 180 days after the campaign finishes (section 4.4).
• Account and subscription records: for as long as you hold an account, and afterwards only where we must keep them for accounting or legal reasons.
• Billing details: with each payment and on your account, for as long as you hold an account. When you delete your account, we delete them from our site. Your invoices stay in the e-invoice system and with the tax authority for the period that Turkish law requires.

9. Children's Privacy

FET Viewer is designed for use by educational institutions and their staff. We do not knowingly collect information from children under 13.

10. International Data Transfers

Data you save to the server may be processed or stored outside your home country (for example in the European Union or the United States). We take appropriate measures to ensure it is protected according to the standards of this Privacy Policy. Analytics data is also subject to the international transfer policies of Google and Microsoft. An AI company that answers a question you send can process it in another country, for example the United States or China (section 2.7).

11. Changes to This Privacy Policy

We may update this privacy policy from time to time. When we make significant changes, we will update the "Last updated" date at the top of this page and may display a notification in the application.

12. Contact Information

If you have questions or concerns about this privacy policy or our data practices, please contact us:

• Through the feedback form at fetviewer.com
• By email at info@fetviewer.com

13. Legal Basis for Processing (GDPR)

If you are located in the European Economic Area (EEA), our legal basis for processing your information is:

• Contractual necessity: providing the service you asked for — your account, your saved timetables, share links, and the transactional email that goes with them.
• Consent: analytics cookies, which run only if you accept them, and which you can withdraw at any time; and sending a question and a timetable summary to an AI company, which happens only after you agree each time.
• Legitimate interest: keeping the service secure and reliable, and telling existing users about product changes — you can object to the latter at any time through the unsubscribe link or Email preferences.
• Legal obligation: issuing an invoice for each payment, which needs your billing details, and retaining accounting records for payments.

← All policies