OFRAVA
Открываем страницу…
OFRAVA
Открываем страницу…
Privacy
What the product needs, when data is stored and what remains under your control.
Last updated: August 18, 2026
Offer text is sent to OFRAVA's server to perform the analysis and is not published. The source contract is not added to cloud deal history without user action. Hosting and infrastructure providers may still generate technical service logs.
OFRAVA uses an HttpOnly cookie to remember the guest review. The server also limits repeated guest reviews using a cryptographic HMAC hash of the network address. The anti-abuse table does not store the raw IP or offer text; hosting providers may still keep their own technical logs.
Analysis history is stored in your browser by default. If a signed-in user enables cloud sync, saved deals may sync to the account. Local history can be cleared from the workspace.
For signed-in users, follower count, average views, engagement and niche may be saved to creator context. These data can personalize the fair range; they are not required to review rights and risks.
When a payment is created, OFRAVA stores the order identifier, selected plan, amount, currency, account identifier and technical payment status. Payments are processed through YooKassa. Card credentials and other sensitive payment data are handled by the payment provider; OFRAVA does not store CVV, online-banking passwords or full card credentials.
Quota and STARTER/PRO grants can be changed only by server-side code using a service credential. The public browser cannot call entitlement-grant functions. Forms may use Cloudflare Turnstile, with tokens verified on the server. Remove personal information that is not needed to understand the commercial deal before submitting a contract.
If you submit the contact form, OFRAVA stores the email address, topic and message. When email notifications are enabled, these data are also delivered to the configured support inbox through the email provider. Do not send passwords, CVV, private keys or unnecessary personal data.
Local history can be removed from the workspace. Account, creator context and synced cloud data can be deleted from the Account area. For order, support or data questions, use the Contact page; the order number is enough and no banking secrets are required.
If storage, synchronization, anti-abuse or billing flows change, this policy will be updated before the new handling rules take effect.