Vosm · Last updated: September 23, 2026
Vosm is the product name. The operator is responsible for the app and these documents. Operator legal name: [REQUIRED BEFORE PUBLICATION]. Postal contact address: [REQUIRED BEFORE PUBLICATION]. Support telephone: [REQUIRED BEFORE PUBLICATION]. Contact email: LivigniDistasio358@outlook.com.
This Policy describes Vosm, a photography app offering camera capture, photo editing, drawing, clarity enhancement, photo grids, hosted photography guides and a preset-based assistant. It explains the difference between on-device processing and hosted account or content services. Reading this Policy is not consent to unrelated processing or a waiver of privacy rights.
Supabase Auth processes the email address or generated account alias, password and authentication requests you submit, and maintains the account identifier and authentication records needed to operate your account. Vosm stores the active session, including access and refresh tokens and account information, in device-only Keychain storage.
The current profile editor saves your selected avatar, nickname and personal signature in an account-associated file in the app’s Application Support directory on this device. Saving these edits does not upload them to Supabase or publish them to other users. Existing hosted profile information and avatar images may be downloaded to populate the profile. Local profile editing is not a cross-device synchronization service.
Vosm uses Apple’s system photo picker to access images you select, rather than requesting unrestricted access to your library for editing. Camera access and permission to add saved results to Photos are requested separately. Permission refusal prevents the related operation, not consent to unrelated data use. Photos may contain people, locations or other personal information; select only content you are entitled to use.
The Apple option uses the user identifier returned by Apple to find Supabase email-and-password credentials saved in this device’s Keychain. On first registration, the app generates an account alias under doeenvosm.com and a random password. The alias is not an Apple private-relay address or a personal mailbox assigned to you. It must not be treated as an email address you can independently access for recovery.
These credentials use device-only Keychain storage and do not synchronize through iCloud Keychain. The backend does not return a password based solely on the Apple identifier. Losing these local credentials or changing devices may prevent access through this flow. Sign-out retains the generated credentials; successful account-deletion cleanup removes matching credentials. This limitation does not remove your right to contact us about your personal data.
Collection: Vosm does not create or collect facial landmarks, face geometry, facial embeddings, biometric templates or facial-recognition identifiers. It does not identify people, authenticate them by their face, or infer personal attributes from their faces. A photo or camera frame may nevertheless contain a person’s face; such image pixels are personal information when they identify someone. This distinction does not mean that photos containing faces are never processed.
Purpose: Vosm processes selected images and camera frames on the device to show the viewfinder, take photos, crop, rotate, flip, adjust color and brightness, reduce noise, sharpen detail, apply filters and frames, add drawings and compose grids. These are image-processing operations, not a face-recognition or face-analysis service. The smoothing control reduces image noise; it does not create a facial model.
Upload and sharing: The current camera, editing, drawing, enhancement, grid and local avatar-editing features do not upload selected or captured images, facial measurements or face templates to our backend or to an AI provider. Vosm does not sell these images or use them to train AI models. Saving to Apple Photos can make the result available to iCloud Photos or other services according to your separate device settings and choices; those copies are not a Vosm cloud photo store.
Storage: Working images and previews are held in app memory during use. An unsaved capture may remain in memory so you can retry a failed save. Successfully exported images are stored in your Photos library. A selected profile avatar is stored in the local profile file described in Section 2. No separate facial or biometric database is maintained.
Retention: Working images remain while the relevant editor or camera state is retained in memory, until replaced, released or the app process ends; Vosm does not promise immediate erasure merely because you navigate away. Saved photos remain in Photos until you delete them, subject to Photos, Recently Deleted, backup and synchronization settings. A local avatar remains until replaced, removed by successful account cleanup, or the relevant app data is deleted. There is no retention period for facial templates because Vosm does not create them. See Section 6 for other storage and retention rules.
Vosm downloads a curated photography-guide library from Supabase and matches your message to keywords on this device. It does not call a live generative-AI service. Assistant messages are not uploaded as prompts to Supabase or an AI provider by this feature. The library contains shooting suggestions and neutral or clarification replies; matching is limited and may not capture the meaning of a message.
A Camera button on a matching plan passes structured settings to the camera, including image ratio, filter, noise reduction, brightening, clarity, timer, flash choice and grid visibility. Effects are applied after capture; the live view is unfiltered. Unsupported hardware features may be unavailable. This is a preset application workflow, not a claim that AI analyzed your face or photo.
Messages, unsent input and the loaded guide list are held in the current assistant screen’s memory. The current app does not implement a persistent or cloud-synchronized assistant history or draft database. They may be lost when that screen is released or the app process ends. Ordinary networking caches may retain downloaded public guide responses; they do not receive the typed message from the matching feature.
Account and hosted profile records are kept while needed to provide the account, subject to deletion requests and applicable legal obligations. An account-deletion request is sent to the account service; local cleanup follows a successful response. We do not promise a specific backend backup or log purge deadline without confirming the production configuration.
Device-only Keychain session records remain until cleared through successful sign-out or account-deletion cleanup. Generated Apple-assisted credentials remain after sign-out and are removed by matching account-deletion cleanup. Uninstalling the app must not be relied upon to erase Keychain records.
Local profile files remain across app launches and sign-out. They are associated with the account identifier and protected by the device’s file-protection facilities; they are not a promise of isolation from someone with access to the unlocked device. Successful account cleanup attempts to remove that account’s local profile file.
Downloaded public works, cover images and publisher avatars may be stored in the app’s Caches directory and memory. Valid cached works may be reused on later launches; pull-to-refresh retrieves current work data. There is no fixed automatic expiration or guaranteed deletion deadline for these caches. They can remain until replaced, evicted by the system or removed with app data. Account deletion does not automatically remove public-content caches.
Unsaved photo edits, drawings, enhancement settings and grid selections are not stored as persistent project drafts. Save images you wish to keep before leaving or closing the app. Exports in Photos are separate from the app’s data and are not removed by sign-out, account deletion or app removal. Device backups and synchronization can retain copies under your settings.
[REQUIRED BEFORE PUBLICATION: confirm the production database and Storage regions, authentication/security-log retention, backup retention and purge schedules, deletion handling, and any applicable legal-retention exceptions. Replace this note with the actual periods or documented criteria. Do not infer them from this client implementation.]
Vosm downloads works, covers, publisher information and shooting guides to display catalog and detail pages. Some content is prepared or sample content. Public covers and publisher avatars may be served from public Storage URLs and are not confidential files.
The current client does not provide an operational public-comment, photo-publication, gift-purchase or in-app reporting submission flow. Displaying content or editing a local photo does not publish your photos. Contact the email in Section 13 for privacy, safety or copyright concerns. Do not assume an inactive interface control submits a report.
The current implementation does not initiate in-app subscription or virtual-gift purchases or maintain local subscription or gift transaction records. Inactive subscription or gift interface elements do not themselves create a purchase, charge or entitlement.
Apple provides system authorization, photo selection, camera permissions and Photos storage according to the operations you request. Apple may process information separately under its own policies. Any future payment feature must disclose its price, billing terms, entitlements and data practices before it is used. Existing Apple-billed purchases, if any, are governed by their applicable purchase terms; app removal or account deletion does not by itself cancel a subscription.
Supabase processes authentication requests and serves hosted profiles, public media and prepared content. Requests to these services and to policy hosting may expose technical data such as an IP address, request time, requested resource and response or security-log information. This is different from uploading the photos or messages used in local editing and matching.
Vosm does not use assistant messages or locally processed photos for advertising, sell them, or send them to a third-party AI provider. Information you send to our support email is used to respond and address the issue, and is processed by the email provider. Do not email passwords, authentication tokens or unnecessary sensitive images.
Information may be disclosed where legally required, to protect people or service security, or in a lawful business transfer with required notices and safeguards. These provisions do not remove the operator’s legal responsibilities for its own processing or providers acting on its behalf.
Where applicable, information is processed to provide requested account or service features, comply with legal duties, and protect the service through proportionate legitimate interests recognized by law. Consent is used where required. Device permission does not waive privacy rights. Withdrawing consent does not affect earlier lawful processing.
Hosted information may be processed outside your country. [REQUIRED BEFORE PUBLICATION: identify the actual processing locations and applicable transfer safeguards, including how users can obtain information about those safeguards.] No data-residency guarantee is made without verification.
You can choose which images to import, decline or revoke camera and Photos permissions in system Settings, delete exported photos through Photos, and use the account actions available while signed in. Signing out clears the active session after the service request succeeds but retains local profile files and generated Apple-assisted credentials.
Delete Account requests deletion through the authenticated account service. After a successful response the app attempts to remove the local profile, matching generated credentials and session. Network, server or local-storage failures can interrupt completion; retry or contact us. Deletion does not remove exported photos, independent external copies, all public-content caches or information that must lawfully be retained. Removing the app does not replace a hosted-account deletion request.
Depending on applicable law, you may request access, correction, deletion, portability or restriction, object to certain processing, withdraw consent, and complain to a competent supervisory authority. Contact LivigniDistasio358@outlook.com and identify the relevant account or records. We may request proportionate identity verification, but not your password or authentication tokens. We respond within applicable legal deadlines and explain lawful exceptions.
Vosm uses device Keychain and file-protection facilities and authenticated requests where appropriate. No system guarantees absolute security. Protect your device and credentials. Downloaded public media is not confidential storage. Backups, shared devices and independent copies may affect deletion and access.
The service is not directed to children under 16. If a child has provided personal information, a parent or guardian should contact us so we can take appropriate steps under applicable law. Higher local age or parental-consent requirements continue to apply. The operator must keep the actual audience and store disclosures consistent with this policy.
We may update this Policy and its date as the service changes. Material changes receive notice or consent where legally required. An update does not retroactively authorize incompatible processing. External sites have their own privacy practices, without removing our obligations for providers acting on our behalf.
Vosm is the product name. The operator is responsible for the app and these documents. Operator legal name: [REQUIRED BEFORE PUBLICATION]. Postal contact address: [REQUIRED BEFORE PUBLICATION]. Support telephone: [REQUIRED BEFORE PUBLICATION]. Contact email: LivigniDistasio358@outlook.com.