This Notice explains how Mira handles information when you draft, edit, and enhance video. It is written to be read in full rather than skimmed, and it applies to every Mira feature that links here. Where a feature needs something beyond what is described below, we ask separately before that processing starts.
1. Device permissions
1.1 What we request
Mira uses the standard permission prompts provided by your operating system. Each one is triggered by an action you take, and each can be withdrawn later from your device settings without uninstalling the app.
| Permission | Trigger | Scope of use |
|---|---|---|
| Photo library | Opening the media picker to add a clip or still image. | Reading only the items you select for the current project. We do not enumerate, index, or upload the rest of your library. |
| Camera | Choosing to record footage inside the app. | Capturing video for the project that is open. The camera is not accessed in the background. |
| Microphone | Recording with sound, or adding a voice-over track. | Recording audio for the take you explicitly start and stop. |
| Save to library | Exporting a finished sequence. | Writing the exported file back to your device storage. |
| Notifications | Opting in after starting a longer render job. | Telling you a render has completed or failed. Not used for promotional messaging. |
1.2 Declining a permission
Refusing a permission disables only the feature that depends on it. For example, declining microphone access still lets you import, trim, and export silent footage. Mira does not repeat a prompt after you have refused it; you can grant access later from system settings.
2. Information we process
2.1 Content you provide
This covers the clips, images, audio, and written directions you bring into a project. Content stays on your device unless a feature requires remote rendering, in which case it is uploaded for that single job as described in section 3.
2.2 Information generated by use
Operating the app produces technical records, which may include:
- Failure diagnostics — crash traces, render error codes, and the app version in use
- Hardware context — device model, operating system version, available codecs, and screen characteristics needed for playback compatibility
- Feature counters — which tools were opened and how long a session ran, used in aggregate to judge product health
- Connection data — IP address and network type, retained briefly for delivery and abuse prevention
2.3 What we do not ask for
Core video work does not require your legal name, postal address, date of birth, or phone number. If you contact support, whatever you choose to put in that message becomes part of the support record.
2.4 Aggregated measures
We compute totals such as install counts and feature adoption. These are statistical and do not identify anyone. If aggregated figures were ever combined with identifiers in a way that could single you out, we would treat the result as personal information under this Notice.
3. Rendering and processing partners
3.1 Why material leaves the device
Drafting a clip and running repair passes such as upscaling, stabilisation, and noise reduction are computationally heavy. Those jobs run on specialist processing infrastructure rather than on your phone.
3.2 What is transmitted
For a remote job we may send:
- The specific clip, frame, or audio segment the job operates on
- The written direction or parameter settings you entered
- Technical job metadata such as target resolution and duration
Before the first such transfer, Mira tells you the category of recipient, the purpose, and the material involved, and asks for your explicit consent. Declining affects only the feature that needs remote rendering.
3.3 Limits placed on partners
Processing partners act on our documented instructions under contract. They may use the material solely to complete the job you requested. Reuse for marketing, resale, long-term profiling, model training, or any unrelated purpose is not permitted.
3.4 People appearing in footage
Video frequently contains recognisable faces and voices. Where a clip you submit includes them, those characteristics are processed only to produce the output you asked for. They are not retained for identification, matching, advertising, or product experiments. You are responsible for having the consent of anyone identifiable in material you upload.
4. Retention
Working copies used for a render are removed once the job completes successfully, or irreversibly anonymised where deletion is not technically possible. Failed jobs are cleared on the same basis after a short diagnostic window. Diagnostic logs are kept for a limited period and then deleted or aggregated. Support correspondence is kept for as long as needed to resolve the matter and to meet record-keeping obligations.
5. Lawful bases
Depending on the processing and where you live, we rely on:
- Your consent, for remote rendering and optional permissions
- Performance of our terms with you, to deliver the app
- Legitimate interests, for security, abuse prevention, and reliability
- Compliance with legal obligations
6. Your choices and rights
6.1 What you can ask for
Subject to local law, you may request to:
- Access the personal information we hold about you
- Correct records that are inaccurate or incomplete
- Delete information, within the limits the law allows
- Withdraw consent where consent is the basis for processing
- Object to or restrict certain processing
- Complain to your local supervisory authority
6.2 Making a request
Write to support@pgreen.xyz. Please include enough context for us to locate the relevant records and to be satisfied the request comes from you. We respond within the period set by the law that applies to you.
6.3 When a request may be refused
We may decline or narrow a request where:
- Identity cannot reasonably be verified
- It is repetitive, excessive, or clearly unfounded
- Acting on it would obstruct a legal process or investigation
- The records concerned are anonymised statistics only
- Another statutory exemption applies
Withdrawing consent stops future processing on that basis. It does not undo processing that already took place lawfully.
7. Security
We maintain layered technical and organisational measures, including:
- TLS for data in transit, and encryption at rest where appropriate
- Access restricted to personnel who need it for their role
- Monitoring, logging, and network segmentation
- Security review and contractual commitments for vendors
No system is perfectly secure. Where a breach is likely to affect your rights, we will notify you and the relevant authorities within the timeframes the law requires. We do not sell personal information.
8. Children
Mira is not directed at children under 14, or under the higher age set by your jurisdiction, without verifiable consent from a parent or guardian. If we discover we have collected such information without the required consent, we delete it. Guardians may write to us to review, correct, or remove a child's information.
9. International transfers
Rendering infrastructure may be located outside your country. When personal information crosses a border we apply appropriate safeguards, such as standard contractual clauses and technical protections, so that the level of protection remains consistent with this Notice and applicable law.
10. Third-party destinations
Exports you share to other platforms, and any external links from this site, are governed by those services' own terms and privacy policies. Once a file leaves Mira, its handling is outside our control. We suggest reviewing their notices before sharing.
11. Updates to this Notice
We revise this Notice when our practices, technology, legal obligations, or product scope change. Significant revisions are surfaced in the app or on pgreen.xyz, and the version line at the top of this page is updated. Continued use after a revision means you accept it, except where the change requires fresh consent, which we will request separately.
12. Contact
Privacy questions, permission queries, and data requests all go to support@pgreen.xyz. If our response does not resolve the matter, you may escalate to the data protection authority for your region.