Timetable Maker Where your timetable is stored
Last updated: 13 August 2026
Your timetable is saved in your own browser, on your own device. It is never uploaded, never stored on a server, and there is no account it could be attached to. This page explains how that works in practice, how to confirm it for yourself, and — just as importantly — what can make your timetable disappear.
This is the mechanical explanation. The formal legal document is the Privacy Policy, and it takes precedence where the two differ in detail.
How saving works
Every time you add, move, edit or delete an event — or change a setting — the tool writes the complete state of your timetable into your browser's local storage, under the key sm_timetable_v1. Local storage is a small database that browsers keep per site, on the device itself.
There is no save button because there is nothing to send. The write happens immediately and finishes in about a millisecond. The Auto-saved indicator in the top right of the tool shows a check mark when the last write succeeded, and a dash if it failed.
When you return to the page, the tool reads that same key back and rebuilds your grid. That is the entire persistence model. There is no backend, no database, and no user table — which is also why there is nothing to sign up for.
What is stored
Exactly what you typed: your event titles, days, start and end times, notes and colours, plus your display settings. It is held as JSON, in the same structure as the JSON export — the full field-by-field breakdown is on the export formats page.
Nothing is added to it. No identifier is generated for you, no timestamp of your visits is kept, and there is no hidden metadata attached to your events.
Verify it yourself
You do not have to take our word for any of this. In Chrome, Edge or Firefox, press F12 to open developer tools, then:
- Open the Application tab (Chrome and Edge) or Storage tab (Firefox), expand Local Storage, and select this site. You will see the
sm_timetable_v1key with your timetable in it, in readable JSON. - Open the Network tab, then add or drag an event. No request carrying your timetable will appear, because none is made.
The page source is unminified and readable too. The storage and export logic is all there, near the bottom of the page.
What will erase your timetable
Local storage is durable but it is not permanent, and it is not backed up by anyone. These will all wipe it:
- Clearing browsing data with "cookies and other site data" selected. This is the most common cause by a wide margin.
- Private or incognito windows. Storage there is discarded when you close the window. If you built a timetable in a private tab, it is gone once that tab closes.
- Using a different browser or device. Storage is per browser, per device. A timetable made in Chrome on a laptop does not exist in Safari, or on a phone.
- Browser storage eviction. Safari in particular clears site storage for sites you have not returned to in about a week. If you use this tool occasionally on an iPhone or iPad, assume the timetable will not be waiting for you.
- Browser extensions that clear site data automatically, and some "privacy cleaner" utilities.
- A full storage quota. Browsers cap local storage per site, typically around 5 MB. Ordinary timetables use a tiny fraction of that, so this is unlikely, but if a write fails the indicator shows a dash instead of a check mark.
If a timetable matters, export the JSON
None of the above is recoverable. We cannot restore a lost timetable, because we never had a copy of it — that is the direct trade-off for not holding your data. Exporting a JSON file takes one click and is the only real backup. It is also how you move a timetable to another browser, another machine, or a phone.
What this page does collect
"Your timetable stays on your device" is precise, and it is true. It is not the same claim as "nothing at all is collected", and it would be dishonest to let the first imply the second. The page loads several third-party scripts, and they behave the way third-party scripts normally do.
| What runs | Why | What it can see |
|---|---|---|
| Google Analytics 4 | Traffic measurement — which pages get used, roughly where visitors are | Standard analytics data: pages viewed, approximate location, device and browser, referrer |
| Ezoic, including its consent manager | Advertising, which is what keeps the tool free | Ad-related data as disclosed through the consent notice |
| Cloudflare (cdnjs) | Serves the two libraries used for PNG and PDF export | Your IP address and browser, as with any file request |
| Google Fonts | Serves the typefaces used on the page | Your IP address and browser |
None of these receive your timetable. Your events are never placed into a network request, so there is nothing for them to collect — they see that a page was loaded, not what you put on it. Your consent choices are handled through the privacy notice, and the full disclosure is in the Privacy Policy.
Deleting everything
To remove your timetable from a device completely, clear site data for this site in your browser settings, or delete the sm_timetable_v1 key directly from the Application or Storage tab described above. Either removes it immediately and permanently.
There is no account to close and no deletion request to send us, because there is nothing held on our side to delete. If you have a question about any of this, the contact page is the place to ask.