Privacy policy
Version of 12.11.2026
Only the German version is legally binding.
Controller
Zugora is operated by Hartmann Association, an association based in Zug, Switzerland. You can find our contact details in the legal notice. We process personal data under the Swiss Federal Act on Data Protection (FADP).
Public pages
Without your consent, the public pages set no cookies for advertising, tracking or statistics; what applies with your consent is described in the section «Statistics with Google Analytics (consent only)». Your settings at the bottom of every page are kept only by your browser in its local storage (localStorage): the appearance under «zg-theme» (automatic, light or dark) and a language you chose explicitly, or your account language, under «zg-lang». Your browser then also stores the cookie «zg_lang» (content: the code of the chosen language, e.g. «de» or «fr», valid for 1 year) so that zugora.ch and the installed app open straight in that language; the server reads the cookie only at the start address zugora.ch and under zugora.ch/app. Without a choice, Zugora follows your device settings. This information is technically necessary and is not analysed; you can delete or block it in your browser at any time, and your device settings then apply again. With an account, we also store the appearance in your profile so that it applies on all your devices.
When you are signed in, your browser keeps only the hint «signed in» in its local storage under «zg-account» (content «1», no key and no proof). Only with this hint does a public page ask zugora.ch/app for your username, your first name (only for the greeting «Hello Erika» in the «My community» area), the number of unread messages and your roles, to show your account menu at the top and your functions on listings, housing and events; the browser keeps the answer for at most one minute in the storage of the tab (sessionStorage «zg-me»), and briefly «zg-logged-out» for the message «You are signed out.». When you sign out, Zugora deletes this information. The public pages themselves are the same for everyone and never contain information about your account.
Zugora runs on Cloudflare, which creates technically necessary server logs without query strings in addresses; they are deleted after 7 days. To measure reach on the public pages (not on pages with a personal link) we use Cloudflare Web Analytics without cookies, without an identifier in your browser and without profiling; it counts page views and measures loading times. It is different with Google Analytics, which runs through Cloudflare Zaraz: it stores an identifier in your browser and therefore runs only after your consent (see «Statistics with Google Analytics (consent only)»). Cloudflare Zaraz also shows the consent window.
On the map, the «Hiking trails» layer, when you switch it on, loads map tiles directly from the federal geodata service (Federal Office of Topography swisstopo, wmts.geo.admin.ch). In the close-up view of the 3D map (closer than about 2 km or 3.6 km), the map also loads the swissBUILDINGS3D building models and the SWISSIMAGE aerial imagery directly from swisstopo (3d.geo.admin.ch, wmts.geo.admin.ch). swisstopo then receives your IP address and the usual details of your browser; the privacy policy of geo.admin.ch applies. Otherwise the map only loads data from zugora.ch.
In the legal notice, the "Show email address" button only loads Cloudflare Turnstile once you click it. Turnstile uses browser characteristics to check that a human is requesting the address; for this, a verification token and your IP address are sent to Cloudflare.
The search in the page header (AI search) sends your search term, as you type, directly to Cloudflare AI Search (web-search.zugora.ch); Cloudflare receives the search term, your IP address and the usual details of your browser. So that results arrive faster, your browser already opens the connection to web-search.zugora.ch as soon as you point at or tap the search button or a search field, or move to it with the keyboard; no search term is sent at that point. The AI search keeps nothing in your browser.
Without JavaScript, the search button leads to the «Search» page (zugora.ch/en/search/), where Zugora searches itself. Your search term is then part of the address of the results page and goes, with your IP address and the usual details of your browser, to our server at Cloudflare. We use it only to compute the results and do not store it: not in logs, not in caches and not in a database. To prevent abuse, we count searches per network range of your IP address in 10-minute periods; for this we store only a short code of the network range (a truncated hash value) and the count, never the IP address or the search term, and we delete the counter after 24 hours. When you click a result, the results page passes on no referring address; Google Analytics (consent only) receives, as on all pages, the address without query parameters, so without the search term. Your browser does not store the results page but keeps its address in the history like any page you visit.
Statistics with Google Analytics (consent only)
Zugora can use Google Analytics 4 to measure how the pages are used. This happens only if you consent. We do not load Google Analytics ourselves but through Cloudflare Zaraz, a Cloudflare service that manages such tools and shows the consent window. These statistics have been in place since 17 October 2026.
Purpose: We want to understand how Zugora is used, for example which pages are in demand and how people find them, so that we can improve content and features. We do not build profiles of individual people from it and do not use the analysis for advertising.
Legal basis and withdrawal: The legal basis is your consent. On your first visit a window asks whether Zugora may measure the statistics. As long as you do not agree, including when you decline or do not answer, Google Analytics does not run: no measurement data is sent to Google and no cookies or similar identifiers of Google Analytics are set. You can change or withdraw your choice at any time: the link «Cookie settings» at the bottom of the public pages opens the window again. A withdrawal applies from then on; what was measured until then remains lawful. You can use Zugora fully without consenting. The reach measurement with Cloudflare Web Analytics (see «Public pages») does not depend on this choice, because it neither sets cookies nor stores an identifier.
Where nothing is measured: In the account area (zugora.ch/app) and on pages you open through a personal link (invitations and unsubscribe links from emails), neither Cloudflare Zaraz nor Cloudflare Web Analytics runs: nothing is measured there, and the consent window does not appear. Elsewhere Zaraz passes the address of the page without query parameters: everything from the question mark on is removed beforehand.
Data: With your consent, Google Analytics processes pseudonymous usage data: the address of the page you view (without query parameters) and its title, the page you come from (as your browser reports it), time and course of the visit, device and browser details (e.g. device type, operating system, browser, language, screen size), an approximate location (country, region or city) derived from your IP address, and a random, pseudonymous identifier that recognises your browser. Google receives the IP address of your device and the browser identifier (user agent) in the process; according to Google, Google Analytics 4 does not store IP addresses and uses them only to derive the approximate location. From us, Google receives no account details such as your name, username or email address, and we do not link the statistics to an account.
Cloudflare: The measurement data passes through Cloudflare Zaraz. Cloudflare also processes your IP address as a processor (see «Processors»).
Recipients of Google Analytics: Google Ireland Limited (Ireland) and Google LLC (USA). For the transfer to the USA the Swiss-U.S. and the EU-U.S. Data Privacy Framework apply, under which Google LLC is certified; as a fallback the standard contractual clauses apply.
Cookies and identifiers: The consent window remembers your choice in the cookie «zaraz-consent». It contains only what you said yes or no to and is technically necessary; Zaraz therefore sets it as soon as you choose, even if you decline. Also technically necessary is the empty cookie «cf_zaraz_client» (valid for 1 year), which Zaraz sets on your first visit. Only after your consent does Zaraz set the cookies «cfz_google-analytics_v4» and «cfzs_google-analytics_v4» for the statistics. They contain a random identifier that recognises your browser and counters for visit and session. The identifier is valid for 1 year, the session identifier for 30 minutes; «cfzs_google-analytics_v4» is valid until you close the browser. Google sets no cookie of its own such as «_ga» in your browser. The cookies apply to zugora.ch and its subdomains. The cookie «cfz_zaraz-analytics» of the former built-in measurement of Zaraz has not been set since 27 October 2026. You can delete cookies that have already been set in your browser at any time.
Retention: On your device the cookie lifetimes apply (see above). At Google the data is kept as configured, at most 14 months; aggregated analyses without personal reference may last longer.
More information: Google privacy policy (policies.google.com/privacy) and «Safeguarding your data» for Google Analytics (support.google.com/analytics/answer/6004245).
Listing view counts
To count views of marketplace and housing listings, your browser stores a random identifier under «zg-listing-browser» in localStorage. It remains after you close the tab or browser until you delete it. This prevents repeat visits in the same browser from always counting as new visitors. It is not a cookie; the identifier is used only for this count on Zugora.
When you are signed in, we recognise repeat views through your account across devices. For each listing, we store different pseudonymous values instead of the original browser or account identifier. A mapping for that listing prevents the same browser from counting twice, first as a guest and then with its first signed-in account; other accounts in the same browser remain separate. We store neither IP addresses nor browser fingerprints for this count. Listing owners see aggregate numbers only and cannot see who viewed their listing. We recognise and skip your own views when you are signed in. Browsers and accounts are not a reliable count of distinct people: different browsers, cleared browser storage or multiple accounts can change the number.
The count respects the browser signals «Do Not Track» and «Global Privacy Control». Without available local storage, we do not count guest visits. You can delete the browser identifier through your browser’s website-data settings. Pseudonymous values and mappings remain until the listing is permanently deleted; deleting an account removes the values and mappings associated with that account. Aggregate counts contain no visitor identities.
Account
For sign-in we process the following details; what you publish on Zugora yourself (events, listings, housing ads, services, messages) is described in the sections after it. We store sign-in data separately from all other content, in a dedicated database (Cloudflare D1) located in the EU.
- Your email address, your chosen language and the time and version of your acceptance of the terms of use.
- A verifier of your password. We never store the password itself; the verifier cannot be reversed and is additionally protected with a secret key.
- For each passkey, the public key, a name, the provider identifier, times of use and a rough label of the device it was last used on. Biometric data such as your fingerprint or face never leave your device.
- For each session, a rough device label (e.g. "Safari · iPhone"), your IP address truncated to the network, and times. Session keys and security codes are kept only in a non-reversible, cryptographically protected form.
- Security events (such as sign-ins, changed passkeys, failed attempts) with a truncated IP address and a rough device label, and abuse counters in which addresses only appear as a non-reversible verifier.
Profile and required details
Optional details (about me, up to five links, a contact detail, occupation, languages, phone, address, nationality) are stored in private storage in the EU. You choose for each detail whether only you, approved followers or everyone allowed to view your profile can see it. The default is «only me» with respect to other members. You enter links and the contact detail (for example an email address or phone number) yourself; whatever you share with others can be seen by everyone who may view your profile, and Zugora does not check it. We never fill in your account email address for this automatically. Your username leads from your listings, housing listings and events to your profile card; with a private profile, only approved followers see more than your username there, namely your details shared with “Everyone” or “Approved followers” and your other content. Authorised admins can view stored profile details to manage accounts. A public profile link accessible without signing in requires separate consent; private profiles stay hidden there. Follow requests to private profiles require your approval. Blocking removes follow relationships. Optional details and follow relationships are removed when your account is deleted. Under «Personal details» you can download a JSON extract of your data (at most five times a day). It contains your account, profile and details, follow relationships, your listings with watchlist and saved searches, your housing listings with viewing slots, your applications for jobs and homes (for dossiers only times and document types; you can see their content and documents in your account), your rental profile (your own details, further household members only as a number), your purchase interests, services and appointment requests, events, your responses and invitations, your posts, comments and likes in the feed, your support requests with the team’s replies, invitations, your blocks, confirmations (such as being of age) and current restrictions of your account, your roles and requests at companies and places with the decision, your edits of places, connected apps, settings and your own messages; photos, videos and documents as links. Of other people it contains only what your data refers to: usernames of the accounts with which you have a follow relationship or a pending follow request or one you declined, or which you removed as followers, and of the accounts you blocked or muted, for invitations only public usernames; title, time and status of events and housing listings you responded to, applied to or registered interest in, or whose invitation you accepted, including the booked viewing and views of your dossier; for appointment requests the title of the offer and the details of the request (times, place and municipality, whether for a minor), even if the other side provided them; for conversations you are or were a member of (including message requests and group invitations), their type, what they are about (as an ID), status and creation, and the time of the last activity visible to you as in the app, even if the last message is from others; names of companies and places, and IDs of content your data refers to (such as posts you liked). It does not contain their content or other details, sign-in data or internal team notes; the file states what is missing and why. Contact us for a complete data access request.
For every account, Zugora requires a username and your first and last name when registering. You may optionally add, change or remove your date of birth in profile settings. Username and name remain required. We store them in your profile (Cloudflare D1 in the EU), separately from the sign-in data, together with your municipality (optional) and your choice of a public or private profile.
The username is publicly visible, for example on listings, events and in messages; a made-up name is fine. First and last name and date of birth are never public: they do not appear in public profiles, listings, events, link previews, the AI interface (MCP) or exports to third parties. Messages are an exception (not for the date of birth): people you share a direct or group conversation with see your first and last name there, with your username in small type next to it (details under «Messages»). The same exception applies to the feed and your profile card: these people also see your first and last name in the headers of your posts and comments and as the heading of your profile card; everyone else, and public pages (public feed, public profile), show only your username. If you explicitly confirm a contact invitation by email, however, that email contains your full profile name and verified email address; your date of birth is never shared this way. Outside these two cases only you and authorised Zugora administrators can see them: in the admin area the name appears in the user list, the date of birth with the age only for people with extended user rights.
Purpose: trust and safety of the community, checking the minimum age of 14, preventing abuse and contacting you if there is a problem. We use these details for no other purpose; apart from a contact invitation email you explicitly confirm, we do not pass them on to third parties, except to our processor (see «Processors») and where an authority requests them on a legal basis.
Retention: until you delete your account. When it is deleted, we remove username, first and last name, date of birth and municipality from your profile (see «Retention and deletion»).
Purpose
We process this data to provide your account, secure sign-in, prevent abuse and send you security notifications. On the forms for registration, password sign-in and "Forgot your password?", Cloudflare Turnstile checks that a human is using the form. What the required profile details are for is described in the section «Profile and required details».
Cookies in the account area
Under zugora.ch/app we additionally set technically necessary cookies: the session cookie (at most 90 days, invalid after 21 days without use; its content is renewed regularly while you use it), a cookie for intermediate steps of registration and password recovery (at most 30 minutes), a cookie for passkey sign-in (15 minutes) and, when you open an invitation, a cookie that carries the invitation through registration and sign-in (24 hours); the language cookie «zg_lang» (1 year, see «Public pages») applies here too. In the account area neither Cloudflare Zaraz nor Cloudflare Web Analytics runs: we set no advertising or tracking cookies here, measure no statistics and show no consent window. Your browser also sends cookies that Zaraz set on the public pages (such as your choice in «zaraz-consent») here; they are not evaluated here. What applies on the public pages with your consent is described in the section «Statistics with Google Analytics (consent only)».
Emails
We send confirmation codes and security notifications (such as a new passkey, a changed password or a deleted account) via Cloudflare Email Service from our support address. You cannot unsubscribe from these notifications while the account exists.
Profile picture
When you upload a profile picture, your browser crops it and saves it again as JPEG (512 and 128 pixels). This drops location data and other hidden image data; our server checks the picture once more. We store it in non-public storage (Cloudflare R2) within the EU.
Who sees the picture depends on your profile: if it is public, everyone sees it – on your profile card, in messages, with event replies and on your listings and housing listings, there even without signing in. If it is private, only you, our moderation team and the people you share a direct or group conversation with see it (in messages); everyone else sees your initials. We ask search engines not to index the picture.
If you replace or remove the picture or delete your account, we delete it immediately; copies already loaded may still be shown in browsers for up to 5 minutes. If a picture is reported, our moderation team reviews it; if they remove it, we keep a copy with the decision as evidence for 2 years. You can download your picture at any time under Account › Profile.
Messages
After verifying a new account, you receive one automatic welcome message from our administrator Jonas Hartmann. You can reply directly. Existing accounts do not receive a retrospective welcome message.
Messages between people on Zugora (about listings, homes, events or in groups) are encrypted in transit and stored encrypted with Cloudflare in the EU. They are not end-to-end encrypted. Within the application, our team has no access to conversations; moderators only see messages that someone reports, together with at most ten earlier messages that the reporting person could see. People with system access could technically access stored data; such access is ruled out organisationally.
Signed-in people who know your exact username can send you a message request, even if your profile is private. They only see your username, no other details; you decide whether it becomes a conversation. Under Messages › Settings you choose who may message you without a shared reason; with «Nobody» and a private profile, your username cannot be found this way.
In messages, people you share a direct or group conversation with (including about a listing, a home, an application or an event) see you with your first and last name and your profile picture, if you uploaded one; your username is shown in small type next to it, and the name leads to your profile card, which still shows only what your profile shares. This applies once you are active in the conversation: whoever sends you a message request sees only your username until you accept, and so does anyone invited to a group until they accept. Conversations about something specific need no acceptance: if someone contacts you about your listing, your home, an application or your event, you see each other with first and last name as soon as the conversation is opened. If you send someone a message request yourself, they see you with your first and last name. After a block, you see each other only with the username again; after you leave a group, its members see only your username again unless you share another conversation. In event chats, in company inboxes (without another shared conversation), in notification emails and in the list of people you have blocked, only the username appears. The same people also see your name above your posts and comments in the feed and as the heading of your profile card, but never on public pages.
In the conversation list we store a short preview of the last message (at most 120 characters). For new messages and message requests, after about one minute you get an email even if you have already read the message, without the message text by default (it names the sender or the title of the conversation); it summarises several new messages of a conversation, and at most one email per conversation every 5 minutes and at most 50 in 24 hours are sent. The email contains a one-click unsubscribe link (it carries a signed token with your account ID, never your email address). You can turn these emails off at any time under Messages › Settings, in your account settings or with this link. Messages are kept until you delete them or the conversation is deleted. If you delete your account, your messages in other people's conversations remain with the sender shown as "Deleted account".
Deleted messages and data may remain in backups for up to 35 days and are then removed permanently. Technical identifiers without content may be processed in Cloudflare logs outside the EU.
Messages to email addresses
If you send a message to an email address, that address receives your full profile name and your confirmed account email after your explicit consent. The email contains no message text. Only an account with verified ownership of the recipient address can accept the invitation and read the text in chat. Text not yet accepted is stored privately in the EU for at most 30 days; accepting, declining or account deletion removes it from invitation storage. The unsubscribe link stops further Zugora invitations to that address.
Notifications
Next to the profile menu, the bell shows what is new for you: for example likes and comments on your posts, new followers, replies to applications, interests, requests and viewings, notes from moderation, event and support updates, and new messages. For each notification we store its kind, a link to the place in Zugora, the time, whether you have read it, a few keywords at most (such as a title or a place) and the account identifiers of the people who triggered it; we fetch names and profile pictures only when it is displayed and only as they are visible to you. We merge similar notifications (such as several likes on the same post) into one.
Only you see the notifications and, where a shared company inbox is concerned, the authorised members of the company; they never contain message texts, reasons from reports or email addresses. Blocked or muted people trigger no notifications for you. The bell shows new messages and news updates from the existing data and stores nothing extra for them. The emails about messages, requests and support stay unchanged.
Retention: we delete read notifications after 90 days and all notifications after 180 days at the latest, and immediately when you delete your account. A notification disappears earlier if the trigger is withdrawn (for example a like) or the post is deleted. While the window is open, the bell asks for the number of new notifications every 60 seconds; the responses are private and are not cached.
Events
If you create an event, you publish, depending on the visibility you choose, its title, description, time, place, category, any cover image and your username as organiser: with «public» on a public page, in the event list, the calendar feed, the sitemap, on the map (only the centre of the municipality) and in structured data for search engines; with «members only» only for signed-in people; with «private» only for people with the invitation link. Cover images of public events are stored without metadata in public storage (Cloudflare R2, assets.zugora.ch), all others in non-public storage.
If you say you are going, answer «maybe» or are on the waitlist, you appear with your username in the guest list – depending on the event settings for the other guests or only for the organiser, never publicly. If the organiser approves RSVPs, at first only the organiser sees your request (username and guests); we tell you about the approval or refusal in the notification bell and by email, and you only see the names of the other guests once you are approved. When an event is cancelled, its time or place changes substantially or someone moves up from the waitlist, we send an email to those affected. Our moderation reviews reports; if it removes an event, we keep the reported content as evidence in non-public storage (reports and decisions for at most one year).
Cancelled events remain visible with the note «Cancelled» for 30 days; after that we delete the cover image. We delete events together with answers, invitations and cover image 12 months after they end, and the event chat 180 days after the end. If you delete your account, we cancel your upcoming events, remove your name and cover images and delete your answers.
Feed
In the feed you share pictures, short videos and stories (visible for 24 hours), you comment on and like other people's posts and you follow people. For this we store your text, your pictures and videos, the place you choose from our catalogue or as a municipality (never a location taken from image data), the time, your username and counters for likes, comments and shares. We also store the people you follow or mute and the posts you like. If you create a public event, it appears automatically as a post with a card in the feed. New and existing accounts follow the account of Jonas Hartmann (@jonas_hartmann), the founder of Zugora, once at the start, so that his posts show up in your feed under «Following». Under «Following and requests» in your account you can unfollow at any time; after that, your account never follows him automatically again. Only you can see who follows you, in your account; there is no public list of followers.
You choose who sees a post: everyone sees «Public» posts, also without signing in, on zugora.ch/en/feed/; we ask search engines not to include these pages. Only people whose follow request you accepted see «Followers only» posts. You post publicly only if you confirm that you are at least 18 years old; accounts under 18 post for followers only. Only signed-in people read and write comments. With a private profile, your posts show only your username, without a link to your profile.
Cleaning: your browser reduces pictures before uploading and saves them anew; location data and other hidden image data are dropped in the process, and our server checks the result. For videos, your browser neutralises location data in the file before uploading it, and our provider re-encodes them. Videos never play on their own: only when you tap a video does your browser load the provider player (Cloudflare Stream).
Storage: pictures are stored in Cloudflare Images, videos in Cloudflare Stream; we use both products as a processor (see the section «Processors»). We may later move older media to an archive with Cloudflare R2; they stay equally visible to you and others.
Retention: posts, comments and likes stay until you delete them, our moderation team deletes them or you delete your account. We delete stories after 24 hours together with their picture or video. We delete uploaded files that were never published after 24 hours. If you delete a post or your account, we remove the media at the providers immediately; for backups, the section «Retention and deletion» applies.
Companies: verified companies publish in the feed from their business area; the owner and managers act on behalf of the company. Only the company appears publicly, with its logo and name; we store which member created a post, and only the Zugora team and the members of the company can see it. If you follow a company, we store it like following a person: only you can see the list, only the number of followers is public, and the export of your data contains the companies you follow. If you delete your account, your follows end, and for company posts you created we remove the link to you; the posts belong to the company and stay until the company deletes them or the company is no longer managed on Zugora (then we delete them).
Viewed stories: so that stories you have viewed appear grey and move to the back, your browser keeps in its local storage (localStorage «zg-fd-seen») only the identifiers of the stories you have viewed, with their expiry time. This information does not leave your device and is not linked to any account; it disappears with the story after 24 hours at the latest and when you sign out. Story ring: whoever may see a story of yours (public story: everyone; “Followers only” story: your approved followers and you; never with a block in either direction and not for people who muted you) sees your profile picture wherever it is shown (feed, comments, messages, profile, listings, homes, events) with a coloured ring and can open your story from it. The server checks for every request whether a story is visible to a person; withheld stories never show a ring.
«First steps» on the overview: if you hide this list, only your browser remembers it in its local storage (localStorage «zg-dash-steps», content «off»); this information never leaves your device.
Reporting: anyone can report any post and any comment, also without signing in; then Cloudflare Turnstile checks the report (a check value and the IP address go to Cloudflare). A report creates a task for our team, which reviews the post; it does not hide the post. The only exception is reports about sexualised depictions of minors: they hide the post immediately until the team has decided; this exception is limited per person and day. If the team deletes a post, you receive an email with the reason. If we suspect depictions of abuse, we secure evidence and work with the authorities. We delete reports and decisions one year after the decision, and secured evidence after 2 years.
Places, invitations and location admins
For places with their own page on Zugora (e.g. sights, playgrounds, toy libraries) we store a contact address if the organisation or business publishes it itself, together with the source (the page on which it appears). We do not collect addresses of private individuals for this. Only our team sees contact addresses; they serve solely to invite the operators to maintain their place on Zugora themselves.
A place invitation is an email with a link and an invitation code (valid for 90 days). If several places share the same address, it receives a single email; the same address receives at most one invitation per place in 90 days. Every invitation names the sender, the purpose and why it was received and contains an unsubscribe link (also as one-click unsubscribe in email programs). After unsubscribing, the address is on our suppression list for place invitations and receives no further ones. We store link and code only as an irreversible check value; the address never appears in the history or in logs, and only as a check value for the suppression list and matching. Our team sends personal invitations only to people who expect them; without an email address it hands over link and code itself.
If you choose «Request admin rights», our team receives your username, the place, the time and whether the request came through an invitation. Whether the confirmed address of your account is exactly the invited one is checked automatically by Zugora, which shows the team only «yes» or «no». We inform you of the decision by email. Location admins maintain details and photos of their place and can create events at the place; public events at the place also appear on the place page and in the detail view of the map.
Time limits: we delete emails in the sending queue 30 days after sending, invitations together with redemptions 12 months after expiry or revocation, and requests 12 months after the decision. Contact addresses remain until we remove them or the organisation asks us to delete them; the suppression list remains so that an unsubscribed address no longer receives invitations.
Invitations from members
With your personal invitation code you can invite people you know. Zugora does not send any emails for this: you share the link yourself, and «By email» opens your own email app – Zugora never learns the address of the invited person. When someone signs up with your code, we store in the sign-in database who invited whom, with the time; to detect abuse, for 7 days we also store an irreversible short code of the network the sign-up came from. You see how many people accepted your invitation and the usernames of those with a public profile. If the inviting person has a public profile, the invitation page shows their username. When you open an invitation link, your browser remembers the code for this session. We delete the link between the two accounts as soon as one of the accounts is deleted; replaced codes after 90 days.
Invitation campaign: from time to time the Zugora team asks you in a direct message from the account jonas_hartmann to invite three people; the message contains your personal invitation code and appears in your messages. For every such message we send you exactly one separate email from Zugora to your account address: it contains the same text, your personal invitation code, your invitation link for sharing and a link to the page «Invite friends»; the usual notification email about the new message is not sent in this case. Anyone who received such a message before 1 November 2026 gets this email once afterwards. Like the other notification emails about your account, we send it via Cloudflare Email Service to run and promote the service. Every such email contains a one-click unsubscribe link (it carries a signed token with your account identifier, never your email address); under Account › Settings you can turn these emails off and on again at any time. You still receive the direct message. The code then sits in your chat and in the email and is visible to the sender account; «Create new code» makes it invalid. For the campaign we store per person only whether and when the message and the email were sent, whether you unsubscribed from the emails and in which conversation, never the code; the mail delivery keeps the text of the email (with your username, without the code) only until it is sent and clears it afterwards. Anyone who signs up receives the same message once, automatically, 7 days after email address and profile are confirmed; for this we also store when the profile became complete. We write to you this way at most once in 30 days and not shortly after the welcome message. With a pause or a quota of 0 you do not receive such a message or such an email. To evaluate it we count how many sign-ups with your code were started and accepted after the message, without naming the people. We delete this information and your email setting together with your account.
Listings and housing
Listings and housing ads are public, even without signing in: title, description, price, place (for housing the exact address only for invited applicants), photos and your username with a note since when you have been a member. We scale photos down in the browser and remove metadata such as the location before they are stored in public storage (Cloudflare R2, assets.zugora.ch). Contact and applications run through messages and are visible only to those involved.
Time limits: listings expire after 30 days, housing ads after 60 days (renewable); afterwards they show a notice for 30 days and are deleted – listings after 90 days, listings you delete yourself after 14 days, housing ads 30 days after the notice period ends, together with their photos (those you delete yourself after 30 days); we clear application messages for housing 30 days after the end. Content removed by moderation is kept in non-public storage for two years (objections, repeated violations).
Interest in properties for sale: if you show interest in a property for sale, we store your first and last name, your email address, optionally your phone number and a short message, and pass them on to the person who placed the ad, or to the managing members in the case of a company. You expressly agree to this in the form. The lister sees the details online under «Interested parties» and receives an email with your name, but without contact details or message. We delete the details 30 days after the listing ends, immediately when you withdraw your interest and together with your account.
External housing listings from Flatfox
On the «Housing» page, Zugora also shows listings from Flatfox (SMG Swiss Marketplace Group) in the canton of Zug; SMG has permitted this. Twice a day we fetch the public Flatfox interface and store facts about the listing (type, rooms, area, price, place, move-in), a short text of at most 300 characters, the link to the original and the name of the advertising company. We take over neither contact details nor persons; we shorten texts that contain an email address, phone number or link. Listings that Flatfox no longer delivers are deleted after two fetches; what has not been seen for three days is no longer shown.
Your browser loads the cover image on the «Housing» page directly from flatfox.ch. Flatfox thereby receives your IP address and the usual details of your browser, but no information about which page you come from. Zugora does not copy images. With «View on Flatfox» you leave Zugora; Flatfox is responsible for the listing, the contact and the application, and its privacy policy applies.
Companies and job applications
For company profiles, we process information about the organisation, its members and contact people. Published company profiles and job advertisements are public. Content belonging to an organisation shows its company name and the contact person’s username according to the content’s visibility. Current authorised members can view and manage shared content and the company inbox; removing their membership removes this access. For invitations to company management, we process the entered email address to identify and invite the recipient. The organisation’s content remains when you delete your personal account; your membership and designation as a contact person are removed.
When you apply for a job directly on Zugora, we store your name, email address, optional phone number and personal message, application status and uploaded documents: CV, cover letter and certificates as PDFs of up to 8 MB per file. Documents are held in non-public storage. A draft is visible only to you. Only after you confirm submission do the company’s current managers gain access to the application and documents; managers who join later can also view them. Your personal application message is also copied into the company chat when you submit. Company managers can open a reply draft in their own email program.
On Zugora, application drafts are retained for 30 days from creation and submitted applications for 180 days from submission; we then delete the application and its files. You can withdraw and delete your application earlier. This removes the application and files, but not messages already sent in the company chat. Those messages are covered by the section «Messages».
Jobs from external sources (Adzuna, company applicant tracking systems)
On the «Jobs» page, the list «Open jobs in the canton of Zug» shows, besides the jobs on Zugora, job ads from Adzuna (Adzuna Switzerland) with a work location in the canton of Zug. Twice a day we fetch the Adzuna interface and store title, employer, place, workload, date and the link that Adzuna delivers to us. We take over neither the description nor contact persons or salary details. Ads that Adzuna no longer delivers are deleted after two fetches; what has not been seen for three days is no longer shown and is deleted after a week. If we switch the source off, we delete all Adzuna data.
Before you click, Adzuna receives nothing from Zugora: the label «Adzuna» is a text link, and we load no image and no script from Adzuna. By clicking a job or «Adzuna» you leave Zugora; Adzuna is responsible for the ad, the application and the data there, and its privacy policy applies.
Companies with a Zugora profile can have their jobs taken over automatically from their own applicant tracking system (Personio, Greenhouse, Lever, Recruitee, SmartRecruiters). Only the company’s owner sets this up and expressly consents in doing so; Zugora approves it by hand. We only read the company’s public job list, without credentials, and store title, place, workload, date and the link to the original job, never the description and never contact persons. As proof we store the time, the version of the consent text and the account of the consenting person; if you delete your account, the person in the proof is made unrecognisable. The consent can be revoked at any time; we then delete all taken-over jobs of the company immediately.
Services and appointment requests (since 18 Oct 2026)
On the «Services» page, people aged 18 or over and companies with a profile can list offers, for example tutoring, trades and everyday help. Public, even without signing in, are the title, description, category, price, the municipality of the offer (never an address), the municipalities served, the rough availability (weekdays and parts of the day), spoken languages and levels, and the username with «member since»; the profile picture and a link to the profile only if your profile is public. For companies, the company name, logo and profile are shown there. We neither store nor show age, date of birth, ID documents, certificates, criminal-record extracts or ratings; services have no photos. Published offers appear on the public pages, in the sitemap and in the interfaces for search engines and AI assistants (public offer data only).
If you request an appointment through an offer, we store the proposed times (up to three per round, at most six rounds), the kind of place (at the customer’s, at the provider’s or online) and, for appointments at the customer’s, the municipality, the flag whether the appointment is for a minor (the flag only, no details about the child), the status (requested, confirmed, declined, withdrawn, cancelled or expired), a reason chosen from a list (for example «no time»), who answered last, and the reference to the conversation. The free-text message of the request stays in the chat only, not in this table. Each step appears as an ordinary message from you in the Zugora chat with a link to the appointment page; the details in the section «Messages» apply to it. We create the calendar file (.ics) only when you download it; it contains the title of the offer, the time and the place in words (online or municipality), but no names, no address and no message text, and it is not stored.
Recipients: only the two sides see the details of an appointment request; for offers by a company, the current authorised members of the company who also see the company inbox. In moderation our team sees offers and reports, but no appointment requests. We store the confirmation «at least 18 years old» as a confirmation, not as a date of birth; a date of birth under 18 in your profile prevents offering, requesting and contacting (parents request appointments for their children). We process this data to arrange offers and appointments (use of the service) and to prevent misuse.
Time limits: offers you delete yourself are deleted after 14 days, expired offers 90 days after expiry (until then you can renew them), drafts that were never published 90 days after the last change. Expired offers still under review by moderation are kept until the decision; offers removed by moderation are kept non-publicly for two years, even if you delete them (appeals, repeated violations). We delete appointment requests 90 days after they close (declined, withdrawn, cancelled, expired), confirmed appointments 180 days after they end and requests that were never answered at the latest 180 days after the last proposed start; the link between person, offer and conversation after 365 days. If you delete your account, we delete your offers, requests and links. Your data export contains your offers and requests (without details about the other side). Chat messages follow the section «Messages».
Directory of Zug businesses
Zugora keeps a directory of businesses and shops in the canton of Zug (for example letting companies, property managers and smaller shops). For profiles that a business has not yet taken over, our team compiles only details that the organisation publishes itself: company name, address, website, phone, opening hours and a short description, with the source and the date of the check. Such profiles are marked «not maintained by the business». This concerns businesses, not private individuals. A business can ask at any time for its profile to be corrected or removed.
To invite a business, we store at most one publicly listed function address of the business (for example info@) together with the source on which it appears. We do not collect addresses of private individuals for this. Only our team sees the address, it never appears on the page and serves solely to invite the business to take over its profile itself.
Such an invitation is a single email with a takeover link (valid for 60 days, can be used once only). Every invitation names the sender, the purpose and why it was received and contains an unsubscribe link (also as one-click unsubscribe in email programs). The same business and the same address receive at most one invitation in 90 days; we send only a few invitations per working day. After unsubscribing, the address is on our suppression list for invitations and receives no further ones. We store the link only as an irreversible check value; the address never appears in the history or in logs, and only as a check value for the suppression list and matching.
Whoever wants to take over a profile needs a Zugora account with a confirmed email address and files a request, through the link in the invitation or the button «Request to take over this profile» on the profile. So that not just anyone can take over a company that is not theirs, our team confirms every takeover after a short check; until then the profile stays unchanged. Every request creates a support ticket. It shows our team your username, your name from your profile, your optional details (role, phone, message) and «yes» or «no» for four points: link valid, address of your account equals the address written to, domain of your confirmed address matches the company website, freemail address. It also shows the domain of your address, never the address itself and never the link. When the takeover is confirmed, the stored contact address is deleted. Our team can undo a takeover within 30 days, for example in case of a mistake or misuse.
If you create a company profile yourself, it is public immediately but marked «not verified» until it has been checked. This also creates a support ticket with the same details; if the name or website change later, our team checks again. When you delete your account, we delete your requests together with the related support tickets.
Time limits: we delete invitations 30 days after they end (expired, revoked or taken over). Contact addresses remain until the profile is taken over, we remove them or the business asks us to delete them; the suppression list remains so that an unsubscribed address no longer receives invitations.
Contact by email
When you write to us (to the address in the legal notice or in reply to one of our emails), we process your email address, the content and any attachments to answer your request. We store a complete copy of every incoming email in non-public storage (Cloudflare R2) located in the EU and delete it there after 180 days. We handle support requests as private tickets. Authorised support staff and admins see the thread; complete raw emails and attachments require a specific admin permission and renewed passkey confirmation. Closed tickets are deleted after 730 days. Sender signature checks retrieve public DKIM keys via cloudflare-dns.com. We also forward the email to the operator’s mailbox, where it remains as long as needed to handle the request.
Retention and deletion
- Unconfirmed registrations are deleted after 24 hours.
- Codes are valid for 15 minutes and deleted after 24 hours.
- Ended and expired sessions are deleted after 7 days.
- Abuse counters are deleted after 24 hours; if a lock is active (at most 24 hours), only once it has ended. Security events are deleted after 180 days.
- You can delete your account yourself at any time under Account › Delete account. Your account, password verifier, passkeys and sessions are then deleted immediately, and in your profile the username, first and last name, date of birth and municipality are cleared; you receive a confirmation by email.
- Posts, comments and likes in the feed stay until you delete them or your account; stories and uploads that were never published are deleted after 24 hours. Feed reports are deleted one year after the decision.
- Your profile picture is deleted immediately when you replace or remove it or delete your account. If our moderation team removes a picture, we keep a copy as evidence for 2 years; reports and decisions are kept for 2 years as well.
- Bell notifications: read ones after 90 days, all after 180 days, immediately when you delete your account.
- Statistics (consent only): identifier in the browser 1 year, session identifier 30 minutes; at Google as configured, at most 14 months.
- For technical reasons, deleted data may remain in backups for up to 35 days before it is permanently deleted or overwritten.
Processors
We use Cloudflare, Inc. (USA) as a processor: for running and delivering the website, the databases, the storage for incoming emails, email delivery, Turnstile, Web Analytics (reach measurement without cookies), Zaraz (consent window and loading of Google Analytics) and the AI search (Cloudflare AI Search). The sign-in database and the email storage are located in the EU; Cloudflare may also process data in other countries to operate its network.
Cloudflare, Inc. is certified under the Swiss-U.S. Data Privacy Framework; for certified companies, the USA is considered a country with adequate data protection (Annex 1 of the Swiss Data Protection Ordinance). Processing in other countries is covered by the standard contractual clauses of the data processing agreement with Cloudflare.
For the feed we also use Cloudflare Images (pictures) and Cloudflare Stream (videos), likewise as a processor of Cloudflare (see the section «Feed»).
Forwarded emails are also stored with the provider of the operator's mailbox. We do not share personal data for advertising.
Your rights
You can request access to your data and its correction or deletion. Please contact us (details in the legal notice). You can also lodge a complaint with the Federal Data Protection and Information Commissioner (FDPIC).