OneFamily.unoOneFamily.uno

Privacy Policy

Last updated: 16 October 2026

1. Privacy at a Glance

General Information

The following notes provide a simple overview of what happens to your personal data when you visit this website. Personal data is any data that can personally identify you.

Data Collection on this Website

Who is responsible for data collection on this website?

Data processing on this website is carried out by the website operator. Their contact details can be found in the imprint of this website.

How do we collect your data?

Your data is collected in part by you providing it to us. This may include data that you enter into a contact form, for example. Other data is collected automatically or with your consent when you visit the website through our IT systems.

2. Hosting

This website is hosted by Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany. Server location: Germany (EU).

The hosting provider collects the following data in log files:
- IP address
- Date and time of request
- Time zone difference to Greenwich Mean Time (GMT)
- Content of the request (specific page)
- Access status/HTTP status code
- Amount of data transferred
- Website from which the request originates
- Browser and browser version
- Operating system and its interface

3. General Information and Mandatory Disclosures

Data Protection

The operators of this website take the protection of your personal data very seriously. We treat your personal data confidentially and in accordance with statutory data protection regulations and this privacy policy.

Name and Address of the Controller

OneFamily.uno
Sole proprietorship
Florin Tudose
Am Hochgericht 1
96050 Bamberg
Germany
VAT ID: DE298621889
E-Mail:

Data Protection Officer

Florin Tudose
E-Mail:

4. Data Collection on this Website

Contact Form

If you send us inquiries via the contact form, your details from the inquiry form, including the contact data you provide there, will be stored by us for the purpose of processing the inquiry and in case of follow-up questions.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest)
Retention period: Until your inquiry is fully processed, then 30 days
Recipients: Web3Forms (GDPR-compliant form processing service)

Newsletter

If you would like to subscribe to the newsletter offered on the website, we require your email address as well as information that allows us to verify that you are the owner of the specified email address and agree to receive the newsletter.

Legal basis: Art. 6(1)(a) GDPR (consent)
Revocation: Possible at any time via unsubscribe link in the newsletter
Processing: Newsletter data is stored on a GDPR-compliant server

hCaptcha

We use hCaptcha (provider: Intuition Machines, Inc., USA) to protect against spam and abuse. When using hCaptcha, data is transmitted to servers in the USA.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest)
Privacy Policy: https://www.hcaptcha.com/privacy

Waitlist Management (Brevo)

When you sign up for our waitlist, we use Brevo (provider: Sendinblue GmbH, Germany) to store and manage your contact information. Brevo is a GDPR-compliant email marketing platform with servers located in the EU.

Data collected: Email address (required), name, phone number, city, and your selected interests/roles
Legal basis: Art. 6(1)(a) GDPR (consent - provided when submitting the waitlist form)
Retention period: Until you unsubscribe from the waitlist or request deletion
Data location: EU servers (GDPR-compliant)
Privacy Policy: https://www.brevo.com/legal/privacypolicy/

Donations via this website

On the Donate page you can support OneFamily.uno once, without an account. Mollie handles the payment itself; we do not store card or bank details. For each donation we store a payment record and, only if you choose to give it, your email address so we can send you a payment confirmation. That confirmation is not a tax receipt: OneFamily.uno is not a registered non-profit yet.

Data stored: Amount, currency, date, payment status, Mollie payment reference, website language and, optionally, your email address
Legal basis: Art. 6(1)(b) GDPR (processing your donation and sending the confirmation you asked for) and Art. 6(1)(c) GDPR (statutory tax record-keeping)
Retention period: Your email address is deleted once the confirmation has been sent, at the latest after 30 days. The payment record, without your email address, is kept for the statutory retention period (§ 147 AO).
Recipients: Mollie B.V., Amsterdam, Netherlands, processes the payment as an independent controller under its own privacy policy. Brevo (see above) sends the confirmation email on our behalf.
Mollie privacy policy: https://www.mollie.com/legal/privacy

5. Analytics Tools and Advertising

GoatCounter Analytics

This website uses GoatCounter, a privacy-friendly web analytics service. GoatCounter uses no cookies and does not collect personal data.

