PhotoVideoFirst Privacy Policy

Version 2026-11-19

1. Data controller

The controller is MAORI DI MARCELLO ORIZIO. Identification and contact details are shown at the end of this page.

2. Scope of the service

PhotoVideoFirst creates, signs, registers and verifies technical evidence for photos, videos and text through HCV-IDs, cryptographic fingerprints, signed certificates, HCVPACK and an online Registry. Free verification may be used without an account; Creator functions require an account and the eligibility conditions shown by the service.

3. Data processed

Depending on the feature, PhotoVideoFirst may process account/profile data, email, acceptance status, device technical data and public-key fingerprints, Apple subscription information, Stripe Identity status and minimum outputs, HCV-IDs, certificates, hashes, signatures, technical metadata, capture signals, security logs and content required for the requested operation. Certified photos, videos and HCVPACK files are stored locally in encrypted form in the app’s private area. When a Creator chooses to share an original, the content is temporarily transmitted to PhotoVideoFirst infrastructure for verification; the technical reference is encrypted server-side before storage in a Cloudflare R2 bucket in EU jurisdiction and can be retrieved by the app only through authenticated, short-lived authorization. PhotoVideoFirst does not sell personal data and does not use user content for behavioural advertising.

4. Purposes and legal bases

Data is processed for account and security, email verification, access recovery, subscription entitlement, Creator identity verification, HCV creation and verification, Registry operation, fraud prevention, support and applicable obligations. Legal bases may include performance of a contract, pre-contractual steps, legal obligations and legitimate interests in security and service integrity. Separate consent is requested where legally required.

5. Stripe Identity

The process may require an identity document, live capture and selfie. Within Stripe Identity, Stripe may process images, document data and, where applicable, biometric data or identifiers under its own notices; depending on the specific purpose, Stripe may act as a processor on behalf of PhotoVideoFirst or as an independent controller. PhotoVideoFirst stores the verification status, the technical session reference and the minimum data needed to link the result to the account and certificates. Data processed by Stripe is also subject to Stripe retention periods, rights handling and deletion procedures.

6. Apple and subscriptions

PhotoVideoFirst receives only technical information needed to determine Creator entitlement and does not directly receive App Store payment details. Deleting a PhotoVideoFirst account does not automatically cancel an Apple subscription.

7. Providers and recipients

Technical providers may include:

8. International transfers

Some providers may process data outside the EEA. Where required, transfers use mechanisms available under applicable law, such as adequacy decisions or Standard Contractual Clauses, together with any additional safeguards that are appropriate and the relevant provider terms.

9. Retention

Account data is retained as needed to provide the service and meet applicable obligations. Encrypted originals and HCVPACK files on the device remain in the app’s private area until removed under the app’s operation or together with local app data. Clear temporary files created for viewing, verification or sharing are deleted when the operation ends. Encrypted technical references stored in Cloudflare R2 and their related records may remain available while the reference is active. Withdrawal immediately disables access and starts physical deletion, which is retried until confirmed, subject to applicable obligations and the technical records needed for audit, security and integrity.

10. Rights

Where applicable, users may request access, rectification, erasure, restriction, portability and objection and may withdraw consent where processing relies on consent. Users may also lodge a complaint with the competent supervisory authority.

11. Account and data deletion

You can request account deletion in the app by confirming your password. Access is suspended and your name, location and device code are hidden from the public summary. There is a 30-day period in which you can cancel the request before it becomes irreversible, or request immediate deletion through support and the confirmation link sent to your email. Confirmed immediate deletion cannot be cancelled. This is a technical reconsideration period, not a period imposed by law.

At the end of the period, or after confirmation of immediate deletion, the service revokes cloud references and completes removal of separable personal data, device associations and identity data processed on behalf of PhotoVideoFirst. If a provider does not confirm removal, the account remains blocked and the service retries. Data processed by Stripe as an independent controller is subject to its own notices and procedures.

Previously issued certificates retain only the technical summary provided for integrity verification. Copies already exported or distributed by third parties are not automatically removed from devices or external services. Rights under applicable law remain exercisable through marcelloorizio@legalmail.it.

Deleting your PhotoVideoFirst account does not cancel renewal of your Apple subscription: manage it separately in Apple settings.

12. Security

