Privacy Policy

1. Who is responsible

E-Vory is a free, open-source tool published by an individual developer (@frianasoa on GitHub). It is not a company, and it is not affiliated with any institution, university or employer.

Because E-Vory processes your files only on your own device, you remain the controller of any personal data you put into it. The paragraphs below explain exactly what happens to it.

2. What data E-Vory handles

The files you load can contain personal data about other people. Typically:

• Names of panel members and presenters, as written in your timetable
• Presentation titles, times and room numbers
• The hours each person said they can attend
• Free-text comments and requests from your availability form
• Any other column that happens to be in the same spreadsheet

E-Vory reads these to build the programme and the report. It does not transmit them, index them, profile anyone, or keep them anywhere except on the device you are using.

3. Where processing happens

Everything happens in your browser. Opening E-Vory downloads a static page, a stylesheet, some JavaScript and the solver (a WebAssembly file) from the web host. From then on:

• Spreadsheets are parsed in the page.
• The optimisation is solved in a background thread in the page.
• The report and log are generated in the page.
• Downloads of the report, the log and the timetable workbook are produced by your browser from data already on your device.

There is no application server, no database and no processing queue behind E-Vory. E-Vory works offline once the page has loaded, which you can verify by disconnecting and running an optimisation.

4. What is stored on your device

So that a reload or an accidentally closed tab does not lose your work, E-Vory saves some things in your browser's own storage for this site. Nothing here is transmitted anywhere.

Local storage (keys beginning evory:)

• The last programme and availability files you loaded, so they are still there when you come back
• Which spreadsheet column plays which role, including choices you corrected by hand
• Your settings: preferences per person, penalty weights, the time limit and the suggested-times settings
• Which collapsible panels you left open

IndexedDB (a database named evory)

• The last 10 results for the files you loaded — the report, the log and the proposed timetable workbook, so you can reopen an earlier run and still download it. These contain the names from your programme.

Clearing it

• Forget files and results saved on this device, at the bottom of the app's left column, removes the saved programme, the saved availability, the column choices and every saved result.
• Reset settings to defaults, under Settings, clears the preferences and weights you entered.
• Clearing site data for this site in your browser's settings removes everything above at once. So does using a private window, which keeps nothing after you close it.

5. The optional Google imports

Instead of choosing a file on your computer, you can load one from Google in two ways. Both are optional, both start only when you use them, and both end the same way: the file is read in your browser exactly as an uploaded file is, and is saved on your device as described in section 4. E-Vory is not affiliated with Google.

A Google Sheets link

You may paste a Google Sheets link to load availability responses. If you do:

• Your browser requests the sheet directly from Google. Nothing passes through E-Vory.
• The request is made without credentials, so it only works for a sheet shared as “Anyone with the link can view”. E-Vory cannot read a private sheet this way, and does not ask you to sign in.
• If the responses should not be publicly readable, pick the sheet from Google Drive instead (below), or download it and load the file, which involves no network request at all.

Picking a file from Google Drive

Where this site has been set up for it, From Google Drive appears under each of the two uploads. It uses Google's own sign-in and Google's own file picker, and works with private files too.

What happens.

• Google's sign-in and picker scripts (from accounts.google.com and apis.google.com) are fetched only once you point at or focus the button — never on page load. If you never use the button, nothing is sent to Google.
• You sign in to Google in Google's own window, not to E-Vory. E-Vory never sees your password and keeps no account of any kind.
• You choose a file in Google's picker. E-Vory does not see the list of files it shows you — only the file you finally pick.
• Your browser downloads that one file straight from Google Drive. A Google Sheet is exported as .xlsx on the way. The file does not pass through any E-Vory server, because there is none.

The permission asked for.

E-Vory asks for one permission, the drive.file scope, which Google describes on its consent screen as access to only the specific Google Drive files you use with this app. In practice that means the files you pick in the picker, and nothing else in your Drive. Google's wording also covers editing and deleting those files, because that is how the scope is defined; E-Vory only ever downloads them. It never writes, changes, creates, moves, shares or deletes anything in your Drive.

E-Vory does not ask for your name, email address, profile picture or contacts, and Google does not give it any of them.

What E-Vory receives from Google, and what it does with it.

• A short-lived access token, valid for about an hour. It is kept in the page's memory only — never written to local storage, IndexedDB or a cookie — and is sent to nobody but Google, with the download request. Closing or reloading the tab discards it.
• The picked file's identifier, name and type, used to download it and to know how to read it.
• The file's contents, used for exactly what an uploaded file is used for: building the programme and the report. They are saved on your device like an uploaded file (section 4), and cleared the same way.