The following anonymous data is collected:
- Pages visited (URL)
- HTTP referrer (origin of visit)
- Browser and operating system (without version)
- Device type (desktop/mobile)
- Country (based on IP, but IP is not stored)

Legal basis: Art. 6(1)(f) GDPR (legitimate interest)
Special feature: Since GoatCounter does not use cookies and does not collect personal data, no consent is required
Privacy Policy: https://www.goatcounter.com/help/privacy

6. Your Rights

You have the following rights regarding your personal data:

  • Access (Art. 15 GDPR): Right to information about your stored data
  • Rectification (Art. 16 GDPR): Right to correction of incorrect data
  • Erasure (Art. 17 GDPR): Right to deletion of your data
  • Restriction (Art. 18 GDPR): Right to restriction of processing
  • Data Portability (Art. 20 GDPR): Right to data portability
  • Objection (Art. 21 GDPR): Right to object to processing
  • Complaint (Art. 77 GDPR): Right to lodge a complaint with a supervisory authority

To exercise your rights, please contact:

Competent Supervisory Authority

Bavarian State Office for Data Protection Supervision (BayLDA)
Promenade 18
91522 Ansbach
Germany
Phone: +49 (0) 981 180093-0
Email:
Website: www.lda.bayern.de

7. Cookies

This website uses only technically necessary cookies that are required for the operation of the website. These are set without your consent as they are essential for the functionality of the website.

No tracking or marketing cookies are used.

8. SSL/TLS Encryption

For security reasons and to protect the transmission of confidential content, this site uses SSL/TLS encryption. You can recognize an encrypted connection by the fact that the address bar of the browser changes from "http://" to "https://" and by the lock symbol in your browser bar.

9. Poster Module — Third-Party Platform Integrations

The OneFamily.uno Poster module (poster.onefamily.uno) lets members publish their own content to third-party social media and email platforms. This section applies only if you choose to connect at least one of these platforms — it does not apply to members who use the core OneFamily.uno features only.

Lawful basis

We process data shared through the Poster module on the basis of your explicit consent (Art. 6(1)(a) GDPR), given each time you authorize a new platform via OAuth or by pasting a personal API key. You can withdraw this consent at any time by disconnecting the platform inside the Poster app.

Categories of data

When you connect a third-party platform, we store the following on our servers in Germany:

  • An OAuth access token (and refresh token where applicable), encrypted at rest, used only to publish content you author
  • The third-party platform's user ID, so we can route published content to the correct account
  • A list of the pages, organisations, lists, or groups you choose as publishing targets
  • The content you author (text, media, scheduled time) until it has been delivered to the platform

Third-party recipients

Once you choose to publish via a platform, the post content you author is transmitted to that platform's servers. Each platform is an independent controller for the data it processes after delivery.

  • Meta (Facebook, Instagram): post content + access token. United States. Transfer covered by the EU-US Data Privacy Framework.
  • LinkedIn: post content + access token. United States. Transfer covered by the EU-US Data Privacy Framework.
  • Mailchimp (Intuit): campaign content + access token. United States. Transfer covered by the EU-US Data Privacy Framework.
  • Meetup: event content + access token. United States. Transfer covered by Standard Contractual Clauses in Meetup's Data Processing Addendum.
  • Brevo (Sendinblue): campaign content + API key. France, EU. No international transfer.

International transfers

Where data is transferred outside the EU/EEA (Meta, LinkedIn, Mailchimp, Meetup), we rely either on the EU-US Data Privacy Framework or on Standard Contractual Clauses. You can request a copy of these safeguards by contacting us.

Retention

OAuth tokens and API keys are deleted immediately when you disconnect a platform or delete your OneFamily.uno account. Post and campaign history is retained for 12 months from the date of publication, then automatically purged by a weekly job. Operational logs that may contain pseudonymous references to platform connections (which user connected which platform and when) are retained for security and debugging purposes; these logs never contain access tokens or post content and rotate on a regular schedule.

How to revoke

You can disconnect any platform at any time from the Poster app's Connections screen. We will revoke the token at the platform side immediately and delete our local copy. You can also revoke access directly from the platform (e.g. in your Facebook Business Settings) — we detect this on the next API call and mark the connection as inactive.

