Information still required
The list below is the minimum needed before the draft banner can be removed. Until each item is filled from the real application, the matching section stays unresolved.
- Confirmation of the legal entity that owns the Google Play developer account, and whether that entity is CHLOE CONSTRUCTION GROUP LTD.
- Each app’s public name, Android package name, and the stores in which it is offered.
- An effective date, and the name of the person who can approve later changes.
- A privacy contact that has been checked, such as a monitored email address or a postal address the publisher will actually read.
- A current build of each app, including its manifest, dependency list and SDK initialisation, so collection can be described from code rather than from assumption.
- Every permission the app requests, and the feature that needs it.
- Whether any data stays on the device only, and whether any data is transmitted, to whom, and for what purpose.
- Whether advertising or analytics SDKs are linked, including Google AdMob, AppLovin, Meta Audience Network, Appodeal, or any other network.
- Whether accounts exist and, if they do, how a person creates and deletes one.
- How long each category of data is kept, and how a deletion request is carried out.
- The intended audience, including whether children are part of it. No age rating should be written here until the store listing states one.
Apps covered and developer identity
The configuration block above is the only place this page records publisher identity, app names, an effective date and a privacy contact. If a field says it is not confirmed, it has not been established. CHLOE CONSTRUCTION GROUP LTD is the operator of this website. That fact alone does not make it the publisher or the controller of a mobile app. It is named as an app publisher on this page only after developerConfirmed is set and the legal name is filled in config/app-privacy.json.
Data collected, sources and purposes
A finished policy has to list the personal data each app collects, whether the person provides it, whether the app generates it, or whether an SDK collects it, and the purpose of each item. That list is not written here. No application source was available to inspect, so this draft does not claim that the apps collect nothing, and it does not invent categories of data.
Processing on the device and data that is transmitted
It is not confirmed whether any processing stays on the device, or which fields are sent to a server or to an SDK provider. Those two cases have to be separated in the finished policy, because a person cannot judge a transmission that the policy never mentions. Until the build is inspected, neither case is described as fact.
Advertising identifiers and device information
It is not confirmed whether an app reads an advertising identifier, a device identifier, an IP address, or device details such as model, language or operating system version. If a later inspection shows that an SDK transmits those values, the finished policy must say so even if the app’s own screens do not ask the user to type them.
Usage data and crash diagnostics
It is not confirmed whether any app records usage, diagnostics or crash reports, or which provider would receive them. Absence of a visible analytics screen is not evidence that no diagnostic SDK is linked.
Sharing and service providers
No service provider is named as a recipient of app data, because none has been identified from source. The finished policy should name each provider that actually receives data, the purpose, and a link to that provider’s privacy notice. Providers that are not integrated should not be listed as if they were.
Advertising networks
Google AdMob, AppLovin, Meta Audience Network and Appodeal are not described as integrated. They are also not described as absent. No application binary or dependency file was available to check. Official privacy links for those companies will be added only for a network the source actually includes. Naming them here is a checklist, not a disclosure of use.
Advertising consent and privacy choices
If an app uses ads that require a consent choice, the finished policy should explain the choice, how to refuse, and how to change the choice later, including any regional message required by the network. No such control is described here, because no advertising integration has been confirmed. Do not read this silence as a statement that ads run without consent, or that ads do not run.
Permissions
Each dangerous or special permission needs a purpose tied to a feature the person can understand. That table cannot be written until the manifest is read. This draft does not list camera, location, contacts, microphone, storage or any other permission as used or unused.
User-selected media and system pickers
If an app lets a person pick a photo, video or file through the system picker, the finished policy should say what is selected, whether the file leaves the device, and why. It is not confirmed that any app offers a picker, so no picker practice is described.
Accounts
Account creation and deletion are covered only if accounts exist. That has not been confirmed. This draft therefore does not include registration steps or a deletion button path. If accounts are later confirmed, the policy must explain how to delete an account and what happens to the related data.
Retention and deletion requests
No retention period is stated, because no data flow is confirmed. A finished policy should say how long each category is kept and how a person can ask for deletion. A request route will be published with the privacy contact once that contact is confirmed. Until then, this draft does not invent a deletion mailbox.
Security
A finished policy should describe the safeguards that are actually used, such as encryption in transit, and it should not promise that storage or transmission is perfectly secure. No app-specific safeguard has been verified from source, so none is claimed here.
International transfers
It is not confirmed whether app data leaves the United Kingdom, or which countries or providers would receive it. Transfer tools such as the UK International Data Transfer Addendum should be described only for transfers that actually occur.
Children and the intended audience
The intended audience has not been confirmed. This draft does not invent an age rating, an age gate, or a statement that the apps are or are not directed at children. Those points must follow the real store listing and the real design of the app. If children are an audience, the finished policy has to meet the stricter rules that apply, including limits on advertising identifiers where those rules apply.
User rights
People may have rights of access, correction, deletion, restriction, objection and portability, depending on the law that applies to them and on whether the publisher is a controller of their information. Because the publisher and the data flows are not confirmed, this draft cannot yet tell a person which rights apply to which app, or where to send a request beyond the unresolved privacy contact above. When the publisher is confirmed, the finished policy should name the rights in plain language and the time in which a reply is aimed for.
Privacy contact
The privacy contact for the apps is the value in the configuration block. If that value says it is not set, there is no confirmed app privacy contact. The registered office of CHLOE CONSTRUCTION GROUP LTD is the privacy contact for this website only. It becomes the app privacy contact only when the configuration says so and the developer identity has been confirmed.
Effective date and changes
This draft has an effective date only if one is set in the configuration. Otherwise there is no effective date. When the policy is finished, changes should be posted on this page, or on a replacement page at this path, with a new date. A material change to collection should be described in the text, not only by changing the date.
Google Play
Google Play asks for a public privacy-policy URL. This address can be opened publicly, which is why the draft is here. Publishing it does not mean the policy is complete, and it does not mean Google Play has approved or will approve any app. Do not submit this URL as the policy for a live listing while the draft banner is still on the page.
If two apps later collect different data, they need separate sections on this page or separate policy URLs. One blended description should not be used to cover different practices.