Privacy Policy

Last updated: 18 October 2026

Workomap is a public map of SAP professionals. This policy explains what personal data we process, why, and what you can do about it. It describes the service as it actually works today — not as it might work later.

1. Who is responsible

Workomap is operated by an individual established in the European Union, acting as the data controller under the General Data Protection Regulation (GDPR). You can reach the controller at tan.gravam@gravam.com.

2. The most important thing to understand

Workomap is a public professional map. If you put yourself on the map, the profile information listed in section 4 is visible to anyone on the internet, without signing in, and may be indexed by search engines. Joining is entirely voluntary, and you can ask us to remove your profile at any time (section 10).

3. What we collect

Sign-in data. Workomap uses Google sign-in only. When you sign in, we receive your email address and a Google account identifier, which our authentication provider stores to keep you signed in.
Profile data you provide. Your display name, your city (city level only), your primary SAP role, your SAP areas, the year you started working with SAP, an optional free-text “About” section, and — only if you add it — the address of your LinkedIn profile. After joining you can also say what work you are open to (freelance projects, permanent roles, both, or not looking), from when you are available, whether you work remotely, hybrid or on site, and up to five working languages; each of these is optional. If you chose “Other SAP professional” as your role, we also keep the role title you typed; it is shown to nobody but you.
Activity date. We keep the date (day only, no time) you last opened your own account page. It tells us whether members come back; it is never shown publicly, never used to rank or sort anyone, and is written at most once a day.
Profile views. We count how many times your public profile page is opened, as one number per day. The count is not linked to who opened the page: no visitor, address or session is stored with it. Only you see it, on your own account page. To count a visitor once an hour rather than at every reload, our server keeps, in memory only, which address opened which profile page for one hour; it is never written to our database.
Rate survey reports. If you add a report to the SAP rate survey, we store the six answers (the kind of pay, the amount and its currency, the country, the SAP role and the years of experience) and the day. A report is not linked to an account, a name, a session or an address, so it cannot be traced back to you, and for the same reason we cannot find it again to change or remove it for you. Figures are worked out once a day from the days before, count at most twenty reports a day for a country, are rounded, and are shown for a country only from five such reports (the middle half from ten). To limit how many reports one connection can add, our server keeps, in memory only, the address that added reports that day; it is never written to our database.
Technical data. The Workomap application processes your IP address momentarily to apply rate limits; it is held only in memory for that check and is never written to our database. When something goes wrong, our servers log a request identifier, the route and an error message — no IP address and no profile data. Separately, the infrastructure providers that host and deliver the site (section 9) keep their own delivery, performance and security logs, and those do contain IP addresses. That processing is carried out by them under their own terms; it is not something the Workomap application controls or reads.
Consent record. When you join we record that you accepted these documents, which version you accepted (this one is version 2026-10-18, matching the date at the top of the page), that you confirmed you are 18 or over, and when. It is kept as an audit trail, so earlier records keep the version that was actually shown at the time.

We do not collect your exact location, your date of birth, your phone number, payment details, your CV, or a profile photo.

4. What is public on your profile

Exactly these fields are public:

your public profile address and display name;
your “About” text, if you wrote one;
the address of your LinkedIn profile, if you added one — shown as a “Connect on LinkedIn” button;
your primary SAP role and your SAP areas;
what you said you are open to, how you work and your working languages, if you added them; and the date you are available from, which is shown until 90 days after you last saved it, or 90 days after the date itself if that is later;
your city, region and country — city level only;
the year you started working with SAP;
an early-member badge, if you were one of the first members;
whether you were the first member mapped in your city or your country;
the date you joined the map;
the number of members publicly on the map in your city and country.

Your email address, your Google account identifier and all internal database identifiers are never published, never shown on the map, and never returned by our public API.

5. Location: city level only

We store and show the city you choose, never a precise location. We do not use GPS, we do not read your device location, and we do not derive a location from your IP address. When you search for your city during sign-up, that search runs from your browser directly against Mapbox, so Mapbox receives your IP address for those requests; we then ask Mapbox to resolve your chosen city into a canonical city record. After a city has been resolved once, later sign-ups reuse the stored record.

6. How the map counts communities

Every number shown on the map — country totals, city totals, role and SAP-area breakdowns, and filtered results — is a count of profiles that are publicly on the map, from a city's first member on. Counts are computed in the database from published profiles; nothing is estimated, and a hidden or deleted profile leaves every count at once. A count reveals nothing a profile page does not already show, because every profile on the map is public by its owner's choice. Until 26 September 2026 the map withheld counts below five; that rule is retired.

7. Why we may process your data (legal bases)

Performance of a contract (Art. 6(1)(b) GDPR): creating your account and publishing the profile you asked us to publish.
Legitimate interests (Art. 6(1)(f) GDPR): keeping the service available and protecting it from abuse, for example rate limiting and error logging.
Consent (Art. 6(1)(a) GDPR): not currently relied upon. Our product measurement is first-party, aggregate and carries no advertising or cross-site tracking, so it rests on legitimate interests rather than consent (section 8).

