Scope and current development status
This policy applies to Eazy Magnify, developed by Eazy Company under the Android application identifier com.eazycompany.eazymagnify. The initial platform is Android, and the application is not yet published.
The inspected Flutter project currently displays a basic Eazy Magnify screen only. It has no camera, image-processing, OCR, text-to-speech, local-settings, advertising, analytics, billing, saving or sharing dependency. Sections below distinguish this current behaviour from planned features.
Data controller and contact
Eazy Company is the public trading name used for the applications and website described in this policy. Where the operator determines how and why personal data is processed, it acts as the data controller.
Privacy questions and requests may be sent to contact@eazycompany.eu.
A separate Legal Notice / Impressum identifying the legal operator and a serviceable business address has not yet been finalised. This privacy policy is not presented as a complete Legal Notice / Impressum.
Camera access and live preview
Current version: the inspected Android release manifest does not request camera permission, and the application does not access or display a camera preview.
Planned feature: camera access is intended to provide live magnification. When implemented, Android will ask for camera permission before the feature can operate. The planned live preview is intended to be processed on the device and not uploaded to an Eazy Company server. This policy will be reviewed against the implementation before release.
Frozen images and image saving
Current version: Eazy Magnify cannot freeze, capture or save an image.
Planned features: users are intended to be able to freeze a camera frame temporarily for closer examination. A frozen frame is intended to remain on the device and not be retained after the user leaves that view unless the user explicitly chooses a future save or share action. Any image-saving implementation, storage permission or system photo-picker integration will be documented here after it exists.
On-device text recognition and recognised text
Current version: no OCR or text-recognition dependency is present, and the app does not recognise or store printed text.
Planned feature: printed-text recognition is intended to run on the user’s device. Recognised text is intended to be available in an accessible reading view without being uploaded to an Eazy Company server. Future controls may allow the user to copy, save or share recognised text; those actions are not yet implemented.
Text-to-speech
Current version: Eazy Magnify does not include a text-to-speech dependency and does not send text to a speech service.
Planned feature: recognised text is intended to be read using the device’s local text-to-speech engine. The exact platform engine and any downloadable voices or associated platform processing will be documented when the feature is implemented.
Local application settings
The inspected app does not yet persist user settings, reading profiles, recognised text, images or magnification preferences. Planned local settings may include visual mode, zoom, brightness, contrast, font, text size, spacing and reading-profile preferences. The implementation and deletion controls will be described before release.
Purchases and subscriptions
No purchase or subscription system is currently implemented. The project does not include Google Play Billing or another payment SDK, and Eazy Company does not currently offer an Eazy Magnify purchase, price or trial.
Premium access is planned for advanced text-recognition and document-reading features. If billing is implemented, this policy will be updated to identify the payment provider, transaction information made available to the app and relevant user controls before subscriptions become available.
Advertising, analytics and crash reporting
The inspected source contains no advertising, analytics, Firebase or crash-reporting SDK. The current app does not display advertisements or send analytics events. If any such service is added, this policy and the relevant store disclosures will be updated before release.
Permissions
The inspected Android main manifest requests no runtime permission. Its debug and profile manifests include internet access solely for Flutter development tooling; that development-only permission is not declared by the main release manifest. The iOS configuration contains no camera, photo-library, speech-recognition or microphone usage description.
Camera permission and any permission needed for a future user-directed save action will be documented only after the corresponding feature is implemented.
Contact and support messages
Contacting Eazy Company is optional. If a user emails contact@eazycompany.eu, Eazy Company receives the sender’s email address, message content, attachments and any technical information the sender chooses to include. This information is used to respond, investigate a reported problem, maintain necessary support records and protect legal rights where necessary.
Data retention
The current application shell does not create app-managed camera images, recognised text or saved user settings. Any ordinary operating-system or Flutter runtime data remains subject to the user’s device controls.
When planned local features are implemented, local information is intended to remain on the device until the user deletes it, clears the app’s data or uninstalls the app. Optional support messages may be retained for the time reasonably necessary to answer the request, maintain support records or comply with legal obligations.
Security
The planned local-processing design is intended to limit unnecessary transmission of camera images and recognised text. However, no application, device or electronic storage method can be guaranteed to be completely secure. Device access, operating-system security and backups remain under the user’s control. Security statements will be reassessed when the planned features are implemented.
User choices and privacy rights
Users can choose whether to contact Eazy Company and what information to include. Once camera access exists, users will be able to deny or revoke it through Android settings; without permission, camera magnification will not operate. Future saving and sharing are intended to occur only after an explicit user action.
Depending on applicable law and the circumstances, users may have rights to access, correct, delete, restrict or object to processing, request portability, withdraw consent and lodge a complaint with a competent supervisory authority. Eazy Company cannot retrieve or delete information that exists only on the user’s device and has not been transmitted to it.
Changes to this privacy policy
Eazy Company will update this policy as Eazy Magnify’s camera, OCR, text-to-speech, storage, sharing, billing or third-party integrations are implemented. The revised policy will be published at this URL with an updated date. The released app, store declarations and this policy must describe the same behaviour.