Privacy Policy
How account, booking, payment and delivery information is handled.
Who is responsible
Pyvira, Germany, is the supplied operator name for this draft privacy notice. You can contact info@pyvira.com about personal information. The operator's full legal identity and business address must be confirmed in the Legal Notice before this notice is finalized.
Information involved in the service
Account information includes your name, email, account role, profile details and authentication records. Creator profiles may include a profile photo, portfolio, service rates, social links, equipment, home city, travel plans and availability.
Booking information includes requests, invitations, participants, schedules, prices, messages, uploaded attachments and delivery files, revisions, reviews and disputes. Verification submissions and support or moderation records can contain additional information you provide.
Payment records include transaction references, amounts, currencies, fees and payment or payout status. Card entry and payout verification are handled through Stripe. Do not put card numbers, bank credentials or identity documents in ordinary booking messages.
Hosting and authentication providers may process IP addresses, device or browser information, request logs and security events when you use the service.
Why information is used
Information supports account access, creator discovery, booking communications, file delivery, payment reconciliation, notifications and dispute handling. Security and moderation records help investigate misuse and protect users.
The proposed legal bases are performance of the relevant service contract, compliance with applicable obligations, legitimate interests in operating and securing the marketplace, and consent where required for optional activities. The final notice must map these bases to the operator's actual processing.
Public and shared information
Published creator profiles, portfolio content, advertised locations, availability and reviews can be visible to other visitors. Do not place private residential addresses or confidential client information in public profile fields.
Booking participants receive information needed for their collaboration. Authorized support or moderation personnel may need access to relevant records when investigating an issue. Signed delivery links are access mechanisms, not a guarantee that a recipient cannot copy a file.
Service providers and transfers
The application integrates Supabase for authentication, data and file storage; Stripe for payments and payout verification; Brevo for configured email notifications; and Google Analytics for optional visit measurement after consent. The production site is hosted on Vercel. External sign-in and linked portfolio services can involve additional providers.
The providers' roles, enabled features, processing locations and any international-transfer safeguards must be checked against the production configuration and contracts. This draft does not promise that all data stays in one country or region.
Retention and security
Retention depends on the purpose of a record, active bookings, disputes, fraud prevention and applicable accounting or legal obligations. Account removal does not necessarily require immediate deletion of every transaction record. Detailed retention periods and deletion procedures are awaiting confirmation.
The application uses authentication and access controls, but no system can guarantee absolute security. Keep your account secure and avoid sharing unnecessary sensitive information. This draft does not claim that all uploads are virus-scanned or that messages are end-to-end encrypted.
Your choices and rights
Where applicable, you may request access, correction, deletion, restriction or portability of your personal data, object to certain processing, withdraw consent, and complain to a data-protection authority. Exceptions may apply, including where records must be retained by law.
Account notification settings control available notification preferences. Send privacy requests to info@pyvira.com, including if you cannot sign in. Include enough information to identify the relevant account; do not email passwords, payment credentials or identity documents unless a secure verification process is arranged.
Updates and related policies
The Cookie Policy describes browser storage and external payment pages. This privacy notice must be reviewed when providers, data uses or public-profile features change. A final publication date will be added after review.