Privacy Policy

Scope

This Privacy Policy applies to the Rimvia mobile application, its public legal and support pages, and related services that link to this policy. Rimvia is an eyewear community for short-form media, fit notes, creator discovery, comments, and limited one-to-one chat.

Some features may be unavailable in a particular build, account, or storefront. This policy describes a category only when that category is processed through a feature you choose to use.

Information we handle

Account and profile information

This may include a display name, handle, avatar, biography, account or session identifiers, sign-in status, and settings. A local-only build may store a profile and session state on your device without creating a server account.

Content and communications

We process material you choose to create or submit, such as videos, images, audio, captions, fit notes, comments, profile text, reports, support messages, and one-to-one chat messages. Chat is available only after you follow a creator in the app; Rimvia does not offer anonymous or random chat.

Activity, safety, and transaction information

This may include likes, following relationships, blocks, reports, moderation decisions, content status, and purchase state. If Diamond is offered, we may process the product, transaction identifier, storefront, verification result, and balance activity needed to support the purchase. Apple processes payment credentials; Rimvia does not receive your full card number from Apple.

Device, permission, and diagnostic information

When you choose a relevant feature, the app may request camera, microphone, or photo-library access. It processes only the media you record or select for that action. Where diagnostics or connected services are enabled, we may receive app version, device and operating system information, IP address, crash details, and service logs needed for reliability, security, and abuse prevention.

Local and online processing

In the current app build, certain profile, feed, post, comment, relationship, chat, and Diamond state may be stored locally on your device. Locally stored information is not automatically uploaded merely because it exists in the app.

When an online feature is enabled, information you submit through that feature may be transmitted to Rimvia and its service providers so the feature can work. The interface and permission prompt identify when you are selecting or recording media.

How we use information

• Provide accounts, profiles, feeds, posts, comments, chat, and support.
• Save your settings and restore the state of actions you take.
• Process and verify Apple in-app purchases if Diamond is offered.
• Review reports, enforce community rules, prevent fraud, and protect people.
• Maintain, troubleshoot, secure, and improve the service.
• Comply with legal obligations and defend legal rights.

The current local prototype does not include third-party advertising or cross-app tracking. If a production service introduces either practice, required permission, disclosures, and store privacy labels must be updated before that processing begins.

Visibility and sharing

Public profile information, public posts, captions, fit notes, and public comments may be visible to anyone who can access the relevant part of Rimvia. One-to-one messages are visible to conversation participants, subject to safety review where a message or account is reported. Reports may be shared with the reported person only when appropriate and without unnecessarily identifying the reporter.

We may share information with:

• vendors that host, secure, moderate, analyze, or support enabled service features;
• Apple for StoreKit purchase processing and transaction verification;
• authorities or other parties when required by law or reasonably necessary to protect rights, safety, and service integrity; and
• a successor in a merger, financing, reorganization, or sale, subject to appropriate safeguards.

We do not sell your payment credentials or private chat content.

Retention and deletion

We keep information only for as long as needed for the purposes above, including providing the feature, maintaining security, resolving disputes, and meeting legal or accounting obligations. Retention varies by category and by whether information is stored only on your device or by an enabled online service.

When account deletion is completed in a production service, it removes the profile and user-generated content tied to the account from active service systems. Limited transaction, fraud-prevention, safety, complaint, and legal records may be retained where required or reasonably necessary, with access restricted and public identity removed where practicable. Residual copies may remain temporarily in protected backups until they are overwritten.

Where an app build provides a real account-deletion service, the request begins from Profile → Settings → Delete Account. A local prototype control that only signs out is not a completed deletion request. Contact Support if the shipped control is unavailable or unclear.

Your choices and rights

You can choose whether to post, comment, connect with another user, send a message, or grant camera, microphone, and photo access. Device permissions can be changed in system settings, although the related feature may then be unavailable. You can use in-app controls to block users, report content, and delete content where that control is offered.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent, and to complain to a privacy regulator. We may need to verify your identity before acting on a request. Legal exceptions may apply.

Contact: support@rimvia.app and use the subject “Privacy request.”

Children

Rimvia is not directed to children who are below the minimum age to use an online service in their region without required authorization. If local law requires parental or guardian consent, that rule applies. If you believe a child has provided information in violation of these rules, contact us so we can review and take appropriate action.

Security and transfers

We use administrative, technical, and organizational safeguards appropriate to the nature of the information. No storage or transmission method is completely secure, so absolute security cannot be guaranteed.

Before a production service transfers information across borders, the public policy must identify the relevant processing regions, providers, and safeguards required for the target markets.

Changes and contact

We may update this policy as the service, law, or data practices change. The date at the top shows the latest revision. We will provide additional notice when required or when a change materially affects your choices.

Contact: support@rimvia.app and use the subject “Privacy Policy question.”