Privacy Policy

1. Who we are

V3T is developed by Matthew Astoria, sole trader trading as 115 Studios. This policy explains how the V3T Android application handles information when you use it.

Privacy questions can be sent to astoria.115studios@gmail.com.

2. What V3T accesses on your device

To perform a device inspection, V3T accesses security-relevant information that Android makes available to the app. This processing happens on your device.

• Device security posture, including screen-lock and supported Android protection-state signals.
• Installed-app metadata such as package name, app label, version, target SDK, enabled or debuggable state, installer source and install or update times.
• App signing-certificate SHA-256 fingerprints used as application identity evidence.
• Security-relevant permissions requested or granted to installed apps. V3T reads permission metadata; it does not read the protected content behind those permissions.
• The base APK file of eligible non-system apps so V3T can calculate an exact SHA-256 hash for local Atlas matching.

3. What 115 Studios does not receive

V3T does not send your device scan to 115 Studios. The current scanning architecture does not require a network connection and contains no analytics, advertising, telemetry, cloud-scanning or remote-configuration service.

• No account or profile is created.
• Your installed-app inventory is not uploaded.
• Your APK hashes and signing fingerprints are not uploaded for threat matching.
• Your scan findings are not sent to an Atlas server or any other 115 Studios service.

4. Atlas security intelligence

Atlas is 115 Studios' in-house security intelligence authority. Atlas definitions are bundled with V3T releases and cryptographically verified on the device before V3T uses them.

Threat matching is performed locally against the bundled definitions. V3T does not need to submit an installed APK hash to a remote service to obtain an Atlas result.

5. Local storage and retention

V3T keeps a private local cache of calculated base APK SHA-256 hashes so unchanged apps do not need to be fully re-read during every scan. The cache is used only for local security inspection.

• A cached hash is automatically invalidated when relevant package, version, update, file-state or signing-identity evidence changes.
• V3T stores a small local preference recording whether first-run onboarding has been completed.
• V3T does not currently maintain a cloud scan history or remote copy of this cache.
• You can remove V3T local app data through Android settings or by uninstalling V3T.
• V3T configures Android to exclude its private app data from backup and transfer where Android platform controls permit.

6. Android access and permissions

V3T requests broad package visibility because the device scanner needs to inspect installed applications. It also requests access to supported Android Advanced Protection state information for device-posture inspection.

V3T itself does not request access to your SMS messages, call logs, contacts, microphone, camera or location for the current device-scanner experience.

Flutter development and debug builds may include Android Internet permission for development tooling such as debugger communication. V3T does not use that development permission to upload scan data, and the production scanning architecture does not depend on it.

7. Sharing, networks and app updates

V3T does not share device-scan data with third parties because that data is not transmitted by the app. Updates to V3T and its bundled Atlas definitions may be delivered through the app distribution service you use. That service may process download or account information under its own privacy terms.

If you choose to contact 115 Studios by email, we receive the information you choose to include in that correspondence. Email providers involved in sending or receiving the message may also process it under their own terms.

8. Lawful basis and your rights

The device information used for a V3T scan is processed locally and is not received by 115 Studios as part of that scan. If you contact us, we use the information you provide to respond to your enquiry and to support or maintain V3T. Where UK data-protection law applies to that correspondence, our usual lawful basis is our legitimate interest in providing support and maintaining the product.

Depending on the circumstances, UK data-protection law may give you rights over personal data held by 115 Studios, including rights of access, correction, deletion, restriction, objection and data portability. You may contact us to exercise an applicable right.

You may also raise a concern with the UK Information Commissioner's Office (ICO).

9. Retention and deletion

V3T's local APK-hash cache remains in the app's private storage until it is replaced or invalidated, you clear V3T app data, or you uninstall the app.

If you contact 115 Studios, correspondence is kept only for as long as reasonably necessary to answer the enquiry, maintain appropriate support records or meet applicable legal obligations.

10. Changes to this policy

We will update this policy when V3T's data handling changes. New processing will not be silently described as local-only if the product architecture changes in the future.

Effective: 15 August 2026.

11. Contact

For V3T privacy questions, contact:

Matthew Astoria
Sole trader trading as 115 Studios
astoria.115studios@gmail.com
www.115studios.co.uk

If you contact us by email, 115 Studios receives the information you choose to include in that correspondence so that we can respond to you. That correspondence is separate from V3T's local scan data.