repostiva.

REPOSTIVA · 2026-09-29

Privacy

Repostiva is a product of Neodelta Labs LLC. For privacy questions or requests about your data, email support@repostiva.com. This page describes the current test version and website; it will be updated before introducing new uses of data.

Optional store-review access on Android, when enabled, sends the review username and password supplied by Repostiva to the server. These are not Google or social-network credentials. We do not save that password on the phone; the server checks its hash. To verify access and prevent abuse, operational records associate the installation identifier with an expiration time and sign-in attempts. Sessions last up to 24 hours and attempts are counted over ten minutes; expired records are periodically pruned. Signing out or deleting the installation identity removes its review access. This access does not share libraries or create a purchase or subscription.

Your library, files, creators and descriptions are stored on your device. Repostiva does not synchronize that library with a cloud account or request social media passwords. Copies in Photos and system backups are managed separately under your settings.

When you request a download, we send the link to Repostiva’s server. It retrieves files and metadata from the source platform to deliver them to you. Temporary files normally expire after ten minutes; removal completes after active operations finish. The source platform and infrastructure providers receive connection data needed to handle the request.

Requesting a download or opening Pro may create a random installation identity. Its credential is kept in secure phone storage; the server stores a hash of that credential and an identifier, not the original credential. Abuse prevention uses timestamps, usage counts and a protected representation of the connecting network. Quotas use windows of up to 24 hours, and records are pruned as the service is used. Infrastructure may also generate connection and error logs.

Advertising measurement with Meta is optional and initially off. If you allow it, activation, first-import and first-save events are sent along with SDK technical data and identifiers allowed by your settings. Meta also receives the connection IP address and may use it to estimate an approximate location; we do not request GPS access. The SDK attaches technical information such as device model, operating system, language and storage capacity. We do not include links, files, creators or descriptions in those events. You can withdraw consent in Settings; the system tracking permission also applies on iOS.

When you open Pro in a build with purchases enabled, RevenueCat receives the random installation identifier and SDK technical data. Apple or Google and RevenueCat process products, transactions and subscription history to verify, restore and manage Pro access and analyze its operation. We do not send your library, links, creators or descriptions to RevenueCat. Repostiva does not receive your card number. Deleting the Repostiva server identity does not automatically erase purchase history held by RevenueCat or the store or cancel subscriptions; contact support with requests about that data.

The app checks Expo’s update service, which receives an installation identifier and technical connection, platform and version data to deliver compatible updates. Following a fatal error, it may also send error information to diagnose update problems. The website remembers only your language in the browser and includes no advertising analytics. Hosting processes the connections needed to serve it. These providers may process data outside your country.

If you contact us, we process your email address and message to handle and follow up on your request. Do not send unnecessary data. You can request access, correction or deletion of your data and exercise rights available under applicable law. Use the app’s deletion option to remove the server identity; it is not linked to your email.

When this feature is available in your version, Privacy → Delete purchase records lets you prepare a temporary code and an email to support@repostiva.com to request deletion of RevenueCat records linked to your installation. Nothing is sent automatically. The server keeps a hash of the code, the installation identifier, its expiry and, if support verifies it, a case reference for up to seven days, subject to periodic service cleanup. Issuance records for abuse prevention use a one-hour window. Support correspondence and the case are kept separately while the request is handled and for applicable obligations; you may request their deletion. The code does not cancel subscriptions or delete Apple or Google records. Send it only to support; never send your installation credential or passwords.

support@repostiva.com

Links, files and recipients

The link you submit, metadata and retrieved files may be temporarily associated with your installation identifier to fulfill the download. We do not access your browser history. Importing a local file does not by itself upload your library to our server. When sharing through another app, you choose the destination and subsequent processing depends on that service. Rights reports are handled as support requests; do not attach identity documents or unnecessary material.

Versions that enable subscription measurement request fresh consent. With your permission, we send offer views to Meta and verified trial starts and payments from RevenueCat through our server, including amount, currency and technical identifiers. Events are deduplicated. Server consent expires 30 days after the last check while using the app; conversions may be recorded while the app is closed during that period. Turning it off stops local events and informs the server; without a connection, withdrawal is retried when you reopen the app online. On iOS we also require ATT. We do not send your files, links or descriptions. A temporary per-installation count of prepared posts enforces the daily limit and contains no URLs.