PhotoVideoFirst uses technical and organisational measures intended to protect accounts, sessions, technical keys, certificates and data against unauthorised access, loss, alteration and abuse. No system can guarantee absolute security.

13. Updates and contact

This Policy may be updated to reflect changes in the service, providers or applicable obligations. Requests and communications: marcelloorizio@legalmail.it.

When you request video subtitles, the app extracts audio from the selected video and uses Apple Speech. Recognition may run on your device or send audio to Apple’s servers. The app saves subtitles in a separate copy.

Cloud storage and retention · 2026-11-07

Each paid purchase or renewal immediately adds 250 MB on the weekly plan, 1 GB monthly or 10 GB annually.

Capacity accumulates on renewal and is shared by encrypted originals and derivatives. Units are decimal. A full quota blocks new uploads without deleting existing files.

After expiry we retain cloud files for 90 days, then send a notice allowing another full 30 days to renew. Without renewal, server deletion starts after that notice period. Late notices or unavailable verification postpone deletion.

Renewing within the deadline preserves all content already on the server, even above the capacity available for new uploads.

Subscription expiry and cloud deletion do not erase encrypted originals or HCVPACKs in the phone archive. Cloud deletion does not revoke certificates.

After a late renewal you can upload local originals again using Restore cloud copy, within available capacity and subject to ownership and consent checks.

Voluntarily deleting the app, archive, account or keys, or losing the device, may make local copies unavailable. Explicit account deletion follows a separate procedure.

Apple verifies paid purchases and renewals, credited once; restoring a purchase adds no further capacity. Free trials and refunds may exclude or reduce credits. During retention you may export your files without an active subscription.

Credits belong to the original PhotoVideoFirst account. If you change accounts, sign in to the previous one or contact marcelloorizio@legalmail.it to recover access. Support does not credit the same renewal twice or automatically transfer content.

Cloud capacity comes from the owner’s verified personal purchases. A transaction received through Family Sharing adds no cloud capacity.

Public provenance

For certificates supporting the new provenance, the verification page may show acquisition time separately from registration time and a short device code. Your name is published only when authorised by the signed choices and comes from identity verification completed at issuance, not your editable profile name. Location appears only when included and authorised in the signed choices. The service may subsequently restrict visibility without rewriting the signed certificate. Historical certificates retain a compatible minimal summary. Identity verification and technical integrity do not by themselves establish the truth of a scene or statement.

The short device code is stable across content from the same phone: viewers can link certificates even when the name is hidden. These public details are accessible to anyone with the HCV-ID or verification link, not only the initial recipient.

Acquisition time is declared by the device clock and is not an independent timestamp. The server omits it when it is more than five minutes after registration or when there is no valid registration reference. This tolerance does not make the phone clock trustworthy.

Public location is rounded to three decimal places (a grid of about 100 metres in latitude, varying in longitude). This is an approximation, not a guarantee of anonymity or a minimum distance from a home. The page and JSON summary indicate approximate precision. The signed certificate and copies already shared may contain more precise original coordinates: rounding the public summary does not rewrite or delete them.

Withdrawal and visibility-restriction journal

We retain a separate, private technical journal in EU jurisdiction of withdrawals and visibility restrictions for the duration of the service, so restoring a backup does not reactivate withdrawn data or republish hidden information, and to document the operations performed. It contains technical identifiers, event types and dates, visibility restrictions and, where applicable, the already-public minimal certificate summary; it does not intentionally contain names, emails, photos or videos. Technical identifiers are pseudonyms and are not necessarily anonymous.

The journal also includes requests and cancellations: an event alone does not prove that every provider has completed removal. The journal has a technical lock with no expiry and is not subject to the 30-day backup rotation. When the service closes, the last restorable backups and journal retention must be managed separately: the lock does not automatically delete the journal at closure.

Database backups

Database backups, including exports and downloaded copies managed by the controller, are retained for at most 30 days from creation of the original backup; copying or downloading it does not restart that period. They may temporarily contain data already removed from the active database. They are intended for recovery after failures; following a restore, the separate journal is used to reapply withdrawals and restrictions before making data available again. This limit applies to backups, not the active database or the separate journal.

Previous versions

MAORI DI MARCELLO ORIZIO · Via della Battaglia 28, 25030 Maclodio (BS), Italy · VAT 04773680980 · REA BS-640525 · PEC marcelloorizio@legalmail.it