10. Blockchain Storage and Encryption Keys

OneFamily.uno is building toward a blockchain-anchored economy (Polygon PoS) so that ORE token balances and reciprocity records can be independently verified. This section explains what we will write to chain, the immutability that comes with it, and how your encryption keys protect you. Today no data is on chain — smart contracts have not been deployed yet — but the disclosure below applies the moment they go live.

Today: nothing is on chain

As of this version of the privacy policy, no part of your data is written to any public blockchain. Everything described below is forward-looking and will apply once the smart contracts (OREToken, OREActivityTracker, OREMinting, OREVault) are deployed on Polygon PoS.

What will be written to chain once contracts are live

Only the minimum required for verifiable economic accounting:

  • ORE token balances — your aggregate received / usable / invested amounts, indexed by a hashed user identifier (not your email, name, or any other personal identifier)
  • Activity references — hashes of unlock activities (deeds, payments, invitations, welcome bonus) so they can be independently audited
  • Daily minting + age-backlog distributions — aggregated, pseudonymous

Blockchain entries are immutable

A core property of public blockchains is that entries cannot be deleted or altered after the fact. This means that even after you delete your OneFamily.uno account, the pseudonymous hashes and ORE balances written for you remain on chain. They are not personally identifiable on their own — without our database mapping, they are just numbers next to a hash.

Encryption and your keys

If a future feature ever encrypts personal content before writing it on chain, the encryption uses a key held by you (the user) — not by us. Deleting your copy of the key renders the corresponding on-chain entry cryptographically unreadable, even though the encrypted bytes themselves remain on the ledger. This is consistent with the GDPR concept of "crypto-shredding" recognised by EU data protection authorities.

Your right to download your keys before deletion

When you initiate account deletion, you are offered a download containing all your personal data plus your encryption public key and any blockchain identifiers we use for you. We strongly recommend you download this archive before confirming deletion — without it, you cannot later prove ownership of an on-chain entry. The download is also available at any time from your in-app Security settings.

11. The OneFamily.uno App

The sections above describe this website. This section describes the OneFamily.uno app — the mobile app for iOS and Android and the web app at app.onefamily.uno — which collects personal data that the website does not. It adds to the sections above rather than replacing them: the controller named in section 3, your rights in section 6, the transport encryption in section 8 and the blockchain statement in section 10 all apply to the app as well.

What the app stores about you

All of the following comes from you, when you create an account and use the app. None of it is bought from or received from anyone else, and none of it is used for advertising.

  • Name and email address: Your display name and your email address, so that you can sign in, so that other members of your neighborhood circle can recognise you, and so that we can write to you about your account — a verification code, a password reset, a moderation decision. The email address is stored unencrypted, because sending those messages requires reading it.
  • Date of birth: Stored encrypted, and used to check that participation is age-appropriate. It is never shown to other members.
  • Landline number: Optional, and stored encrypted. It is not shown to other members; it appears only in your own profile and in the data export described below.
  • Location: Your neighborhood circle is a hexagonal area of roughly one square kilometre, and the circle is what other members see — never your address. If you ask the app to use your current position, to find your circle or to centre the map on you, it reads the device position once while the app is open; it never reads your position in the background. When you attach a place to a request, an offer or a resource, the coordinates you picked are stored with that entry and visible to the members who can see it.
  • Photos and videos: Pictures you upload for your profile or for a request, offer, resource or Dream. They are kept in object storage rather than in the database, and are reached through signed links that expire.
  • Direct messages: Sender, recipients and the message text. Messages are stored so that a conversation is there on your next device; they are not end-to-end encrypted, which means they are technically readable on our servers.
  • Requests, offers, resources and Dreams: The title, description, category and details you enter, and the status of whatever follows from them. These are shown to the members of the circles you post them in.
  • Push notification token: A token that identifies your installation of the app rather than your device, and that changes when you reinstall. It is stored with your profile so that notifications can reach you, and switched off when you sign out, after which it is not used to send you anything.

