About Services Contact

LMC Flow Analytics — Privacy Notice

Effective 14 November 2026

1. Scope

1.1 This notice explains how NJ LIFESTYLE & MANAGEMENT SL processes personal data through LMC Flow Analytics: website statistics, Instagram account data and, where authorised, the captions of posts.

1.2 It explains what data we process, why we process it, who receives it, how long we retain it and how you can exercise your rights.

2. Our role and contact details

2.1 NJ LIFESTYLE & MANAGEMENT SL, a company established in Spain and the company behind LMC Flow, operates LMC Flow Analytics. We are the controller where we process personal data for our own purposes described in this notice. Contact: info@lmcflow.com.

2.2 Where we process personal data on behalf of a client for its website or accounts, the client is the controller and we act as its processor, on its instructions.

3. Information we access

3.1 Website statistics, with access granted by the owner to Google Analytics and Google Search Console: the number of visitors, where they come from and which pages they read; how the website appears in Google search, including the words people searched for. Totals and trends only; no profiles of individual visitors. On the owner's request: adjusting how the statistics are collected and kept, and sending Google the list of the site's pages.

3.2 Instagram accounts connected, through a Facebook Page, to our business account at Meta: the account's name and identifying details; basic details and links of its posts; the figures showing how the account and its posts perform, such as reach, views, likes, saves, shares and the number of comments.

3.3 Captions: the text of the posts' captions, for the accounts of our own publications, for the personal accounts of people who have consented to caption analysis, and for client accounts only where the client has separately instructed us to do that work. A caption may contain the names of the people mentioned in it. We do not use captions to identify those people or to build lists of people.

3.4 Not accessed: the text of comments; lists of the people who follow an account or react to its posts.

3.5 Search interest: we use our own Google account to obtain search-volume estimates for selected keywords. This does not use data from your accounts.

3.6 Connection records: to run the software we keep the identifiers of the connected accounts and pages (account id, page id and, in older records, username) in our configuration, in the raw statistics files and in our work records. We hold no passwords or access tokens of account owners.

4. Purposes and legal bases

4.1 Website statistics (3.1): to understand what works on the website and to prepare the owner's reports, within the work agreed with the owner. Here we act on the owner's instructions. We do not include one client's non-public data in another client's report.

4.2 Instagram figures (3.2): to prepare the owner's reports. Where the owner contracts with us personally, the basis is that contract; where the account belongs to a client, we act on the client's instructions. For the accounts of our own publications: our legitimate interest in understanding and improving them.

4.3 Captions (3.3): to learn how the author writes, in order to prepare editorial rules and draft captions for the captions we propose to that author or publication. Basis: for our own publications, our legitimate interest in a consistent editorial voice; for personal accounts, the account holder's consent. For client accounts we act on the client's documented instructions; the client determines the basis for its own processing.

4.4 We share a client's non-public Google data with an AI service provider only after obtaining the client's explicit permission.

4.5 Giving us access is voluntary. Without it we cannot do the related work.

5. Recipients

5.1 We use hosting providers to operate our systems.

5.2 We use AI service providers while we prepare reports, study writing style and draft captions. They receive the statistics and, for the accounts under 3.3, the captions we work on, and process them under their own terms. In the AI accounts we use for this work, the providers' option to train on our data is switched off.

5.3 We share only what the work requires. You can request the names of these providers by contacting us.

5.4 We never sell your data and never use it for advertising.

5.5 Some recipients process data outside the European Economic Area, including in the United States. Basis: European Commission adequacy decisions, including the EU-US Data Privacy Framework where it covers the company and the data, or the European Commission's standard contractual clauses. Details and a copy of the safeguards: info@lmcflow.com.

6. Data retention

6.1 Raw statistics, and the captions read with them: up to 400 days from the day we receive them.

6.2 Working files, including copies of captions and the notes made while studying them: deleted at the first quarterly clean-up after the work has been closed for 90 days, so up to about six months after closure. The raw statistics files, the working copies of captions and the notes made while studying them are kept outside our backups.

6.3 Editorial rules for the captions we propose: they contain editorial instructions in our own words and newly written examples, not copies of captions. Rules drawn from the captions of a person who has consented are kept in a single file outside our code repositories and outside our backups for as long as we propose captions to that person, and are deleted within 90 days after we stop, or within 30 days after the person withdraws consent (7.3). Rules for our own publications are kept for as long as we propose captions for them.

6.4 Connection records (3.6): in our configuration while the account is connected; in the raw statistics files for their 400 days; in our work records as in 6.2. Our task records and our code change history keep the account identifiers as a record of which accounts we had access to and when; they are used for nothing else. New records carry a numeric id or a label rather than the username. In our task records we keep the identifiers for as long as the records of that work exist and no longer than six years after that work ends; then we delete them from each record. On request we remove the username from our task records earlier. We do not edit our code change history, so it keeps the identifiers already in it.

6.5 Final reports that must be kept as business records under Spanish commercial law: six years from the last entry in the relevant accounting books, unless another legal retention period applies, then deleted at the first quarterly clean-up. Other personal data in final reports: deleted or returned when the agreed work ends, unless a specific dispute requires us to keep it until the dispute and any related proceedings end.

6.6 Copies held by AI service providers while they help us: under those companies' own terms (5.2). Our own conversations with these tools are kept as files on our computers. Captions never enter our ordinary conversations: the software writes them to files only, and we study them in separate runs that keep no conversation file. Of the ordinary conversation files, only those that our main AI assistant starts in its registered windows after 9 November 2026 are deleted automatically: once 12 months have passed without activity in them and the computer has since been restarted, so the wait can be longer and has no fixed end; a conversation a window is still holding is not deleted. All other conversation files — those already open on that date or continued from an earlier one, those the clean-up cannot identify, the logs of our other AI tools and sessions outside those windows — are not deleted on a schedule.

6.7 Data held on a client's behalf is returned or deleted sooner where the client's instructions or the law require.

6.8 The routine periods in this section do not postpone deletion required by law or by our obligations to the account owner, including the consequences of withdrawing consent (7.3).

6.9 Our computer backups hold copies of our other working files and of our ordinary conversation files, and serve only to restore our systems; they are not opened for any other purpose. For the working files we have set a limit of 90 days, which applies once our backup retention rule is installed; until then, and for the conversation files, backup copies are not deleted on a schedule.

7. Your rights and withdrawal of access

7.1 You can stop our access at any time. Website statistics: remove our team's access in Google Analytics and Search Console. Instagram: disconnect your Instagram account from our Facebook Page in your Instagram settings; our software then stops reading it. In both cases you can also email us and we will stop. Revoking access does not automatically delete data we already hold; you may request deletion by email.

7.2 Where these rights apply, you can ask us to show you, correct or delete your data, to restrict its use, or to give it to you in a file.

7.3 If you have consented to caption analysis, you can withdraw your consent at any time by emailing us. We stop using your captions on the day your message reaches us. Within 30 days we delete the captions we hold in our raw statistics files and working files and the editorial rules drawn from them; none of these are in our backups. Copies held by AI service providers remain under their own terms (5.2); the account identifiers in our work records stay as described in 6.4. Withdrawal does not affect what we lawfully did before.

7.4 Where we rely on legitimate interests, you have the right to object to that processing on grounds relating to your particular situation.

7.5 Contact: info@lmcflow.com.

7.6 You also have the right to lodge a complaint with a data protection authority.

8. Changes

8.1 If we change the data we access or how we use it, we will update this notice and notify the affected account owners before the change takes effect.

8.2 Before accessing new types of Google data or using Google data in a new way, we will update this notice, explain the change and obtain your agreement.