HomeFolio
Back to HomeFolio

Signing in and your data

What we ask for, and exactly why.

HomeFolio needs an account so that a home belongs to someone and stays private to them. You can register with an email address and a password — the password is stored as a hash, so nobody here can read it — or sign in with Google or Apple and not have one at all. If you use a provider, what it hands over is below, and it is all we receive.

Sign in with Google

Choosing Continue with Google asks Google to confirm who you are. Google then passes HomeFolio three things, and nothing else:

  • Your nameFills in your display name, so the other members of a shared home see a person rather than an address. You can change it in Settings.
  • Your email addressIdentifies your account. It is what an invitation to a home is matched against, and how we reach you about the account itself. We send no marketing.
  • Your Google account IDAn identifier from Google that lets us recognise you the next time you sign in, so the account works without a password.

These are the standard sign-in scopes openid, email and profile. HomeFolio requests no other scope.

HomeFolio cannot read your Gmail, Drive, Calendar, Contacts or Google Photos, and never asks for access to them. Sign-in is used only to sign you in.

Sign in with Apple

Apple passes the same two details — your name and email address, plus an identifier for your Apple account. If you choose Apple’s Hide My Email, we only ever see the relay address, which works exactly as well.

What happens to what you put in

  • Your home content is yours. Photos, floor plans, documents and notes are stored on our own server and object storage, and are visible only to you, the people you invite into that home, and any AI assistant you connect to it.
  • Nothing is sold or advertised against. There are no advertising SDKs and no third-party trackers in HomeFolio. The front page and this page count visits with Umami running on our own server — no cookie, nothing stored on your device, no IP address kept. Nothing inside the app, and nothing in the iOS or Android apps, is measured.
  • You can delete all of it. Settings → Account → Delete account removes your account, the homes you own and their files. For a copy of your data, write to the contact address at the end of this page; we answer within 30 days.
  • The full detail is in the policy below — what is collected, the legal basis for it, how long it is kept, and your rights under the GDPR.

Privacy Policy

Last updated: 19 October 2026

This Privacy Policy explains how HomeFolio (“HomeFolio”, “we”, “us”) collects, uses and protects personal information when you use the HomeFolio app and website — the home documentation and virtual tour service at https://homefolio.cloud and in the HomeFolio apps for iOS and Android.

HomeFolio is the data controller for that information. You can reach us at the address under Contact, at the end of this page.

This notice is written for transparency under the GDPR and similar laws. It is not legal advice.

1. What we collect

  • Account: name, email address, password (stored hashed) or Sign in with Apple / Google identity
  • Home content you upload or create: home name, optional address, floor plans, rooms, photos (including 360°), videos, documents, notes, links, contact details you attach to items, LiDAR / room measurements and 3D models (on supported iPhones and iPads)
  • Sharing: membership (who you invite), invite links, and member display names / emails visible to other members of a home
  • Feedback you send: your message, its category, any photo you attach, and which screen, app version, platform and language it was sent from — kept with your account so we can answer you
  • Technical: session token (cookie or on-device storage), basic server access logs (for example IP address, time, path) used for security and rate limiting
  • Push notifications, if you turn them on in the app: your device's push token and platform (iOS or Android), and your device's time zone and language, so reminders arrive at the right local time and in your language. Each notification's text is kept until it is sent: a shopping list's name and who added which item, or an upkeep task's title and when it is due.
  • AI assistants you connect: the connection itself (the name the assistant gives itself, the permissions you approved, and when it was last used), and a line in the server log for each request it makes: which tool, which home, which account and whether it worked. The log does not record what was sent back.
  • Visits to the public web pages (the front page, this policy, the terms of service and the support page): the page visited, the page that referred you, any campaign parameters in the link, your browser, operating system, device type, screen size, language, and the country, region and city your address belongs to. This is counted by Umami, which we run on our own server. It sets no cookie and stores nothing on your device. Your IP address is used to work out the location and to build a one-way hash that stands in for "the same visitor", and is not stored. The hash is re-salted every month, so a visitor cannot be recognised from one month to the next, and never across other websites. Nothing you type is collected, and if your browser sends a Do Not Track header nothing at all is sent.

None of this runs in the HomeFolio apps or on any signed-in page. The measurement exists only on the pages a stranger can read, and the iOS and Android apps do not contain it.

We do not use advertising SDKs, third-party trackers, or payment processors in HomeFolio today. The visit counting above is our own software on our own server; no analytics company receives it, and it is never combined with your account.

2. Signing in

You can register with an email address and a password, or sign in with Google or Apple.

  • Google passes us three things and nothing else: your name, your email address, and your Google account identifier. These are the standard sign-in scopes openid, email and profile. HomeFolio requests no other scope, and cannot read your Gmail, Drive, Calendar, Contacts or Google Photos.
  • Apple passes the same details, plus an identifier for your Apple account. If you choose Apple’s Hide My Email, we only ever see the relay address, which works exactly as well.

Your name fills in your display name, so other members of a shared home see a person rather than an address. Your email address identifies the account, is what an invitation to a home is matched against, and is how we reach you about the account itself. We send no marketing.

3. Why we process it (purposes and legal bases)

