Security and data

Updated 4 October 2026

This page lists what you can check for yourself: where the app connects, which permissions it asks for, where the data lives and who signed the files. In short: the workshop's data stays in the workshop's own Google account and on its own devices. Primpex Oy has no storage of its own with workshops' data.

1. Where the app connects

WS Calendar for Windows and Android connects only to the addresses in this list. You can check it with any tool that shows network connections, for example TCPView.

accounts.google.com — Google sign-in. It opens in your browser, not in the app.
oauth2.googleapis.com — granting and revoking Google access. The phone gets its access here directly; the computer contacts it when you sign out.
www.googleapis.com — Google Calendar and Google Drive.
tasks.googleapis.com — Google Tasks for shared notes (computer only).
googleusercontent.com — thumbnails of photos from your Google Drive.
us-central1-my-calendar-app-507519.cloudfunctions.net — Primpex Oy's sign-in function in Google Cloud (computer only, see section 3).
wscalendar.fi — checking for a new version and the list of revoked licence codes. The app only downloads two small files; no workshop data is sent.

Links to Google Drive files and to pages of this site open in your browser. The app has no ads, no trackers and no usage statistics.

The app's identifiers at Google — they are visible in the address of the sign-in page and are not secret:

Windows: 600845232795-20t0gg43lba3a4ir6nbcucgpu9hn7l7h.apps.googleusercontent.com
Android (version from this site): 600845232795-j7tfofargcv8280940arpm6qohm4ls1f.apps.googleusercontent.com

2. Which permissions the app asks for

At Google

Calendar events (calendar.events) — read and change bookings in the workshop's calendar.
Drive files created by the app (drive.file) — only the WSCalendar folder and files the app created itself. It cannot see the rest of your Drive.
Google Tasks (tasks) — computer only, for shared notes.
The account's e-mail address (openid email) — only when the owner is assigned or the owner PIN is restored. This is a separate sign-in that confirms the address; the app gets no new permissions from it.

The app cannot see Gmail, contacts or the rest of your Drive. It never gets your Google password: you sign in on Google's page.

On an Android phone

Internet.
Camera — photos for bookings and tyres.
On Android 12 and older — reading files, to pick a photo. Newer Android versions do not have this permission.

The app does not ask for access to messages, contacts, location or the gallery. Photos from the gallery are picked through Android's own window: the app receives only the photos you chose.

On a Windows computer

The app installs into the user's folder and runs without administrator rights. It needs no special permissions.

3. Where the data lives and what Primpex Oy sees

Bookings — in the workshop's Google Calendar.
Stock, tyre hotel with photos, notes, work templates, settings and printed documents — in the WSCalendar folder on the workshop's Google Drive and in the database on each of its devices.
Backups — on the workshop's computer.

What passes through us. Only Google sign-in on the computer. When you sign in and when access is refreshed (about once an hour), the request passes through our sign-in function: it adds the app secret, forwards the request to Google and returns the reply. The function does not store tokens and does not write them to logs; Google Cloud's log keeps only technical details — time, network address and response code. The secret is kept on the server so that nobody can pass their own program off as ours. The phone signs in to Google directly, without the function.

What we do not have. Workshops' customer lists, bookings, receipts, photos or files. Error logs are not sent anywhere automatically: the log stays on your computer, and you decide whether to send it.

4. File signatures

Windows. The installer and the app itself are signed by Primpex Oy. To check: right-click the file → Properties → Digital Signatures.
Android. The app installed from a file on this site is for now signed with the standard Android key; the Google Play version will have a permanent signature.
Checksums. The SHA-256 of each file is shown on the download page next to its link. To compare on Windows: certutil -hashfile file_name SHA256.

5. Reporting a vulnerability

If you have found a weakness, write to info@wscalendar.fi. Describe what you saw, how to reproduce it and which version you tested. Testing is welcome as long as it does not touch other people's data. For automated tools there is a security.txt file.

6. Code review

We will show the code of the sign-in function and of the app's network part (Google sign-in, update check) for review on request. The full source code of the app is closed.

7. Questions and answers

Where is my workshop's data stored?

In your Google account (Calendar, Drive, Tasks) and on your own computers and phones. We have no storage of our own for workshop data: the customer list, bookings and files are not sent to the developer.

Which Google permissions does the app need?

Viewing and editing calendar events, access only to the Drive files the app itself created, and Google Tasks (on the computer, for shared notes). The app cannot see Gmail or your other Drive files.

Does the app get my Google password?

No. You sign in on Google's own page in the browser. The app only receives permission to work within the rights you granted.

Does anything go through the developer's server?

Only the Google sign-in on the computer. When you sign in and when access is renewed (about once an hour), the request passes through our function in Google Cloud: it adds the app secret, forwards the request to Google and returns the answer. It does not store tokens or write them to logs. The secret is kept on the server so that nobody can impersonate the app in our name. The phone signs in to Google directly.

Where does the app connect to?

Google (Calendar, Drive, Tasks, sign-in), our sign-in function, and wscalendar.fi to check for a new version and the list of revoked licence codes. There are no other connections; the full list of addresses is in section 1.

Has Google verified the app?

Yes. In October 2026 WS Calendar passed Google's verification (OAuth verification): Google checked which access the app asks for and why. The “app not verified” warning is no longer shown.

Are the app files signed?

The Windows installer and the program are signed by Primpex Oy (file properties → "Digital Signatures"). The Android app installed from a file is currently signed with the standard Android key; the Google Play version will have the permanent signature.

Are error logs sent to the developer?

No, nothing is sent automatically. The log stays on your computer and you decide whether to send it. It may contain details from bookings, such as a licence plate — look through it before sending.

How do I back up, and take my data with me if I stop using the app?

The database is copied automatically at start-up and once a day (Settings → Owner → Backups). Bookings stay in your Google Calendar and shared data in the WSCalendar folder on your Google Drive; export — Settings → Export and import.

Does mechanic mode restrict access to data?

Only inside the app. If a mechanic signs in with the same workshop Google account, they see the same as the office through Google Calendar and Drive. Strict separation needs separate Google accounts.

How do I revoke the app's access?

In your Google account settings: Security → Third-party apps and services. Access through Google stops at once; data on your computers and backups are deleted separately.

What is the safest way to start testing?

With a separate workshop Google account and made-up bookings. Check the backup, then move on to real bookings.