None of this is transferred to the developer or to anyone else, used for advertising, sold, or used to train any model. E-Vory's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Withdrawing access.

Google remembers that you allowed E-Vory, and which files you picked with it, so a later pick may not ask again. You can withdraw that at any time under Third-party apps & services in your Google Account. Doing so does not affect anything saved on your device; section 4 explains how to clear that.

What Google sees

For either import, Google handles the request, the sign-in and the download under its own Privacy Policy, and decides what it logs about them.

Apart from these Google imports, when you use them, and the visit statistics described in section 8, E-Vory makes no requests to any third party. It loads no fonts, stylesheets or images from external services; everything the tool needs is served from its own address.

6. What E-Vory does not do

E-Vory does not:

• Upload, copy or retain your programme, availability, results or reports
• Read anything in your Google Drive other than a file you pick, or write, change or delete anything there
• Keep your Google access token beyond the open tab, or store it anywhere
• Use cookies, or any advertising, cross-site tracking or fingerprinting technology
• Record what you do inside the tool: no event tracking, telemetry or crash reports. Only page visits are counted (section 8).
• Ask you to create an account, or ask for your email address. Picking from Google Drive uses the Google account you already have, and signs you in to Google, not to E-Vory.
• Show adverts, or sell, share or trade data with anyone
• Use your data to train any model

7. Web hosting logs

E-Vory is served as a static site by a hosting provider (currently Cloudflare Pages). Like any web server, that provider may record ordinary request information — such as IP address, time, the file requested and your browser's user-agent string — for delivery, security and abuse prevention. This is handled by the provider under its own policies, and it is limited to the act of fetching the page.

Your programme data is never part of those logs, because your files are never sent to the server. The only thing the host sees is that someone downloaded the page.

8. Anonymous visit statistics

To know roughly how many people use E-Vory and where they find it, the site uses Cloudflare Web Analytics. Cloudflare adds a small script (static.cloudflareinsights.com/beacon.min.js) to each page, and when a page loads it sends one report to cloudflareinsights.com containing:

• The page address visited, such as / or /privacy
• The site you came from (the referrer), if your browser shares it
• Your browser, operating system and device type, taken from the user-agent string
• Your country, derived from your IP address
• How long the page took to load and render

It does not:

• Set cookies or use your browser's local storage, so nothing links one visit to the next
• Fingerprint your browser or build a profile of you
• See anything you do inside the tool: the files you load, their names, columns or contents, your settings, or your results. E-Vory never puts any of that in the page address, so it cannot appear in the report.

The developer sees only aggregated counts in the Cloudflare dashboard, not individual visitors. Cloudflare processes the report under the Cloudflare Privacy Policy. If you prefer not to be counted, a content blocker that blocks cloudflareinsights.com stops the report without affecting the tool in any way.

9. Personal data about other people

A programme almost always contains other people's names, and an availability form often contains their comments. When you use E-Vory for this, you are handling their personal data under your own institution's rules and under the law that applies to you (for example the GDPR in the EU).

E-Vory is designed to make that easier rather than harder:

• The data never leaves your device, so there is no transfer to a third party to justify.
• There is no central store, so a deletion request is satisfied by clearing your own browser storage.
• There are no sub-processors to disclose for the core function of the tool.

Please still collect only what you need, keep results no longer than useful, and remember that a downloaded report is an ordinary file containing names — treat it like any other document with personal data in it.

10. Children

E-Vory is a scheduling tool for people organising events, not a service aimed at children, and it does not knowingly collect personal data from anyone. A programme may of course list young participants; that data stays on the organiser's device like any other.

11. Security

Because there is no central store, there is no central breach to suffer: nobody can compromise a server and obtain your programmes, since no server ever holds one. The realistic risks are local ones — someone with access to your computer, browser profile or downloaded files — and section 4 explains how to clear them.

If you pick files from Google Drive, the access Google grants is limited to those files, the token that uses it lives only in the open tab, and you can withdraw the access itself from your Google Account at any time (section 5).

The site is served over HTTPS with a strict set of security headers, and the code is public, so you can audit every claim on this page yourself. If you believe you have found a security or privacy problem, please report it at github.com/frianasoa/evory/issues.

12. Changes to this policy

If E-Vory gains a feature that changes how data is handled, this page will be updated and the date at the top changed with it. The history of every change is visible in the project's public repository. The commitment that your files are not uploaded is a design principle, not a setting — it will not be quietly reversed.

13. Contact

Questions about this policy, or about how E-Vory handles anything, are welcome as an issue on GitHub.