1. Who we are
Huddled is a private, shared media service operated by Callo Apps LTD, a company registered in England & Wales (Company No. 17194575), registered office 66 Paul Street, London, EC2A 4NA (“Callo Apps”, “we”, “us”, “our”). Callo Apps is the data controller for the personal data described in this policy. For any privacy question or request, contact us at support@huddled.cloud.
2. Scope
This policy explains what personal data we collect when you use the Huddled app, websites, and API (the “Service”), how we use and share it, and the rights you have. It applies to registered account holders, members of shared spaces, guests who join without an account, and developers who use our API.
3. Information we collect
- Account & identity. When you sign up we (through our authentication provider) collect your name, email address, whether your email is verified, and an optional avatar and bio. If you sign in with a third-party account, we receive basic profile information from that provider.
- Your content. The photos, videos, files, captions, comments, and reactions that you and the members of your spaces upload or create, together with related metadata such as file name, type, and size.
- Payment data. Paid plans are processed by our payment provider acting as merchant of record. We do not receive or store your card number or other full payment details — we store only your plan, subscription status, and the identifiers our payment provider returns to us.
- Device & technical data. Information needed to run and secure the Service, such as IP address, browser/device type, and log data, including error reports when something goes wrong (Section 6). For API keys we record the IP address last used with the key.
- Usage data. When you use the Huddled website, web app, or mobile apps, we record how the Service is used, such as the pages and screens you view and the features you use. What we record depends on your choice about analytics cookies. Section 6 describes exactly what is recorded.
- Push subscriptions. If you enable browser notifications, we store the delivery details your browser provides so we can deliver notifications.
- Support communications. Messages you send us and their contents.
- Face data (optional). If you turn on the optional “Find Me” feature, we collect the face data described in Section 4. We never collect face data without your explicit consent.
- Guest data. If you join a space as a guest without an account, we store a display name you choose and an anonymous session token; we do not collect an email for guests.
- Developer & integration data. If you use our API or connect a third-party storage or photo account, we store protected access credentials and the account label you connect. We can access only the files you pick and the files Huddled creates or saves for you.
We do not intentionally collect special-category data, and we ask that you do not use free-text fields to share it.
4. Face data — the “Find Me” feature
Find Me is an optional feature. It finds photos that you appear in, inside your own spaces. It is off until you enroll. This section explains exactly what we collect, why, and when we delete it.
Consent comes first. We collect face data only after you give explicit consent on a dedicated consent screen. This consent is separate from these terms and from any other agreement. We record the date and time of your consent. You can withdraw it at any time by un-enrolling in the Huddled app (Settings → Find Me).
What we collect:
- A face template. When you enroll with a photo or a guided scan, we convert your face into a numeric representation. This template is what we compare photos against. It cannot be reversed into a picture of your face.
- Your enrollment photo. If you enroll with a single photo, we keep that photo until you un-enroll or replace it. If you enroll with the guided scan, every captured frame is deleted immediately after processing — we keep no scan images at all.
- Match results. A private list of the photos our system believes you appear in, with a confidence score.
How matching works, and who can see it:
- Matching is strictly self-search. Photos in your spaces are compared against your template only, to find you. Results are visible only to you — not to space admins, not to other members, not to anyone else.
- Faces of people who have not enrolled are processed transiently in memory during matching and are never stored.
- If you mark a match as “not me”, we store that choice (which photo you rejected — it contains no face data) so the photo is never suggested again.
- Matching runs only in spaces where the feature is enabled by the space’s plan or by your own plan.
Where processing happens. All face detection and matching runs on infrastructure we operate with our hosting sub-processors (Section 7). We do not use any third-party facial-recognition service, and we do not use face data to identify you to anyone, for advertising, or for any purpose other than showing you your own photos.
Retention and deletion schedule. We delete face data when the first of these happens:
- You un-enroll: your template, your enrollment photo, and every match are deleted immediately.
- You delete your account: everything above is deleted, including your “not me” choices.
- A photo is deleted, or you leave a space: the matches tied to that photo or space are deleted.
- We upgrade the matching model: your old template stops being used and is replaced only if you re-enroll.
We never sell, lease, trade, or otherwise profit from face data, and we do not disclose it except to the hosting sub-processors above acting on our instructions, or where the law requires.
Legal bases. In the UK and EEA, face data used to identify a person is special-category biometric data; we process it only with your explicit consent (UK/EU GDPR Article 9(2)(a)), which you may withdraw at any time as described above. In US states with biometric privacy laws, the consent screen is our written notice and release, and the schedule above is our retention and destruction schedule.
5. How we use your data and our legal bases
Under the UK GDPR and EU GDPR we rely on the following legal bases:
- To provide the Service (performance of a contract): creating your account, storing and displaying your media to members of your spaces, enabling comments and reactions, sending service emails (verification codes, password resets, invites), and processing your subscription.
- To secure and improve the Service (legitimate interests): preventing abuse and fraud, enforcing our Terms, automatically checking uploaded media (see below), maintaining reliability and security, finding and fixing errors through error reports and service logs (Section 6), understanding how teams use the Service through team information (Section 6), and measuring use of the Service with anonymous, cookieless analytics until you accept analytics cookies (Section 6). We balance these interests against your rights.
- With your consent: analytics cookies, usage analytics linked to your account, and session recordings (Section 6); sending browser push notifications, connecting optional third-party integrations, and processing face data for the Find Me feature (explicit consent — see Section 4). You can withdraw consent at any time.
- To meet legal obligations: tax and accounting, and responding to lawful requests from authorities.
Automated checks on uploaded media. We automatically check photos and videos uploaded to Huddled for nudity and sexual content, so that spaces only show this content where it is allowed.
- How the check works. Software on our infrastructure scores each photo and samples frames from each video. If a video scores high, an AI model run by our hosting provider (Section 7) looks at a small number of its highest-scoring frames to confirm the result.
- What a flag does. If a space does not allow sensitive content, only the uploader and the space’s admins can see a flagged item. If the space allows it, each viewer’s own sensitive-content setting decides whether the item is shown, blurred, or hidden.
- What a flag does not do. The check does not delete your media, and it does not close or limit your account.
- Human review. Space admins can mark an item as sensitive or clear a flag. Their decision replaces the automated result.
- What we keep. We keep the result with the item, including the score and, for videos, the times of the flagged moments and copies of frames that scored high. Space admins can see those moments and the model’s reasons. We delete all of this when the media is permanently deleted.
We do not sell your personal data, we do not use it for third-party advertising, and we do not run ads.
6. Cookies and similar technologies
Huddled uses strictly necessary, first-party cookies and similar browser storage — for example to keep you signed in, remember your theme preference, and protect sign-in against attacks. We ask before we use analytics cookies (below). We do not use advertising cookies.
Product analytics. To find problems and improve Huddled, we use a product analytics provider that stores the data in the EU (see Section 7). We never use this data for advertising, and we never sell it.
- Your choice. We ask whether we may use analytics cookies when you create an account, or once after you sign in if you have not been asked yet. You can change your answer at any time in Settings → Privacy. We save your answer to your account, and it applies on all your devices. Guests who join a space without an account are never asked and are only counted anonymously.
- Until you answer, or if you decline. We record anonymous visits, without cookies or any identifier stored on your device. To count unique visitors, we use a one-way code built from your IP address, your browser information, and the date. The code changes every day and cannot identify you.
- If you accept. The analytics provider stores an identifier on your device, so we can see how you use Huddled across visits. If you are signed in, we link this to your Huddled account ID, never to your name or email address. Our servers also record some account events linked to the same ID, such as signing up, creating a Space, finishing an upload, and changing your plan. If you use a team workspace, these events also record which team they belong to.
- Team information. For each team workspace, we send the analytics provider the team’s name, plan, number of seats, members, and guests, and its subscription status. We also send team events, such as the team being created, its plan changing, or seats being added. This information is about the team and is not linked to any person. We use it to understand how teams use Huddled, and we rely on our legitimate interest for this (Section 5).
- Session recordings. If you accept and are signed in, we may record how you use the web app or the mobile apps, so we can find and fix problems. Text you type into fields is hidden, and photos, videos, and other images are never recorded.
- What is recorded. The pages and screens you view; which links and buttons you use, without their text; the referring website and any campaign tags in the link; your browser, operating system, and device type; and your approximate location (country, region, and city).
- What is removed first. Before anything is sent, we remove invite links and Space identifiers from page addresses, and all other link parameters except campaign tags. We estimate your location from your IP address, and we do not store the IP address.
For analytics cookies, account-linked analytics, and session recordings, we rely on your consent. For anonymous, cookieless analytics, we rely on our legitimate interest in understanding how the Service is used (Section 5). You can object to anonymous analytics at any time by emailing us, or block analytics with a content blocker without affecting the Service.
Error reports and service logs. When something goes wrong in the website, the web app, the mobile apps, or on our servers, we send an error report to the same analytics provider, so we can find and fix the problem.
- What an error report contains. The error message, the technical trace of where the error happened, your browser or device type, the app version, and the page or screen. Before an error report is sent, we remove invite links, Space identifiers, and link parameters, as we do for analytics.
- Your account ID. We link an error report to your Huddled account ID only if you accepted analytics cookies. If you did not, the error report is anonymous.
- Service logs. Our servers also send their service logs to this provider. Service logs record the requests our servers receive and what the servers did, such as the web address requested and any errors. Before a request is logged, we remove invite links, Space identifiers, and link parameters from the web address. Our web servers’ request logs do not include your IP address, location, or browser details.
- Team and account IDs in logs. Our app logs record which team an action belongs to. They record your Huddled account ID only if you accepted analytics cookies, so we can find the logs for a problem you report.
- Who this applies to. We send error reports and service logs for everyone, including guests, because we cannot keep the Service working without them. You cannot turn them off in Settings. For this we rely on our legitimate interest in keeping the Service reliable and secure (Section 5).
7. How we share your data
Your content is visible only to members of the spaces it belongs to, according to the roles you assign. Beyond that, we share personal data with the service providers (sub-processors) that help us run Huddled, each acting only on our instructions:
- Authentication providers — sign-in, single sign-on, and directory sync.
- Hosting and infrastructure providers — application hosting, database, network delivery, media storage, transactional email, video processing, and automated checks on uploaded media (Section 5).
- Product analytics provider (EU) — usage analytics, session recordings, error reports, and service logs (Section 6).
- Payment provider — payment processing as merchant of record.
- Browser push services — the service run by your browser’s maker, to deliver notifications you enable.
- Storage and photo providers you connect — only when you authorise an integration.
To get the current list of these providers by name, email support@huddled.cloud.
Google user data. Huddled’s use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In plain terms: data we receive from Google Drive or Google Photos is used only to provide the import and export features you ask for — we do not use it for advertising, do not sell it, and do not let humans read it except with your consent, for security, or to comply with the law.
We may also disclose data where required by law, to protect our rights or users, or in connection with a merger, acquisition, or sale of assets. We do not sell your personal data.
8. International data transfers
We are based in the UK and some of our sub-processors are located in the United States and elsewhere. Where we transfer personal data outside the UK or EEA, we rely on an appropriate safeguard — such as an adequacy decision, the UK International Data Transfer Agreement (IDTA) or Addendum, or the EU Standard Contractual Clauses.
9. Data retention
We keep your content while your account and spaces are active. When you delete media we mark it as deleted, then permanently purge it from storage around 30 days later. When you delete your account we erase your personal data and login identity (see below); content you contributed to other people’s shared spaces may remain there so that one member’s deletion does not remove a shared album, but your access is removed. Residual copies may persist briefly in backups before being overwritten. We delete analytics events and error reports (Section 6) after 12 months, session recordings after 30 days, and service logs within 12 months. The daily code used to count anonymous visitors changes every 24 hours. When you delete your account, we also delete the analytics and error reports linked to your account ID.
10. Your rights (UK & EU)
If you are in the UK or EEA you have the right to access, correct, erase, restrict, or object to the processing of your personal data, to data portability, and to withdraw consent. You can delete your account and associated personal data from Settings → Account, or exercise any right by emailing support@huddled.cloud. We aim to respond within one month. You also have the right to complain to your local supervisory authority — in the UK, the Information Commissioner’s Office (ico.org.uk).
11. US privacy rights (California and other states)
We collect the categories of personal information described in Section 3 (identifiers, biometric information (Section 4), account and commercial information, internet/network activity, and user content) for the business purposes described in Sections 4 and 5. In the past 12 months we have not sold or “shared” personal information as those terms are defined under the California Consumer Privacy Act (CCPA/CPRA), and we do not knowingly do so. If you are a California resident — or a resident of another US state with similar laws — you may request to know, access, delete, or correct your personal information, and you will not be discriminated against for exercising these rights. Submit a request to support@huddled.cloud; you may use an authorised agent to act on your behalf.
12. Security
We protect data with encryption in transit, access controls, secure storage of keys and tokens, and reputable infrastructure providers. No system is perfectly secure, but we work to protect your data and to notify you and regulators of a qualifying breach where the law requires.
13. Children
Huddled is not intended for children under 13, and under 16 in the United Kingdom, the EEA, and other regions where a higher age applies. We do not knowingly collect personal data from children below the applicable age. If you believe a child has provided us personal data, contact support@huddled.cloud and we will delete it.
14. Guests
Spaces may allow people to join as guests without an account. For guests we store only a chosen display name and an anonymous session token kept in the guest’s browser; guest uploads are held for review by a space administrator before they become visible. A space owner may ask guests to accept a consent notice before joining.
15. Changes to this policy
We may update this policy from time to time. If we make material changes we will notify you in-app or by email and update the “last updated” date above.
16. Contact
Callo Apps LTD, 66 Paul Street, London, EC2A 4NA, United Kingdom. Email support@huddled.cloud.