Privacy Policy

Jakub Kamiński, ul. Górna 12/4, 72-003 Bezrzecze, Poland; support.ofravo@gmail.com, is the controller for OfraVo account administration, security, support and OfraVo’s own billing information. For customer records processed on a business’s instructions, the business is generally controller and OfraVo processor under the Data Processing Agreement.

This policy is a notice, not blanket consent to all processing. We use contract necessity, applicable legal obligations and proportionate legitimate interests in service operation, security and the establishment or defence of claims, as appropriate. Where consent is actually required, it must be requested separately and may be withdrawn as applicable.

We process account email, business details and preferences; customer names, contact and service addresses; offers, requests and appointments; recorded payments, charges, refunds and costs; invoice details, PDFs and delivery history; uploaded business images; support messages; and necessary technical and audit metadata to provide and protect the requested functions.

Account acceptance records contain the agreement version, document-bundle digest, server acceptance timestamp and explicit acceptance method. They are kept with the account for contract administration and evidence. We do not collect an extra copy of your IP address or user agent through the beta acceptance form.

Required account and transaction information is used to provide the corresponding function; optional invoice or contact fields are requested in context. Failure to supply necessary information can prevent that operation. Do not submit health records, SSNs, full payment-card numbers or credentials. OfraVo does not make legal or similarly significant decisions about individuals solely through automated processing.

Supabase provides database, authentication, file storage and backend functions. Vercel hosts the application and APIs. Cloudflare provides domain/network security services and private R2 backup storage. Resend provides transactional email, including authentication and owner-requested invoices. GitHub provides source hosting, CI, health checks and backup automation; backup runners temporarily process file contents before encryption.

Google/Gmail receives support messages sent to support.ofravo@gmail.com. Do not email customer databases, exports, credentials or unnecessary personal information. The support mailbox is not a business-archive upload channel. Where enabled, OpenAI processes the image supplied for AI offer scanning; submit only business menus or price lists without private customer information. AI extraction may be inaccurate and requires your review.

Stripe is reserved for separately enabled OfraVo subscription billing and can act as an independent controller for payment, fraud and compliance purposes. No paid subscription is started by accepting the free beta. OfraVo records your own customer payments but does not execute those payments or store their full card details.

We disclose information only as needed to operate the service, follow documented instructions, comply with law or establish, exercise or defend legal claims. We do not sell your customer database or use it for targeted advertising. The Data Processing Agreement describes subprocessor authorization and changes.

The primary Supabase database is in Frankfurt and the external R2 backup bucket uses EU jurisdiction. This does not mean all processing occurs in the EEA: application, email, support, AI and CI providers may process information elsewhere, including the United States.

Where a restricted transfer occurs, applicable contractual safeguards, such as EU Standard Contractual Clauses, or another valid transfer mechanism and necessary supplementary measures must cover it. We provide information about applicable safeguards on request, subject to protecting confidential and security-sensitive information. This notice does not claim that EU storage alone removes international-transfer obligations.

Measures include authenticated access, tenant isolation, restricted privileged operations, private invoice storage, encrypted transport, encrypted external backups, operator access controls and audit/incident procedures. No system can guarantee absolute security or uninterrupted availability. Operational logs are restricted and used for investigation and security; they must not deliberately contain passwords, private keys or full customer exports.

Necessary authentication storage supports sign-in and security. Any optional tracking requiring consent must be handled separately. Your device and downloaded archives are under your control; protect them and your recovery credentials.

Business records are kept to deliver the service and follow documented instructions. The acknowledged retrieval period is 180 days from the effective end of access; the account-data page shows the deadline. Previously expired accounts receive the full period from acknowledgment. No acknowledgment means no retrospective countdown under this policy. At the deadline the account enters operator deletion review.

A valid earlier deletion request is reviewed without renewal and is not held solely to finish the grace period. Source records, uploaded files, private PDFs, temporary exports and access are addressed separately. Soft deletion, voiding an entry or deleting an authentication identity alone is not proof of complete erasure.

Prepared exports are available for 24 hours and normally cleaned within a further 24 hours. External R2 file backups have a 30-day lifecycle for backup runs; provider cleanup can take additional time. Managed database and email-provider backup copies follow their applicable schedules. Isolated copies are excluded from ordinary use and deletion instructions must be replayed before restored access resumes. We do not promise that every provider copy disappears on the same day.

A minimal encrypted erasure journal is retained separately for as long as needed to prevent deleted information from returning through still-restorable copies and to document instructions. It is not another copy of the customer database. Narrow legal holds, our own accounting obligations and necessary contract or claims evidence can justify restricted retention for the applicable period; they do not justify keeping an entire business database indefinitely. Records and exceptions are reviewed for continuing necessity.

Sign in on the homepage or visit /account-export to retrieve held business records during access and the acknowledged retrieval period without renewing. A business archive is not automatically a complete response to every individual privacy request. Contact support for access problems or a verified request outside the available interface.

Where applicable, you may request access, correction, erasure, restriction and portability, or object to processing; withdraw separately given consent; and complain to a competent authority. Customers should generally direct requests about business-controlled records to that business, with our assistance where required. We verify identity proportionately and explain applicable exceptions.

Contact support.ofravo@gmail.com or the postal address above. You may complain to the President of the Polish Personal Data Protection Office at https://uodo.gov.pl/ or another competent authority. No subscription or sign-in is required to contact us.