Privacy notice
This draft explains the information used by LifeAlign and the controls available today. Some operational details remain to be approved and implemented before a commercial launch.
1. Who is responsible
ImpactGraph Technologies Ltd is the data controller for LifeAlign. Registered in England and Wales, company number 16971350. A business address for publication will be confirmed before commercial launch. Privacy contact: privacy@lifealign.app.
2. Information the service uses
| Information | Purpose |
|---|---|
| Account name, email, identifier, verification status and linked providers | Create and maintain your account, confirm identity, link sign-in methods and manage access. |
| Priorities, trade-off choices, perspective and optional reflection notes | Display your values profile and put everyday choices in that context. |
| Lifestyle answers, optional location/context and reported food or travel quantities | Compare your answers with general research and applicable factors, and explain assumptions and gaps. |
| Saved brands, purchase markets, optional products/barcodes/retailers and buying relationships | Maintain your private selections, match the brand you confirm and display sourced company connections. A requested brand name and market enter an operator research queue; product details and saved priorities are not attached to that queue. Authorised operators may access records to run the service. |
| Sign-in identifier, provider and timestamp; account creation and latest-sign-in metadata | Understand use and signup progress, and support account administration. These records are linked to accounts, not anonymous. |
| PoC feedback, page category, review history, account identifier and notification records | Record reports and suggestions, review them, let you follow progress, and email your feedback receipt and status updates. Saved values and lifestyle answers are not automatically attached. |
| Session and verification tokens, resend cooldown record and chosen colour theme | Maintain sign-in, verify an address, limit repeated verification emails and remember a requested display preference. |
| Messages you send us and technical information processed by our suppliers | Respond to requests and operate hosting, identity and database services. Suppliers may process IP addresses and technical logs. |
Email/password credentials pass through the app’s authentication route to Firebase. The application does not store passwords in profile documents or sign-in statistics. With Google or Microsoft sign-in, the provider authenticates you; the app does not request access to mail messages or calendars.
3. Purposes and proposed legal bases
The proposed basis for account and requested comparison processing is performance of a contract or steps you request before one. Security, abuse prevention and proportionate service statistics are proposed legitimate interests. These choices and the legitimate-interest balancing assessment still need the operator’s documented review. Legal obligations may apply to particular records and requests.
Optional marketing is not part of the current signup flow. Adding it would require separate choices and an unsubscribe process. Reading this notice or accepting terms is not consent to unrelated marketing or every possible data use.
4. Values and sensitive information
Personal values and free-text circumstances may reveal health information or religious, philosophical or political beliefs. Please keep optional notes general and avoid identifying other people or adding medical histories, diagnoses or detailed beliefs.
The operator must assess these risks and establish any additional legal conditions needed for sensitive information before expanding collection or profiling. A general terms checkbox would not resolve this. The current rules compare stated priorities and activities; they do not infer protected characteristics or make decisions about employment, credit, insurance or access to essential services.
5. Suppliers, sharing and locations
- Google Firebase and Google Cloud: authentication, session verification and Firestore storage. The configured main Firestore database is in London. This does not mean every identity service, log, backup or support operation is UK-only.
- Netlify: website delivery, server functions and associated operational processing.
- Google or Microsoft: the identity provider you choose, under its own account and privacy arrangements.
- Microsoft 365, when notification email is enabled: your account email address, approval notices, and feedback receipts/status updates are processed through our dedicated mailbox. Feedback receipts quote the feedback you submitted. Saved values and lifestyle answers are not automatically included. Sending records and any delivery reports also remain in the operator’s mailbox under its retention settings, which need confirmation.
- GitHub and OpenAI Codex, when feedback development is enabled: an administrator reviews and approves a separate development brief before sharing it for a proposed code change. Original feedback, account email addresses and saved profiles are not automatically sent. The operator must remove personal details from the brief. Repository history, workflow records and pull requests may be visible according to the repository’s access settings. A human reviews the proposed change before merging.
- Public evidence providers: the backend fetches published datasets and metadata. The current evidence requests do not send your profile or free-text notes as query parameters.
- Open Food Facts, when you choose barcode lookup: our server sends the barcode to retrieve contributed product information. Your account identifier, email, saved brand list and value answers are not sent. The provider sees our server request and processes it under its own arrangements. Lookup results may be cached in server memory for up to one hour. You confirm any product details you save; they do not establish ownership or supply-chain provenance. Product data attribution and ODbL links are shown with the results.
Supplier agreements, subprocessor details, service regions and safeguards for access or transfers outside the UK are being reviewed. No claim of UK-only processing is made. A payment provider has not yet been integrated; this notice must be updated before payment details are collected.
6. How long information is kept
The current app has no automatic inactive-account deletion or age-based expiry of sign-in event records. Displaying the last 30 days of statistics does not delete older events. Account and profile data stay in the service until removed through supported controls or operator action. Feedback, its account-linked review history and email outbox records also require operator removal; automatic feedback expiry is not configured. Mailbox copies and approved development material have separate retention and deletion boundaries.
The login cookie lasts up to 14 days and the verification cookie up to one hour. The theme preference stays in your browser until cleared or overwritten. Supplier logs and backups have separate settings that need confirmation.
A justified retention schedule, deletion procedure and backup-erasure boundaries must be adopted and implemented before these drafts can become final commercial notices. You can request erasure now using the contact below; any legally justified exceptions should be explained in the response.
7. Your rights and practical controls
Depending on the processing and applicable law, you may request access, correction, erasure, restriction, portability, or object to particular uses. Where consent is relied upon, you can withdraw it. These rights are not absolute; we may need proportionate identity checks.
Use the values and lifestyle pages to edit your answers, and the dashboard to download your profile bundle. Lifestyle answers can be removed in the app. That action does not delete your account, values, all logs or supplier records. For an account-wide or statutory request, email privacy@lifealign.app. We must handle requests within applicable statutory timescales; the mailbox and internal handling process need operational confirmation.
Brand controls and research retention
My brands lets you edit, remove or download your own selections, including removing the entire list. The full dashboard export also includes your saved selections. Removing selections does not delete your account, lookup cooldown record, shared research or the research audit history. Research requests retain the requested brand name and market without attaching your identity or product details; shared catalogue records retain reviewed public company facts. There is no automatic expiry of research requests or audits. These records and operator access must be included in the retention and account-wide request procedures.
Administrator company lookups send a public company name or registry identifier to GLEIF or Companies House. They do not automatically include participant identities, saved brands or values. Exact company results are saved as administrator-only evidence drafts; reviews and publication or withdrawal record the administrator identity and time. Confirmed public graph connections include source evidence and dates, without administrator account IDs. Drafts and audit records have no automatic expiry and must be included in retention and account-wide request procedures.
Adding a brand does not initiate paid AI development, automatic web research or an email notification. Source publication and corrections are operator-reviewed, and changes are recorded in an administrator audit history.
8. Security and access
Server-side account checks, restricted database client access, separate administrator roles and secure production session cookies are implemented. Authorised staff and suppliers may access information when needed to run the service. These measures reduce risk but do not guarantee perfect security. Do not email passwords, verification links, access tokens or private keys.
9. Cookies, changes and complaints
See the cookies and storage notice for the current browser controls. Material changes to data use need an updated notice and any additional choices required by law.
You can contact us about a concern and may also complain to the Information Commissioner’s Office. This does not limit your other statutory rights.