Privacy
Privacy Policy
Last updated 18 August 2026
Privacy, without the mystery. This Privacy Policy explains what information WIZUP collects, why it is used, who may receive it, and the choices available to you.
What we collect
Account, workspace, generated, support, transaction, and technical data.
Why we use it
To provide, secure, save, generate, support, and improve requested Services.
Who receives it
Hosting, database, AI, research, payment, and support providers relevant to the features you use.
Your choices
Access, correction, deletion, objection, portability, and consent requests.
1. Scope
This Privacy Policy applies to the WIZUP website, public product pages, account and workspace experiences, creator partnership enquiry forms, support communications, and related services that link to it. WIZUP is an AI-native product studio that helps people explore opportunities, shape strategies, create digital-product material, and prepare product and sales experiences.
WIZUP is operated publicly as VIBEJAM DIGITAL, a registered business name in Kenya (business number BN-ZWSAMKE7). Its registered principal place of business is Sohail Regency, Rhapta Road, Westlands, Nairobi, Kenya; postal address: P.O. Box 62986-00800, Westlands, Kenya. This Policy explains the providers, safeguards, and transfer limitations that apply to the Services.
2. Operator and contact
WIZUP is the product name, operated publicly as VIBEJAM DIGITAL, a registered business name in Kenya (business number BN-ZWSAMKE7). Registered principal place of business: Sohail Regency, Rhapta Road, Westlands, Nairobi, Kenya. Postal address: P.O. Box 62986-00800, Westlands, Kenya.
For privacy questions, data-rights requests, security concerns, support, and rights complaints, email wizuplive@gmail.com. Put “Privacy request” or “Rights complaint” in the subject line and describe the request clearly. We may need to verify identity before disclosing or changing personal data.
3. Information we receive
Depending on the features you use, WIZUP may receive or create the following categories of information:
- Account data: email address, authentication state, profile details, and onboarding preferences.
- Workspace data: project names, ideas, research inputs, prompts, instructions, generated drafts, product plans, sales assets, storefront data, workflow state, and saved work.
- Uploaded and generated material: files, manuscript sections, images, covers, private product artifacts, and related metadata where the feature is enabled.
- Enquiry and support data: creator partnership submissions, waitlist responses, PMF validation responses, support messages, and contact details supplied with them.
- Transaction data: payment provider, amount, currency, status, provider references, order or invoice identifiers, webhook events, and delivery or entitlement state. Payment processors may collect payment credentials directly; WIZUP should not be understood to store full card numbers unless separately confirmed.
- Technical data: IP address, browser and device information, timestamps, request and error information, authentication cookies, security events, and server logs where generated by the hosting or authentication stack.
- Browser storage: WIZUP uses sessionStorage/localStorage for onboarding, workflow, and preview state and a cookie for a sidebar preference. These are not advertising cookies.
4. Sources of information
Information can come directly from you, from your browser or device, from authentication and hosting providers, from payment providers, from authorised team members, and—where the feature is actually enabled—from lawful public sources used for research or creator/product opportunity analysis.
5. Why information is used
WIZUP uses information to:
- providing, authenticating, saving, securing, and supporting the Services;
- processing prompts and relevant workspace context to generate requested outputs;
- running research and opportunity-analysis workflows and storing source references;
- operating creator partnership enquiries and responding to support or rights requests;
- processing payments, reconciling provider events, managing entitlements, and preventing fraud;
- monitoring reliability, diagnosing errors, protecting the platform, and complying with law;
- evaluating product demand through the separate PMF validation flow when a person chooses to submit a response.
6. Lawful bases and choices
Where a data-protection law requires a lawful basis, the basis depends on the processing. Contract is generally relevant to account operation, saved work, requested generation, and paid-service delivery. Legal obligation may apply to records and disclosures required by law. Consent may be used where the product asks for it and a law requires it. Legitimate interests may support security, fraud prevention, service reliability, and limited product improvement where those interests are balanced against people’s rights.
You can withdraw consent where consent is the basis, but withdrawal does not undo processing already carried out lawfully. You may also object to processing based on legitimate interests, subject to the applicable legal test.
7. AI and research processing
WIZUP uses Google Vertex/Gemini and Tavily for certain AI and research features. A prompt, instruction, project context, or uploaded material may be sent to those providers when needed to deliver the requested feature. Google states that customer data is not used to train or fine-tune models without permission or instruction, but provider logging, abuse monitoring, caching, grounding, and regional settings can still affect retention; WIZUP does not promise zero retention.
Where WIZUP analyses limited lawful public information for research or creator/product opportunity analysis, public availability does not create permission to use a person’s identity commercially. Research does not imply endorsement, sponsorship, authorship, partnership, affiliation, or approval. A person may contact WIZUP to ask questions or object where applicable.
8. Model training and generated outputs
WIZUP does not use customer private project content to train a general-purpose WIZUP model. Third-party provider policies and settings are separate. Google states that customer data is not used to train or fine-tune models without permission or instruction. Provider abuse-monitoring logs, caching, feature-specific retention, and feature-specific settings may still apply, so this Policy does not promise universal zero retention or identical treatment across providers.
Generated content is returned to the user’s workspace where the feature saves it. AI output can be inaccurate, incomplete, outdated, similar to other output, or unsuitable for a particular purpose. Human review is required before public, commercial, or consequential use.
11. International transfers
WIZUP may use Vercel, Supabase, Google Cloud/Vertex, Tavily, Paystack, NOWPayments, and an email provider in jurisdictions outside Kenya. Processing locations and subprocessors may vary by provider and feature. WIZUP will use an applicable safeguard—such as an adequacy decision, standard contractual clauses, UK transfer addendum/IDTA, or another legally available mechanism—and will not treat “global processing” alone as a transfer safeguard.
12. Retention
WIZUP retains information only for as long as reasonably necessary for the purpose collected, legal obligations, dispute resolution, security, and backups. Unless a longer period is required by law or an active dispute or security incident, WIZUP generally retains account/profile data while active and up to 90 days after verified closure; project and generated content until user deletion or 30 days after closure; billing/tax records for the period required by payment, accounting, tax, and dispute rules; security, error, and webhook logs up to 180 days; support, creator, and rights correspondence up to 24 months after resolution; and backups until the ordinary backup cycle overwrites them. Provider and statutory retention can extend these periods.
- account/profile data: while the account is active and up to 90 days after verified closure, unless security or legal records require longer;
- project and generated content: until the user deletes it or up to 30 days after verified account closure, subject to backups and legal/security needs;
- billing and tax records: for the period required by payment, accounting, tax, and dispute rules;
- security, error, and webhook logs: ordinarily up to 180 days, subject to incident investigation or legal preservation;
- support, creator enquiries, and rights complaints: ordinarily up to 24 months after resolution, or longer where needed for a dispute or legal record;
- backups: until the ordinary backup cycle overwrites them, subject to security and legal constraints.
13. Security
WIZUP uses authenticated access, ownership controls, private artifact access, signed URLs for private artifacts, webhook signature checks, and separated secrets. These are safeguards, not guarantees. No system can promise that unauthorized access, loss, or interruption is impossible.
14. Privacy rights
Send requests to wizuplive@gmail.com. Depending on the law that applies, a person may ask for access, correction, deletion, restriction, portability, objection, information about sharing, or withdrawal of consent. California residents may also have rights to know, delete, correct, limit sensitive personal information, opt out of sale/sharing where applicable, and avoid discrimination for exercising rights. Kenya, EEA, UK, Brazil, Australia, Canada, and other jurisdictions may provide additional or different rights.
Include the account email, the request type, and enough context for us to locate the information. WIZUP may request reasonable identity verification. Account deletion is available through a verified email request; deletion is not an instant universal erasure because payment, security, legal, backup, and third-party provider records may need to be retained.
15. Automated decision-making
WIZUP generates recommendations, drafts, scores, and other decision-support material. WIZUP does not currently make solely automated decisions producing legal or similarly significant effects about a person. Users remain responsible for decisions and review. If that changes, WIZUP will update this Policy and provide the rights and information required by applicable law.
16. Children
WIZUP is designed for adults, creators, operators, and business users and is not directed to children. You must be at least 18 to use the Services. If WIZUP learns that it collected information from a child where consent or another safeguard was required, contact us so we can investigate and take appropriate action.
18. Complaints and changes
Contact wizuplive@gmail.com first. Depending on where you live, you may also complain to a competent supervisory authority, including the relevant data-protection authority in the EEA/UK, Kenya’s Office of the Data Protection Commissioner, California’s privacy regulator, Brazil’s ANPD, Australia’s OAIC, or Canada’s privacy regulator. The correct authority depends on the person, operator, and processing.
WIZUP may update this policy when the Services, providers, law, or data practices change. Material changes should be communicated through a legally appropriate notice or acceptance flow rather than silently treated as accepted everywhere.