PurposeLegal basis
Create and run your account and homesContract (providing the service you asked for)
Store and show your home contentContract
Invite others and share a homeContract / your instruction
Sign-in with Apple or GoogleContract; the provider authenticates you
Security, abuse prevention, rate limitsLegitimate interests (keeping the service safe)
Count visits to the public web pagesLegitimate interests (knowing whether the site is read, by a measurement that identifies nobody)
Read and answer feedback you send from the appLegitimate interests (fixing and improving the app you use)
Send the push notifications you turned onContract (the reminders and list updates you asked for)
Answer an AI assistant you connectedContract / your instruction
Respond to privacy or support requestsLegal obligation and/or legitimate interests

4. Sharing

  • Other members of a home you own or join can see that home’s content and the member list (including email and display name).
  • Apple or Google if you choose their sign-in.
  • Apple and Google, for push notifications. To reach your phone, a notification's text and your device's push token go through Apple Push Notification service (iOS) or Firebase Cloud Messaging from Google (Android).
  • The AI assistant you connect, and the company that runs it (for example OpenAI for ChatGPT, or Anthropic for Claude). When you connect an assistant, by signing in or with an API key, and it asks HomeFolio something, HomeFolio sends it the answer, within the permissions you approved. That can include the homes and their rooms; items with their notes, links, photos and saved contacts; the text of documents; upkeep tasks and their service history; shopping lists; and members' display names, but not their email addresses. What the assistant's company then does with it is covered by that company's own privacy terms. You choose the assistant, and you can disconnect it in Settings at any time. If an assistant adds to a shopping list, the other members' notification names the assistant.
  • Hosting and infrastructure we use to run the service (database, object storage, server hosting, and the mail server that sends invitations, password resets and address confirmations).
  • Nobody, for the visit counts. Umami runs on our own infrastructure, so the public-page statistics are not sent to an analytics provider.
  • Authorities if required by law.

We do not sell your personal information.

5. Retention

  • Account and home data: until you delete the account or home, or ask us to erase them.
  • Feedback you send: kept until you delete your account, which deletes it and any photo with it, or until you ask us to erase it.
  • Session tokens: expire after about 7 days (you can sign out earlier).
  • Invite links: expire after about 7 days if unused.
  • Server logs, including the log line for each AI assistant request: kept only as long as needed for security and operations (short period), then discarded.
  • Push notifications: your device's push token is deleted when you sign out or delete your account, and a token that stops working is deleted after 30 days. Each notification is deleted 30 days after it is sent.
  • AI assistant connections and API keys: kept, marked as disconnected or revoked, until you delete your account. An assistant's sign-in expires after an hour and is renewed for up to 90 days without asking you again.
  • Public-page visit counts: kept as the site's own history. They hold no name, email, account or IP address, and the monthly re-salting means the records cannot be joined back to a person or followed from one month to the next.
  • Copies cached on your device (for example panorama cache) are removed on sign-out or account deletion where the app controls them.

6. Your controls in the app

  • Delete account in Settings — removes your account, the homes you own and their files. Homes shared with you stay with their owner.
  • Delete a home if you are the owner.
  • Notifications in Settings — choose which notifications this device gets, or turn them off. Signing out also stops them on that device.
  • AI access in Settings — lists every assistant connection and API key, with what it may do and when it was last used, and disconnects or revokes it.
  • For a copy of your data (access / portability), write to the address under Contact at the end of this page. We aim to respond within 30 days.

7. Cookies and similar technologies

HomeFolio uses an essential session cookie (homefolio_token), or the equivalent token stored on your device in the apps, to keep you signed in. It also stores local preferences and a media cache on your device. Essential login cookies do not require a marketing cookie banner, and we set no advertising or analytics cookies.

The visit counting on the public pages is cookieless: it sets no cookie, writes nothing to your browser's storage, and reads nothing back out of it. What it does read is only what your browser announces to every site it loads — its name, the operating system, the screen size and the language — and that is listed in section 1 above. That is why this site asks you to accept nothing: there is no consent banner because nothing is put on your device to consent to.

8. International transfers

Some providers (for example Apple and Google, for sign-in and push notifications) may process data in the United States or other countries outside your own. An AI assistant you connect may be run from outside the EEA too (OpenAI and Anthropic are based in the United States); that transfer happens because you connect the assistant and ask it about your home. Where required, we rely on appropriate safeguards used by those providers, such as Standard Contractual Clauses or an adequacy decision. Our own application database and object storage run on infrastructure we control; we aim to keep them in the EEA where practical.

9. Security

We use reasonable technical and organizational measures: access control, HTTPS in production, hashed passwords, and encrypted secrets where implemented. No method of storage or transmission is perfectly secure.

10. Children

HomeFolio is not directed at children. Do not use it if you are under 13, or under the digital consent age in your country if that age is higher. We do not knowingly collect personal data from children. If you believe a child has provided data, contact us and we will delete it.

11. Your rights (EEA / UK and similar)

Depending on where you live, you may have the right to:

  • Access your personal data
  • Correct inaccurate data
  • Delete data (“erasure”)
  • Restrict or object to certain processing
  • Withdraw consent where processing is based on consent
  • Receive a portable copy of data you provided
  • Lodge a complaint with a supervisory authority (in Norway: Datatilsynet)

To exercise these rights, write to us at the address below. You can also delete your account in the app at any time. We aim to respond within 30 days.

12. Changes

We may update this policy from time to time. The “Last updated” date at the top will change. For significant changes we may give additional notice in the app or on the website.

13. Contact

Questions about this policy, or about the data HomeFolio holds about you:

HomeFolio
Email: haakony@gmail.com
Web: https://homefolio.cloud

This policy is published at https://homefolio.cloud/privacy — the URL linked from the app and from its Google and Apple sign-in configuration.