Privacy Policy
Transparency about Data · This policy describes what personal data Bizowizo processes for platform, payments, media, communication, and security.
Transparency about Data
This policy describes what personal data Bizowizo processes for platform, payments, media, communication, and security.
1. Controller and contact
The controller for Bizowizo is Pitch60 Social Media Marketing Services - FZCO, IFZA Business Park, Premises No. 10742-001, Dubai, United Arab Emirates. Trade License issued by the Government of Dubai, Trade License No. 10742, Makani No. A1-3641379065.
info@bizowizo.ai is the central email address for privacy enquiries and contact with the operator.
2. Scope
This policy applies to website, web app, accounts, profiles, feeds, campaigns, wallet, payments, premium, messenger, comments, reviews, moderation, and the future advertising program. Supplementary notices may be required for a later native app or external social media presences.
3. What Data is Processed
Depending on the use, Bizowizo processes account and contact data, role and profile data, public content, media and documents, follower and interaction data, messages, moderation and security data, technical access and device data, as well as payment and ledger metadata.
Account: OpenID or later email, display name, role, language, session data, and account status.
Public Profile: Username, profile picture, banner, bio, country/location, and published activities.
Project and Content: Pitches, videos, captions, campaigns, documents, rewards, comments, and reviews.
Communication: Private messenger content, invitations, notifications, and support requests.
Finances: Stripe customer/session/event references, purchase status, Coin and ledger bookings, donations, holds, and payout status; no full card, CVC, or bank access data.
Security: IP/time/device information, abuse signals, reports, blocks, moderation, and audit data.
4. Purposes and Legal Bases
The specific legal basis depends on the purpose. Contract and pre-contractual measures support account, platform functions, Coin purchase, premium, advertising, and payout. Legal obligations particularly concern accounting, payment verification, and authority requests. Legitimate interests can support security, abuse prevention, error analysis, and basic platform operation. Consent is used for optional analysis, marketing, and other non-necessary processing.
5. Public Profiles and Content
Published profiles, pitches, campaigns, comments, and reviews are visible worldwide. They can be shared, embedded, and indexed by search engines.
Users should not include confidential or particularly sensitive data in public content. Search engines and recipients of shared links can cache public content independently.
6. Stripe, Coins, and Payouts
Stripe processes payments, payment methods, fraud prevention, identity verification, and Bizo payouts as an independent controller or processor according to the respective service. Bizowizo only receives the references and metadata necessary for status, assignment, support, accounting, and ledger.
Coin balances arise from immutable Double-Entry-Ledger bookings. Refunds and disputes become traceable through counter-bookings. Statutory financial and proof obligations may require longer retention.
7. Media, Subtitles, and Translation
Media bytes are stored in an S3-compatible storage. Metadata, ownership, status, and storage references are in the platform database. For transcription, subtitles, and translation, audio, text, and necessary context can be transmitted to integrated AI services.
Private messenger texts are only translated for the respective logged-in recipient.
8. Messenger, Notifications, and Email
Private messages are processed for delivery, read status, abuse prevention, and reports. Notifications only contain the information necessary for the event. Message contents are not transferred to public activity feeds.
A provider for confirmation and password reset emails is not yet configured. After selection, provider, region, data scope, and storage duration will be added here; until then, no email delivery may be simulated.
9. LiveKit and Live Broadcasting
LiveKit Cloud is intended as future infrastructure for live pitches and battles, but not yet activated. After activation, room, participant, connection, audio/video, and technical quality data can be processed. Beforehand, provider region, retention, recording, moderation, and third-country transfer will be added.
10. Cookies, Local Storage, and Analytics
Necessary technologies store in particular session, language, privacy decision, sound preference, and interface settings. The project-side Umami analytics script is only loaded after optional analytics consent.
Consent can be revoked at any time via "Cookie Settings" in the footer. Further details can be found in the cookie notices.
11. Recipients and Service Providers
Recipients can be, depending on the function, Manus Hosting/Auth/Database/Storage, Stripe, future email services, LiveKit, translation/transcription services, support providers, professional advisors, and authorities. Data is only transmitted to the necessary extent and on a suitable legal basis.
12. International transfers outside the UAE
Where personal data is processed outside the United Arab Emirates, Bizowizo will assess the conditions and safeguards required by applicable UAE data protection law, including Federal Decree-Law No. 45 of 2021 where applicable. Recipients, regions, legal basis and safeguards must be documented in the provider register.
13. Storage Duration
Data is only stored as long as it is needed for the respective purpose, contract, security proof, or legal obligations. Account data can be omitted after deletion; public content is removed or anonymized, provided no rights or obligations conflict.
Ledger, Stripe, invoice, audit, moderation, and dispute data can be stored longer due to statutory retention, fraud prevention, and legal defense.
14. Data-subject rights under applicable UAE law
Subject to legal conditions, individuals may request information and access, correction, deletion, restriction or cessation of processing, portability and objection to certain automated decisions. Consent may be withdrawn for the future.
Complaints may be submitted in accordance with applicable law to the UAE Data Office or another competent UAE authority.
15. Automated Rules and Profiling
Follower thresholds, campaign completeness, rankings, fraud indicators, and moderation priorities can be calculated automatically. They currently do not establish an exclusively automated decision with a similarly significant legal effect; high-risk measures are kept administratively verifiable.
Advertising may not use sensitive data for target group formation and may not play targeted advertising to minors.
16. Minors and Data Security
Until a verified age and parental consent model is in place, payment-related functions are only intended for adults. Suspicious minor accounts can be restricted.
Bizowizo uses role-based access, secure cookies, server-side validation, rate limits, signed webhooks, encrypted transmission, S3 access protection, and immutable financial journals. No system can guarantee absolute security.
17. Changes and privacy contact
This notice will be updated for new providers, functions or legal bases. Material changes will be communicated appropriately.
Privacy enquiries may be sent to info@bizowizo.ai.
18. Wizo referral data
For active Wizos who participate automatically, Bizowizo processes target-specific referral code, target, time, consent state, pseudonymous click/session/risk signals, attribution, conversions, and booked commission plus refund/dispute adjustment status. This public Wizo programme path is limited to the attribution data described above.
Persistent 30-day attribution is stored only after separate optional referral consent. Without consent the destination remains available and only a necessary short-lived session attribution remains. Later consent withdrawal does not falsify financial and audit evidence.
18. Qualified Views, Tap-Support Preference and Financial Evidence
To count a qualified view once, Bizowizo processes the pitch ID, time and visibility thresholds and an HMAC-hashed viewer key. The internal user ID is hashed for logged-in users; otherwise a necessary first-party session key is hashed. Raw IP addresses and complete device profiles are not stored in the view record.
The Tap-Support preference is stored server-side with activation status, contract version and timestamp. Each accepted tap creates financial and audit metadata for the Wizo wallet, target pitch, any Live Pitch or Battle, campaign, Coin amount, idempotency key, reward, commission and potential counter-entry. Tap Support is not processed for Wallstreet or notifications.
Stripe may process its own data for Connected Account onboarding, identity/business checks, capability status, payments, transfers, payouts, fraud prevention and reversals under its terms. Bizowizo stores only the references and metadata needed for assignment, status checks, accounting, security and reversal handling.
