Legal
USULINN Privacy Policy
1. Who is responsible
1.1 The controller of your personal data is René Heigl, trading as EdotCorp.com, a sole proprietorship not entered in the commercial register (no UID number yet), Bärengasse 1, 8750 Glarus, Switzerland ("USULINN", "we", "us").
1.2 For anything about your data, write to [email protected] or to our postal address.
1.3 to be confirmed (Q44)
2. The short version
- We collect what we need to run a trusted room exchange, and not more.
- Your exact address is encrypted. Only a guest whose stay you confirmed receives it, shortly before arrival. It never appears on public pages, in search engines, in logs or in AI requests.
- We do not keep copies of your identity document, your selfie, your document number, your date of birth or your phone number. Our identity provider holds the check; we keep only the outcome and a one-way key that stops a second welcome Night.
- We never see your card details.
- We do not sell data, show ads or use tracking cookies. We count visits to our pages with Cloudflare Web Analytics, which sets no cookies and builds no profile of you.
- People at USULINN do not read your messages in the normal course. An automatic rule list looks for scams and abuse; only a message it flags, or one you report, may be read by a person.
- We use a small number of service providers. Section 6 names every one, what it receives and where.
3. What this policy covers
3.1 This policy covers usulinn.com, its pages under /de, the USULINN app (installed or in the browser) and the emails we send.
3.2 It does not cover the websites of other companies you reach from USULINN, such as Stripe's payment and identity pages or Booking.com. Their own privacy notices apply there.
4. What we process, feature by feature
For each feature: what data, where it comes from, and why.
4.1 Visiting public pages
- Data: the technical data of each request (IP address, browser, requested page, time). Our edge provider, Cloudflare, sees all public traffic (section 6). Our own server uses the IP address only to apply rate limits, stored as a one-way hash for at most about two days, and does not write it to its logs.
- Why: to deliver the pages, keep the service secure and stop abuse.
- If you follow a language link, we set a cookie that remembers your language (section 8).
4.2 Account and sign-in
- Data: your email address and whether it is confirmed; your account status; a sign-up source tag if you arrived through a link with one (for example
founder_story), which tells us which channel brought you, not who you are elsewhere; for each sign-in session a hashed token, the sign-in method, a coarse device hint such as "Chrome on Windows" (never the raw browser string or your IP address), and the times it was created and last used; for passkeys, the public key and technical details of the credential. Your fingerprint, face or device PIN never leave your device and never reach us. - Source: you, and your browser.
- Why: to create your account, sign you in safely, show you your devices and let you sign them out, and protect accounts against misuse.
- Sign-in links are sent by email, are single use, valid for 15 minutes and stored only as a hash.
4.3 Identity check
- Data at the provider: the identity check runs on the pages of Stripe Identity. Stripe collects images of your passport or identity card, a selfie and the data on the document (such as type, issuing country, number, name and date of birth), and compares the selfie with the document.
- Data at USULINN: the reference of the check, its outcome, and a one-way key. Our server reads the document's issuing country, type, number and your date of birth from Stripe once: the date of birth to check that you are at least 18 (a document showing a younger age fails the check and leaves no key), and all four fields to make the key. To make the key, it combines them with a secret value that is stored in no database and no backup, and keeps only the resulting 64-character code. The number, the date of birth, your name, the images and the selfie are not stored by USULINN, not logged and not sent anywhere else.
- Why: to make sure every member is a real, verified person, and to give the welcome Night only once per person, even if someone closes an account and opens a new one.
- Retention at Stripe: 90 days after the check, the shortest period that still allows an appeal. to be confirmed (Q18)
- to be confirmed (Q45)
4.4 Phone check
- Data: your mobile number and a one-time code sent by SMS through Twilio Verify. Only numbers from Switzerland, Liechtenstein, Germany, Austria, France and Italy are accepted.
- At USULINN: we pass the number to Twilio and keep only the outcome (verified or not). We do not store your phone number.
- Why: an extra signal that a real, reachable person is behind an account, and protection against abuse.
4.5 Membership payment
- Data we send to Stripe: your email address (so that Stripe can send your receipts and keep the customer record) and your USULINN account id. Nothing else.
- Data Stripe collects on its own pages: your payment details and anything else Stripe's checkout asks for. We never see your card details.
- Data we keep: the Stripe customer and subscription references, the membership status, the renewal date, whether you cancelled, and checkout records. Stripe's notifications to us (webhooks) are checked and applied but their contents are never stored; we keep only a short record of each event (its id, type, time and outcome) for 400 days.
- Why: to sell and renew the CHF 59 yearly membership, send renewal reminders, handle failed payments and keep accurate payment records.
4.6 Your profile
- Data: first name, age range (for example 25–34), home region and country, languages and a short introduction, if you fill them in. We do not ask for your date of birth in the profile.
- Why: so a host can decide about a request. Section 5 says who sees what.
4.7 Rooms, exact addresses and photos
- Room data: room type, city, neighbourhood, country, time zone, capacity, beds, bathroom, entrance and kitchen arrangements, amenities, accessibility notes, house rules, stay settings, availability dates and your confirmations of the minimum standards.
- Exact address: street, number, postal code, city, country and optional access notes. It is encrypted (AES-256-GCM) with a key held by the founder and bound to your property. The host always sees their own address. A guest receives it only for a confirmed stay, 48 hours before the 15:00 check-in on the arrival day, or earlier if the host chooses. Everyone else, including the guest's companions and the public, never receives it. It is never in a public page, a search-engine document, a log, a notification, an email or an AI request. To stop a street name being repeated in a public room name, we also keep a keyed one-way code of the street.
- Photos: every upload is re-encoded and its hidden metadata (including location data) is removed before it is stored. Photos are stored privately on our own storage and shown only through links that expire after a few minutes.
- Why: to show rooms to the right people, keep homes private until a stay is confirmed, and keep personal details out of photos.
4.8 Requests and stays
- Data: the room and dates you ask for, the number of adults and children, the accounts of verified adult companions, pets, your acceptance of the house rules, your short introduction, the host's decision, request and booking states and times, arrival and departure confirmations, the number of nights that took place, early-ending reasons, cancellations, no-shows and reports that a stay failed.
- Why: to run the request, the stay and the settlement of Nights, to resolve disagreements and to protect members.
4.9 Nights
- Data: an unchangeable record of every Night entry for your account: the welcome Night, reservations, releases, pending and released host earnings, and corrections. Entries are never edited or deleted; a correction is a new entry.
- Why: to keep an exact, fair and checkable record of hosting and requests.
4.10 Messages and moderation
- Data: the messages between a guest and a host, linked to their request, with times; whether a message was flagged, hidden or reported.
- Automatic screening: each message is checked against a fixed rule list (no AI model, no outside service) for signs of payment demands, scams, requests to pay or book elsewhere, threats and abuse. Contact details and links are refused before a request is accepted. A match is recorded and creates a review task.
- Who reads messages: nobody at USULINN reads messages in the normal course. A person may read a message that was flagged or that a member reported, and every such reading is recorded.
- Why: to let members arrange stays, and to protect them from scams, payment demands and abuse.
4.11 Reviews, trust figures and badges
- Data: your structured review answers and those about you; trust figures derived from them and from your stay history (for example response rate, typical response time, completion reliability, experience bands, would-host-again and would-stay-again percentages); internal reliability events (late cancellations, no-shows, unanswered requests, failed stays); badges and their state.
- Why: to help members decide whom to host and where to stay, and to recognise reliable members.
- Public figures appear only once five different members stand behind them and are rounded (section 5).
4.12 Notifications and email
- Data: your in-app notifications (a template name and a few details such as room name, city, dates and counts); your settings (quiet hours, your time zone, urgent alerts, message emails, demand-alert level); whether an email bounced or was marked as spam.
- What emails never contain: your exact address, a message's text, a phone number, a legal name or someone else's email address. Our emails contain no tracking pixels, remote images or click tracking.
- Why: to tell you about requests, stays, messages, your membership and safety notices, without unwanted noise.
- If your address bounces hard or you mark our email as spam, we stop sending you notification emails. Sign-in links are still sent.
4.13 Room Wanted and demand alerts
- Data: for a Room Wanted alert, the destination, dates or date window, party and filters you choose.
- What hosts see: only that "several members are looking" in a city and week, from at least three members, shown as a range (3 to 4, 5 to 9, 10 or more). Never a name, an account, an exact count or anyone's exact dates. The stored summary has no account column.
- Why: to tell you when a matching room opens, and to tell hosts where rooms are needed.
4.14 Emergency Rehousing
- Data: the case (city, dates, party size), the hosts alerted, their offers and your choice.
- What alerted hosts see: the city, dates and party size only, never who the guest is.
- Why: to find a replacement room quickly when a host cancels late or a stay fails.
4.15 Integrity checks
- Data: signals about patterns of stays (for example two members repeatedly hosting only each other, travel that is not physically plausible, very fast accumulation of Nights), cases, holds on pending Nights and decisions. These records hold account and booking ids, counts and category names only: no name, email, address or free text.
- Why: to detect invented stays and protect the fairness of Nights. Section 9 explains how decisions are made.
- Members never see signals or cases. When a hold is placed, the member receives a neutral safety notice.
4.16 Reports and blocks
- Data: the report category, your note, the message you cite, and who blocked whom.
- Why: to handle safety concerns and stop unwanted contact.
4.17 Founder decisions and the audit log
- Data: review tasks ("decision cards") with ids and structured facts, the decision (yes or no), who decided and why, and an append-only audit log of every decision and every time a person viewed details such as a flagged message.
- Who: only the founder, through a private admin connection that is not reachable from the internet. Admin lists show masked email addresses (such as
a***@example.com), never names, exact addresses, identity data, phone numbers or internal scores. - Why: to make human decisions accountable and traceable.
4.18 Security and logs
- Data: technical logs of our servers. Before a log line is written, personal and secret data (such as email addresses, phone numbers, addresses, names, tokens, links, IP addresses) are removed. Logs are rotated by size.
- Rate limits: counters keyed by a one-way hash of the account, email address or IP address, deleted after about two days.
- Why: to keep USULINN running and secure, and to find and fix faults.
4.19 Backups
- Data: a nightly encrypted copy of the database and the stored photos. The exact-address key and the identity-key secret are kept separately and are in no backup.
- Where: encrypted copies are kept on our main server for 7 days and on a second server of ours for 30 days, both in Switzerland. An encrypted copy is also kept on an offline disk in Switzerland. Only the founder holds the decryption key.
- Important: when we delete your data from the live system, it remains in these encrypted backups until they expire, at most 30 days later. We do not restore deleted data except to recover from a failure.
5. Who sees what inside USULINN
| Viewer | Sees |
|---|---|
| Anyone, including search engines | Room type, city (and a neighbourhood only where several hosts share it), capacity, basic facts and amenities, availability, public photos, and "Hosted by a verified member". No host name, profile, reviews, exact address, contact details or trust data. |
| Verified, paying member | Additionally the full photo gallery, description, complete house rules and the host's rounded trust summary and displayed badges. |
| Host, for a request to their room | The requester's first name (or "A verified member"), verified status, and a short trust summary: travel experience band, would-host-again percentage, member-since year and displayed badges; the party and the introduction. Your other profile details are not shown to the host. Never your legal name, identity data, home address, phone or email. |
| Guest of a confirmed stay | The exact address and check-in details, from 48 hours before the 15:00 check-in or earlier if the host chooses. |
| The founder | As described in 4.17, through the private admin connection. |
Trust figures are rounded to 5 percent and capped at 95 percent until twenty members stand behind them. Exact internal scores are never shown to anyone.
6. Service providers and other recipients
We share data only with the providers below, only what each needs, and under a contract. to be confirmed (Q46)
| Recipient | What it receives | Where | Safeguard |
|---|---|---|---|
| Stripe (membership payments) | Your email address and account id; your payment data entered on Stripe's pages; subscription and invoice data. | Stripe Payments Europe; transfers to the United States possible. | Swiss-US Data Privacy Framework where applicable to be confirmed (Q46) |
| Stripe Identity (identity check) | Document images, selfie and document data (type, issuing country, number, name, date of birth); your account id. | to be confirmed (Q23) | to be confirmed (Q46) |
| Twilio (phone check) | Your mobile number and the SMS with the one-time code. | United States | to be confirmed (Q46) |
| Postmark (email delivery) | Your email address and the content of our emails, including sign-in links and notification text. Bounce and spam reports come back to us. | to be confirmed (Q24) | to be confirmed (Q46) |
| Cloudflare (network, security, DNS) | All public website traffic, in readable form at Cloudflare's edge: requests, responses, cookies and IP addresses of visitors. The private admin connection never passes through Cloudflare. Cloudflare Web Analytics: a small script on our pages reports each page view (page address, referring site, browser and device type, country, load times) to Cloudflare without cookies or local storage; we see only totals, never individual visitors. | Cloudflare's global network | to be confirmed (Q46) |
| Booking.com (commercial hotel link) (only if switched on) | Nothing from us. If you click the link, your browser opens Booking.com with the city, dates and party size of the search. The link carries no account, booking or room id, and our pages send no referrer. Booking.com may set its own cookies. If you book, Booking.com may pay us a commission. | Booking.com's own processing | Booking.com is responsible for what happens on its site. |
| Search engines through IndexNow (production only) | Only the web addresses of public pages that changed or were removed. Never a query string, member data or anything private. | IndexNow (api.indexnow.org) and the search engines that take part in it | Public URLs only; no personal data |
| Other members | What section 5 describes. | — | — |
| Authorities | Only where the law requires it. to be confirmed (Q47) | — | — |
Our own servers, including the database and photo storage, run on hardware operated by the founder in Switzerland.
We do not sell personal data, we do not share it for advertising, and we use no analytics or advertising service.
7. Disclosure abroad
Some providers in section 6 process data outside Switzerland, including in the United States. We disclose data abroad only where the destination has adequate protection, the recipient is certified under the Swiss-US Data Privacy Framework, or standard contractual clauses or another safeguard recognised by the revDSG are in place. to be confirmed (Q46) You can ask us for a copy of the safeguard used.
8. Cookies and storage on your device
We use only what USULINN needs to work. No tracking, analytics or advertising cookies. Visits are counted with Cloudflare Web Analytics, which stores nothing on your device (section 6).
| Name | Type | What it does | Lifetime |
|---|---|---|---|
__Host-usulinn-session | Cookie, strictly necessary | Keeps you signed in. Holds a random token; we store only its hash. HttpOnly, Secure, SameSite=Strict. | Up to 30 days; the sign-in ends earlier after 14 days without use, and at once when you sign out |
usulinn-csrf | Cookie, strictly necessary | Protects your account against forged requests from other sites. Readable by our own page scripts. Secure, SameSite=Strict. | Same as the session cookie |
usulinn_locale | Cookie, functional | Remembers your language when you choose one with a language link. HttpOnly, SameSite=Lax, Secure. Not used for tracking. | 365 days |
usulinn_src | Cookie, functional | Remembers which link brought you here, for seven days, so a sign-up can be counted to its channel. Holds only a short channel name from the link you opened, never anything about you. Set only when a link carries one; removed when you ask for a sign-in link. HttpOnly, SameSite=Lax, Secure. Not used for tracking. | 7 days |
usulinn.identity.session | Session storage (browser tab) | Remembers which identity check you started, so the page can show the result when you come back from Stripe. | Until you close the tab, or the check fails |
usulinn-shell-1 | Service-worker cache | Keeps the offline page, the logo, an icon and the site's static files so a public page can show a branded offline message. It never stores a member page, an API answer or anything about you. | Until the app is updated or you clear site data |
Cookies of other services: Stripe sets its own cookies on its payment and identity pages, and Booking.com on its site. to be confirmed (Q27)
to be confirmed (Q48)
9. Automated processing and decisions
We tell you where machines make or prepare decisions about you.
- Search order. Rooms are ordered automatically by date match, fit for your party, place, listing accuracy, host responsiveness, fresh availability and a small daily rotation. A host's Night balance, membership, badges, the room's market value and payment never influence the order. There is no paid placement.
- Duplicate check. When a verified identity matches one already used, the system automatically refuses a second live account for the same person and never gives a second welcome Night.
- Membership status. A failed renewal payment pauses the membership automatically until it is paid.
- Requests. Unanswered requests expire automatically, and accepting one request automatically closes conflicting ones.
- Message screening. Messages are checked automatically against a rule list. A match never blocks delivery; it creates a review task for a person, and may show the recipient a warning.
- Integrity checks. Patterns of stays are scored automatically. Depending on the score, a case is only monitored, or sent to the founder for review. At the highest level the system also places a temporary hold on the host's still-pending Nights from that stay, until the founder decides. Nights are taken back only if the founder confirms it. No automatic process closes, bans or restricts an account.
- Trust figures and badges are calculated automatically from reviews and stays. Awards are decided by the founder.
You may ask us to explain a decision that affects you, give your point of view, and have it reviewed by a person. to be confirmed (Q49)
10. How we protect your data
- Exact addresses are encrypted with a key held by the founder; the identity-key secret is held outside the database and the backups.
- Sign-in uses passkeys or single-use, short-lived links. Session and link tokens are stored only as hashes.
- Forged requests from other sites are blocked; rate limits slow down attacks.
- Photos are private and shown only through expiring links. Their metadata is removed.
- Logs are cleaned of personal data before they are written.
- The admin console is reachable only over a private, encrypted connection and requires a passkey with a PIN or biometric check. Every view of sensitive details is logged.
- Backups are encrypted before they are written. The second server fetches them itself, so the main server holds no access that could delete them.
- If a data breach is likely to put you at high risk, we inform the FDPIC and, where needed for your protection, you, as the law requires.
11. How long we keep data
| Data | How long |
|---|---|
| Sign-in links | Until used or expired (15 minutes), then deleted |
| Passkey sign-in challenges | 5 minutes, then deleted |
| Sessions | Deleted 30 days after they end |
| Rate-limit counters | About 2 days |
| Short records of payment-provider events | 400 days |
| Identity check data at Stripe | 90 days after the check |
| Identity check outcome and one-way key at USULINN | For as long as USULINN operates (the key must outlive the account so that a welcome Night is never given twice) |
| Demand summaries for hosts | 30 days |
| Room Wanted alerts | Deleted 90 days after they end |
| Technical job records | 7 days (successful), 90 days (failed) |
| Night records | For as long as USULINN operates (never edited, so that every Night can be accounted for) |
| Integrity records | 10 years (kept for fraud prevention; after a closure they remain linked only to an anonymised account) |
| Account and profile | Until the account is closed, then anonymised at once |
| Rooms and photos | Until you delete the room or close the account |
| Requests, stays and messages | 5 years after the stay or the request ended to be confirmed (Q50) |
| Reviews | For as long as USULINN operates; anonymised when an account closes |
| Notifications | 90 days |
| Payment and accounting records | to be confirmed (Q50) |
| Founder decisions and audit log | 10 years (append-only) |
| Server logs | Rotated by size (a few megabytes per service), no fixed time |
| Encrypted backups | 7 days on our main server, 30 days on our second server; the offline copy is replaced about monthly |
When you close your account (Settings, "Close your account"), or we close it, we delete or anonymise your account data at once: your email address, name, profile, photos, exact addresses and notifications. We keep, linked only to an anonymised account, what we must keep by law or to prevent fraud: the one-way identity key (so that a welcome Night is never given twice), Night records, reviews and messages (shown as from a former member), integrity records and our audit log. How long each is kept is shown in the table above.
12. Your rights
12.1 Under the revDSG you have the right to:
- ask whether we process data about you and receive a copy (right of access);
- receive data you gave us in a common electronic format (data portability), where the law provides it;
- have incorrect data corrected;
- have data deleted, or its processing stopped, unless we must keep it;
- object to processing;
- ask about an automated decision and have it reviewed by a person (section 9).
to be confirmed (Q44)
12.2 How to exercise them. Write to [email protected]. We may ask you to confirm your identity, for example by writing from the email address of your account. We answer within 30 days, free of charge in normal cases. You can already see and change much of your data yourself in your account (profile, rooms, settings, signed-in devices).
12.3 Complaints. You can complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC / EDÖB), Feldeggweg 1, 3003 Bern, www.edoeb.admin.ch. to be confirmed (Q51)
13. Children
USULINN is for adults. Members must be 18 or older; the identity check confirms it. Children may travel with a verified member, under that member's responsibility; we record only the number of children in a party, not their names or ages. Room photos must not show children.
14. Changes to this policy
We update this policy when our processing changes, for example when we add a provider or switch a feature on. The version and date are at the top. We tell members about important changes by email and in the app before they apply.
15. Contact
René Heigl, trading as EdotCorp.com, a sole proprietorship not entered in the commercial register (no UID number yet), Bärengasse 1, 8750 Glarus, Switzerland Email: [email protected] We have not appointed a data protection advisor; the contact above answers every privacy request.