8. Cookies and analytics

Workomap itself sets only the cookies required to keep you signed in. The content-delivery edge the site is served through (section 9) may additionally set one short-lived security cookie of its own to tell browsers from automated traffic; it carries no Workomap data and we never read it. We run no advertising, no third-party tracking and no cross-site profiling. No analytics company receives your data, because we do not use one.

We do measure how the product is used, using our own servers and our own database. When you open the map or start joining, we record the event itself — that a map was viewed, a filter applied, a join step reached — along with a small fixed set of context: which map, which page template, a two-letter country code, whether you were signed in, and which door you arrived through — for example the map, a guide, or an invitation link a colleague sent you.

To count visits rather than repeat page loads, your browser holds a random identifier for the current tab session. It is stored in sessionStorage, not a cookie, it disappears when you close the tab, and it is never linked to your account, your profile or your IP address. Usage events are deleted after 90 days; the clean-up runs automatically as the service is used.

Two things are kept in your browser's own storage, on your device. An unfinished join (what you have chosen so far: city, role, SAP areas, start year and name, and the door you arrived through) is kept so that a refresh or the Google sign-in does not lose it. It is used for 24 hours and removed the next time you open the join after that, and it is sent to us as a whole only when you publish your profile; choosing a city asks our server about that city, as any search does. And if you play the T-code of the day, your guesses for the day and a tally of your games are held there and are never sent to us. Clearing the site's data in your browser removes both. A few flags for the current tab (that you arrived through a shared link, that you have seen your welcome page, that you signed in again to delete your account) are kept in sessionStorage and disappear with the tab; so are unsaved edits to your profile, if your session ends while you are editing, until you have signed in again.

We deliberately do not record your name, email, profile address, what you typed into a search box, the text of your About, or the address of an individual profile you visited. (The count of how often a profile page is opened, in section 3, is a number per profile per day and carries no trace of the visitor.) There is no session recording, no heatmap, no automatic capture of page content, and nothing is shared with anyone else.

9. Who else processes your data

Google — sign-in. Google authenticates you and tells us your email address.
Supabase — database and authentication hosting.
DigitalOcean — application hosting, including the Cloudflare content-delivery edge it serves the site through. Every request to Workomap passes through that edge.
Mapbox — map tiles and city lookup. Your browser contacts Mapbox directly when the map loads and when you search for your city, so Mapbox receives your IP address for those requests.

These providers keep their own delivery, performance and security logs, which contain IP addresses and request details. We rely on them to run the service; that logging is theirs, under their own terms, and is separate from what the Workomap application itself stores (section 3).

We do not sell personal data, and we do not share it for advertising. The Workomap application is hosted in the Netherlands (Amsterdam region), inside the European Economic Area. Some providers may process data in other regions; where data leaves the EEA it is covered by the safeguards in those providers' data processing terms, such as the EU Standard Contractual Clauses.

10. Keeping and deleting your data

We keep your account and profile for as long as you are on the map, and you control all of it yourself, from your profile page: your display name, city, role, SAP areas, start year, “About” text and what you are open to are all editable, you can hide your profile from the map or leave it entirely (and rejoin later with your original founding status), and you can delete your account.

Deleting your account erases your name, your “About” text, your LinkedIn address and any role title you typed immediately, clears your SAP areas, what you said you are open to, your working languages, the count of your profile views and your activity date, replaces your old profile address with a neutral placeholder (it stops resolving and is not reused), removes your profile from the map, search and public statistics at the same moment, and removes your Google sign-in. For your safety, deletion asks you to type a confirmation and, if you signed in a while ago, to sign in again first. What we keep afterwards, on a record that no public page can read: the date you joined (and of any return and of the deletion itself), your founding sequence, your SAP role, your start year, your city, and whether you were the first member there or in its country — so that founding numbers are never reissued and our statistics stay honest — and your consent history (the law expects us to be able to show what was agreed). None of that identifies you.

11. Your rights

Under the GDPR you have the right to access your data, to correct it, to have it erased, to restrict or object to processing, and to receive your data in a portable form. Two of these you can exercise yourself, without asking us and without waiting: Download my data on your account page gives you a JSON file containing everything we store about you, and Delete account on the same page ends it. For anything else, email tan.gravam@gravam.com. You also have the right to lodge a complaint with the data protection supervisory authority in your country.

12. Minimum age

Workomap accounts and map profiles are for working professionals aged 18 or over, and joining records your confirmation that you are 18 or older. We do not knowingly create an account for, or publish a profile of, anyone under 18; if you believe we have, contact us and we will remove it. Browsing the public map needs no account and we do not ask visitors their age, so this section is about account and profile participation rather than a claim that no data of any under-18 visitor is ever processed — technical processing such as the delivery and security logging described in sections 3 and 9 applies to every visitor.

13. Changes to this policy

If we change how we handle personal data, we update this page and the date at the top. Material changes will be communicated before they take effect.