Privacy and terms

Who runs this site

The maintainer of the mbse-workflow repository (GitHub user cosmindxu), personally — not a company or a school. The site is built from that public repository and hosted on GitHub Pages.

What the app is

Sysprose is a modeller that runs entirely in your browser. It is open-source software under the MIT licence. Nothing you do in it is sent to a server of ours: there is none. The site's own code sets no cookies and runs no analytics or advertising code; once you use Drive ▾, Google's scripts run in the page too (see third parties), and what they keep is Google's. The Collaborate command connects only to a relay that you start and name yourself.

When Google is contacted

Never, until you do one of these:

• open Drive ▾ on the app's toolbar;
• press Ctrl/⌘ + Shift + S (Save to Drive) in the app;
• follow a link to a file in Google Drive (an app address ending in ?drive=).

Each of these loads Google's sign-in script from accounts.google.com, so Google receives your network address and this site's address (and its own cookies, if you are signed in to Google in this browser). Signing in is a separate click after that, in a window shown by Google: it receives the app's client ID, and asks you to let the app use the Drive files you make or choose with it — Google's drive.file permission — and no others.

What Google data the app reads

• Only files you create with the app or choose in Google's file picker. The drive.file permission does not let the app see the rest of your Drive. For those files it reads their text and these metadata fields, exactly as it asks Google for them:

  id, name, mimeType, version, modifiedTime, headRevisionId, md5Checksum, resourceKey, webViewLink, trashed, capabilities(canEdit), lastModifyingUser(displayName)

• Your account's email address and display name (user(emailAddress, displayName)), shown in the Drive panel and in the app's messages so you can see which account is signed in. The app also hands the email back to Google as a hint when it renews your sign-in, and checks that the renewed sign-in is the same account; if it is not, the app detaches the Drive file it had open and clears the Recent list. They are not used for anything else and are not kept after sign-out or tab close.

Where it is processed, and who gets it

In your browser. Your files and their metadata travel between your browser and Google's own APIs (www.googleapis.com, and for the file picker apis.google.com and docs.google.com), each time at your request: Save to Drive, Save to Drive as…, opening a file, the Recent list, Browse Drive…. They are never sent to the site's operator or to anyone else, not used for advertising, and not sold. Information received from Google APIs is used as Google's API Services User Data Policy requires, including its Limited Use requirements, which we follow voluntarily.

What is stored, and where

• Your Google sign-in (an access token): the app keeps it in the page's memory only, and never puts it in the browser's storage or in an address. It stays there until you sign out or close the tab; it stops working after about an hour. Google's file picker receives it when you use Browse Drive…, and what the picker does with it is Google's.
• Projects you keep with the app's Save: in this browser's IndexedDB (localStorage if IndexedDB is unavailable), on this device only. With a Drive file open, Save and Ctrl/⌘ + S also keep a copy of the model here, as they always do. On a shared computer, remove these copies by clearing this site's data (cosmindxu.github.io) in the browser's settings.
• Preferences — the theme, the palette's collapsed state, your regroup scenarios — in this browser's localStorage, as before Google Drive existed.
• The app's own files, kept by its service worker in the browser's cache so it opens offline.
• Nothing of Google's from the app: the app writes no token or account detail to browser storage. (The model copies that Save keeps, above, are yours.)
• Files you save to Drive: in your Google Drive, under your account.

Sharing and earlier versions

A Drive file is shared only through Google Drive's own sharing controls, by you. A link the app copies for you (…/app/?drive= and the file id) opens the file only for someone the file is shared with; opening it sends that id to this site's host, like any address. When you save, Drive keeps the earlier version of the file for about 30 days (up to 100 versions) unless you mark it Keep forever under Manage versions in Drive.

Withdrawing the app's access

Drive ▾ → Sign out asks Google to revoke the app's access, then forgets your sign-in, the Recent list and the attached file. When your sign-in has already expired, it first asks Google for a fresh one in a brief window, because Google needs one to revoke. If Google does not accept the request, the app says so, and you can remove Sysprose yourself under your Google Account › Security › Third-party access, as the app's message says. Files you saved stay in your Drive until you delete them there.

School accounts and students under 18

A Google Workspace for Education account that the school has designated as under 18 can sign in only once the school's administrator allows the app; until then Google shows an Access blocked page inside the sign-in window. The administrator allows it in the Admin console under Security → Access and data control → API controls → Manage third-party app access → Add app, by its OAuth client ID; Limited access is enough for drive.file.

The app's OAuth client ID: (client ID: to be filled when the deployment is configured)

Third parties

• GitHub Pages hosts the site and, like any web host, receives your network address with every page and file it serves — GitHub's privacy statement.
• Google serves the sign-in script, the sign-in window, the file picker and the Drive API, loaded at run time from Google's own addresses — Google's privacy policy and the Google APIs Terms of Service.

Terms

The site and the app are provided as is. Sysprose is MIT-licensed software and its standard-library data is under EPL-2.0 (see the licences); both come with no warranty of any kind. You are responsible for what you store in your browser and in your Google Drive, and for keeping copies of anything you need. Using the Google Drive commands also means using Google's services under Google's terms.

Contact

Questions and requests go to the repository's GitHub issues. Issues are public, so do not put personal data in one.