# Privacy Policy

> What Headloom collects, how images are processed and deleted within 24 hours, who receives data, and your rights.

- **URL**: https://headloom.com/privacy
- **Last Updated**: 19 October 2026

---

Headloom is an AI image-editing service operated by **Latent Mind Labs LLP, India** (**Headloom**, **we**, **us**, or **our**). This Policy explains how we handle personal data when you visit [headloom.com](https://headloom.com/), sign in, upload images, generate results or contact us.

**The short version:** we use account data to provide and protect the Service. We temporarily store images to complete your request and return the result. Routine uploads and temporary processing files are deleted within **24 hours after upload**, and routine generated outputs within **24 hours after generation**. We do not use your images or outputs to train AI models, sell them, or publish them in a public gallery. Account, security and other legally required records are retained separately.

## 1. Who is responsible for your data

Latent Mind Labs LLP is responsible for the account, security, support and other personal-data processing described in this Policy. Where applicable, we act as a controller or data fiduciary. If we process images solely on a business customer's documented instructions under a separate data-processing agreement, we may act as that customer's processor for that processing.

- **Privacy contact:** [suraj@headloom.com](mailto:suraj@headloom.com)
- **Grievance Officer:** Suraj Narayanan

## 2. What we collect

| Category | Information and source |
| --- | --- |
| Account information | Your name, email address, profile picture and account identifier provided through Google sign-in. Firebase Authentication maintains the sign-in account record. We do not receive your Google password. |
| Images and processing data | The image to edit, the reference image, generated outputs and temporary files or image features needed to perform the edit. Images may contain personal data about you or someone else. |
| Service and consent records | Account/user ID, job reference, request time, processing duration, result or error status, usage limits and your permissions confirmation. |
| Technical and security data | IP address, browser or device information, request paths, timestamps, authentication and security events, and related server logs generated when you use the Service. |
| Communications and reports | Messages, contact details, complaint information and any relevant evidence you choose to provide when you contact us or report misuse. |
| Purchase information | Order reference, purchased and used credits, transaction status, amount, currency, tax and invoice details. Our payment provider processes card and other payment details under its own notice; we never receive your full card number. Free swaps do not require a card. |

Please do not submit unnecessary personal data, confidential documents or sensitive information unrelated to the requested edit. Do not upload images of minors or prohibited content. If image metadata contains location or other personal information, remove it before upload if it is unnecessary.

## 3. How images and face information are used

Your browser sends the source images to our processing infrastructure. Our models run on contracted GPU infrastructure in the European Union to generate the requested edit. Producing a head or face replacement involves analysing visual features such as head position, facial appearance, hair and lighting, and may produce temporary crops, masks or other processing data.

We use this processing to perform the requested edit. We do not use your images to identify or authenticate people, create a persistent facial-recognition database, or sell face profiles. Some laws impose additional rules on particular uses of face information. Where those rules apply, any required additional notice or consent must be provided before that processing begins.

We do not use uploads, outputs or derived face information to train or fine-tune our own or a third party's AI models. Any future optional model-training programme would need a separate, clearly explained opt-in before the content was used. Refusing it would not change the terms of an already completed generation.

Routine generation is automated. Staff do not manually approve every output. Authorised personnel may access necessary information to resolve a support request, investigate reported misuse, respond to a security incident or comply with law. This does not authorise model training or routine public display.

## 4. Why we use personal data

We use the information described above to:

- create and maintain your account, authenticate access and provide requested generations;
- return results, administer usage limits and, if introduced, manage credit purchases and billing;
- protect the Service, investigate abuse, diagnose failures and improve operational reliability using appropriate service metadata;
- send a few short emails about getting started and your free swaps, each with an unsubscribe link that stops them;
- respond to support messages, privacy requests and complaints; and
- meet legal, tax, accounting, security and regulatory obligations and establish or defend legal claims.

We do not sell or rent personal data, use your images in advertising, or share personal data for cross-context behavioural advertising.

Where the GDPR, UK GDPR or a similar law requires a legal basis, we use contractual necessity for account services requested by the account holder, legitimate interests where recognised for proportionate security, abuse prevention and service administration, legal obligations where applicable, and consent where required. A contract with an uploader does not by itself provide a contractual legal basis for processing another person's data. For people shown in uploaded images, the relevant permissions and any legally required consent must cover the actual image processing and intended use. If a feature requires explicit consent or another additional condition for protected face information, that requirement must be met before the feature is used.

Where we act as a business customer's processor, that customer is responsible for establishing the appropriate legal basis and notices for its instructions. We remain responsible for obligations that law independently assigns to us.

## 5. Images of other people

You may upload another person's image only if you have the required image rights, their informed permission for the proposed edit, and any consent required for our processing. You should make this Policy available to them before upload where required by law. Permission to use an ordinary photograph may not cover AI alteration or advertising use.

People whose likeness appears in an image can contact us directly, even without a Headloom account. We will assess privacy and misuse reports and assist with requests as required by our role and applicable law. If a file has already been deleted, we cannot recover it or remove copies independently held outside Headloom.

## 6. Cookies and browser storage

We use essential cookies, local storage or similar technology for sign-in sessions, security and necessary application functions. Firebase Authentication helps maintain your signed-in session. You can sign out or clear browser storage, although disabling necessary storage may stop parts of the Service from working.

We do not currently use advertising cookies or optional advertising trackers. If optional analytics or advertising technology is introduced, we will explain it and obtain consent before activation where required. Signing out of Headloom does not necessarily sign you out of Google or clear data held independently by Google.

## 7. Who receives personal data

We disclose only information reasonably necessary for the purpose involved to:

- **Google/Firebase Authentication**, for account sign-in and authentication. See [Firebase privacy and security information](https://firebase.google.com/support/privacy) and [Google's Privacy Policy](https://policies.google.com/privacy).
- **Website, application and infrastructure providers**, to deliver the website and operate accounts, requests, temporary storage and service/security logs.
- **Our contracted GPU/inference infrastructure provider**, to process images and return results. Routine image inference takes place in the EU.
- **Communication and support providers**, to deliver necessary account communications and respond to messages and reports.
- **Our payment provider, Razorpay Software Private Limited (India)**, to process authorised purchases and associated fraud, tax and billing matters.
- **Professional advisers and competent authorities**, where necessary for advice, legal claims, lawful requests or required reporting.

Providers processing data for us must do so under appropriate contractual instructions and safeguards. A provider may also process some information independently for purposes for which it is legally responsible, such as Google's own account services or a payment provider's fraud and regulatory duties.

If the business is involved in a merger, reorganisation or asset transfer, necessary personal data may be disclosed under confidentiality safeguards and transferred subject to applicable law. The recipient must be informed of the commitments in this Policy; any materially different use requires the notice and legal basis required by law.

## 8. Where processing takes place

We operate from India. Image inference is hosted in the EU, but not all account, support, website or security processing is EU-only. Firebase Authentication currently processes authentication data in the United States, and other providers may process information in their operating locations.

Where international-transfer rules apply, we use the legally required safeguards, such as an applicable adequacy decision or approved contractual clauses with any necessary additional measures. Contact us for information about safeguards relevant to your data, subject to legitimate confidentiality restrictions.

## 9. Retention and deletion

| Information | Retention approach |
| --- | --- |
| Routine input images and associated temporary processing files | Deleted within **24 hours after upload**. This includes routine copies and processing artefacts under our control or our providers' processing instructions. |
| Routine generated outputs | Deleted within **24 hours after generation**. Download a result if you want to keep it. We do not offer long-term media storage. |
| Account information | Kept while your account is active, then deleted or restricted following account closure, except for the limited records we must retain. Where applicable Indian intermediary rules require it, registration information is retained for 180 days after cancellation or withdrawal. |
| Service, consent-confirmation and security logs | Kept for the period necessary to operate the Service, investigate misuse and meet legal duties. Where Indian cybersecurity directions apply, required ICT logs are retained securely for at least 180 days and maintained in India as required. Longer retention is limited to a legal obligation, incident or documented legal need. This is not a requirement to keep every uploaded image for 180 days. |
| Purchase and invoice records, if applicable | Kept for the period required by applicable tax/accounting law and to resolve payment disputes. |
| Support messages, complaints and evidence | Kept while needed to handle the matter, complete any required preservation and address related legal claims, then deleted or anonymised. Images you separately submit as complaint evidence are handled as complaint records, rather than routine generation files. |

Routine storage replicas, image caches, temporary files and any image backups follow the same 24-hour media deletion windows. Account, security and other record categories follow the separate retention rules described above.

A specific legal preservation requirement, valid legal hold, reported abuse or security incident may require limited records or relevant available content to be retained longer. We restrict such retention to what is necessary and legally permitted. An exception does not mean we can recover material that has already been permanently deleted.

Copies you download, place on another service or share with someone else are outside our storage systems. Deleting your Headloom account does not delete those copies.

## 10. Your choices and rights

You can stop submitting images, sign out, request account deletion in the Studio, or email [suraj@headloom.com](mailto:suraj@headloom.com). Account deletion ends normal access and starts deletion of account data, subject to the retention exceptions above. It does not require you to give up a complaint or billing right.

Depending on applicable law, you may ask to access, correct or delete personal data; obtain a portable copy; restrict or object to processing; withdraw consent for processing based on consent; or nominate another person to exercise rights where that right exists. Withdrawing consent does not invalidate earlier lawful processing or require us to erase records we must lawfully retain.

We may request proportionate information to verify a request or an authorised representative. Do not send government identification unless we request it through an appropriate channel. We aim to respond within one month and will meet any shorter applicable deadline. If a lawful extension is necessary, we will explain it within the original response period.

You can complain to a competent privacy regulator where applicable law provides that right. Statutory rights and regulatory complaint routes apply according to their legal scope and commencement dates.

## 11. Children

Headloom is for users aged 18 or older. Do not submit images depicting anyone under 18. If you believe a minor has an account or has been depicted through the Service, contact us so we can investigate, restrict access and delete or preserve/report information as legally required.

## 12. Security and incidents

We use reasonable technical and organisational measures appropriate to the information involved, including encrypted transmission, authenticated service access and restrictions on access to personal data. No system is completely secure.

We will investigate suspected incidents and make notifications to affected people or authorities when required by applicable law. Contact [suraj@headloom.com](mailto:suraj@headloom.com) if you suspect unauthorised access or another security issue.

## 13. Privacy complaints and grievance officer

- **Grievance Officer:** Suraj Narayanan
- **Organisation:** Latent Mind Labs LLP
- **Email:** [suraj@headloom.com](mailto:suraj@headloom.com)
- **Suggested subject:** "Headloom privacy grievance"

Describe your concern and provide a way to contact you. An account is not required to report a problem involving your likeness. We will handle grievances within applicable legal deadlines; content-removal and other urgent reports may require faster action than an ordinary privacy request.

## 14. Changes to this Policy

We will update this Policy when our practices change and revise the date above. We will give appropriate notice of material changes before they take effect and obtain fresh consent where required. We will not treat acceptance of a general policy update as permission for an incompatible new use of your images.