Legal basis: Art. 6(1)(b) GDPR, performance of the contract you enter when you create an account, for your name, your email address, your messages and the content you post. Art. 6(1)(a) GDPR, consent, for your position, for each photo or video you choose to upload, and for push notifications — each of which you can withdraw at any time in the app or in your device settings. Art. 6(1)(b) together with Art. 6(1)(f) GDPR, our legitimate interest in age-appropriate participation, for your date of birth.
Where it is stored: On servers of Hetzner Online GmbH in Falkenstein, Germany: both the database and the object storage that holds your pictures. Neither is replicated outside the EU. The only data that leaves this setup goes to the recipients named below, and to no one else.

kAI and AI-assisted features

AI features are off until you switch them on under Profile, AI settings. While they are off, nothing you write in the app is sent to an AI provider. Once they are on, using an AI-assisted feature — asking kAI to draft a request, an offer or a Dream, or letting your entries be matched by meaning rather than by keyword — sends the content of that entry to Mistral AI for processing.

What is sent: The text of the entry you are working on and, if you attached one, its picture. Your name, your email address and your contact details are not part of the request.
Legal basis: Art. 6(1)(a) GDPR, consent. The AI setting is that consent, and switching it off ends this processing for everything you do afterwards.
Recipient and transfers: Mistral AI, through api.mistral.ai. A data processing agreement is in place. Mistral gives no commitment to process only inside the EU, so processing outside the EU/EEA is possible, in which case it rests on an adequacy decision or on standard contractual clauses. If you enter your own API key under AI settings, your content goes to Mistral under that key and under your own agreement with them instead of ours.
Mistral AI's privacy policy: https://legal.mistral.ai/terms/privacy-policy

Other services the app passes data to

Each of these receives only what its own task needs. Nothing is passed on for advertising, and nothing is sold.

  • Brevo (Sendinblue SAS, France): sends your account emails — verification code, password reset, the notifications you asked for — and therefore receives your email address, your display name and the content of that message. EU, no transfer outside the EU/EEA.
  • Expo push service (650 Industries, Inc., United States): delivers push notifications, and therefore receives your push token and the text of the notification before Apple or Google hands it to your device. Transfer to the United States, for which Expo states that it adheres to the EU-U.S. Data Privacy Framework.
  • OpenStreetMap Foundation (United Kingdom): supplies the map in the web app and the address search you use to find your circle, and therefore receives the map area you are looking at or the address text you typed. The United Kingdom is covered by an EU adequacy decision.
  • OpenRouteService (HeiGIT gGmbH, Heidelberg, Germany): works out the route and travel time to a place attached to a request, offer or resource, and receives the two sets of coordinates involved. EU.
  • Apple and Google (native app only): the map inside the mobile app is drawn by Apple Maps on iOS and by Google Maps on Android, so whichever of the two applies receives the map area the app asks for. The web app uses OpenStreetMap instead.

Payments in the app

The app takes no payments. It carries no purchase, subscription or donation screen on any platform, so no payment data arises there. Donations run through the Donate page on this website and are described in section 4.

Health and fitness data

The app collects none. There is no connection to Apple Health, Google Fit or any comparable service.

How long we keep it

For as long as your account exists. There is no separate expiry per category: deleting your account is what ends the processing described here. Where a statutory period applies to a particular record — the tax retention on a donation, for instance — it applies to that record alone, and that case is covered in section 4.

Export and deletion in the app

Under Profile, Security you can download everything we hold about you as a JSON file, and you can delete your account. Deletion takes effect the moment you confirm it: your display name is replaced, your picture, date of birth, landline number, encryption key and any stored AI key are removed, your circle memberships end, your open requests and offers are cancelled, and any publishing accounts you connected are disconnected at the platform concerned. Thirty days later your login record, including your email address, is deleted as well.

Two consequences are worth stating plainly. The emptied profile row itself is kept, so that other members' records of help given and received do not break; it no longer holds anything that identifies you. And deletion cannot be undone — your data is removed when you confirm, not at the end of the thirty days — so download your export first if you want a copy.

Nothing about your use of the app is written to a public blockchain today. Section 10 describes what is written, and what is not, once that goes live.

The rights listed in section 6 cover everything in this section, and the same contact address applies.