HomeAboutBlogContactHelp Center
Get Started
yenzi
yenzi

Yenzi is a new social app for personal and professional connections. Find your buddy, share your story, and grow together.

CareersAboutBlogContactHelp CenterTerms of Service (draft)Privacy Policy (draft)

Copyright © 2026 Yenzi. All rights reserved.

Subscribe to our Newsletter

Read our draft Privacy Policy and Terms of Service. Awaiting approval.

Terms of ServicePrivacy Policy

Yenzi Privacy Policy

Draft: awaiting approval

Draft for review. Awaiting approval. Some details are still awaiting confirmation. Proposed features described here may not yet be available.

Version 1.0 - draft · Prepared 5 October 2026

Contents
1. About Yenzi and this policy2. Information we collect3. How and why we use information4. Who can see your profile, posts and communities5. Portfolios, CVs, pitch videos and references6. Applications and information received by employers7. Recommendations, search, AI and analytics8. Advertising and how we earn revenue9. Who receives information10. Cookies, device storage and permissions11. Communications and telephone numbers12. How long we keep information13. Deleting information or closing your account14. Age eligibility and safeguards for young people15. Company identity and verification16. Your rights and choices17. International processing18. Security19. Changes and contact
Internal draft - not ready for publication. Prepared 5 October 2026. This is the proposed policy standard, not a statement that all described safeguards and controls are already implemented. Resolve every [CONFIRM: ...] field and complete the applicable release gates in policy-implementation-requirements.md before publication. Proposed choices include contextual advertising first, private professional files, and additional safeguards for 16–17-year-olds. Features described as conditional must remain disabled until their stated protections are ready. Remove this internal note only after review and approval.

Effective date: [CONFIRM: publication/effective date] Version: 1.0 - draft Controller: [CONFIRM: exact registered legal entity], operating as Yenzi App Registered address: [CONFIRM: address, Ghana] Privacy contact: [CONFIRM: monitored privacy email] Account-deletion page: [CONFIRM: public URL]

1. About Yenzi and this policy

Yenzi is a social platform for professional conversation, connections, communities, and sharing professional work. This policy explains how we handle personal information when you use our mobile app, websites, and related services, or contact us.

The controller named above is responsible for deciding how Yenzi uses personal information. A company or recruiter that receives information from you for its own recruitment or business purposes may separately be responsible for that information. Section 6 explains this distinction.

We do not sell your personal information. We earn revenue from services and advertising without giving advertisers or recruiters unrestricted access to your personal information. Payment for a company plan, advertisement, or recruiting tool does not give access to private files or make a company verified.

This policy describes the features available to you. Before introducing a feature that materially changes how we use personal information, we provide an appropriate notice and obtain any required permission.

2. Information we collect

Information you provide

Depending on the features you use, we collect:

  • Account details: your name, email address, username, password credentials, profile image, date of birth or age-eligibility information, and telephone number if requested or provided. We explain at collection which details are required and why.
  • Profile details: your biography, professional interests, website, location you enter, and visibility preferences.
  • Content and activity: posts, replies, uploaded images, video and audio, projects, reactions, reposts, bookmarks, follows, connection requests, and community participation.
  • Professional materials: CVs, pitch videos, skills, achievements, work history, project collaborators, reference details, and linked professional or social accounts.
  • Company and verification details: company name, website, industry, authorised representatives, claimed employment, and evidence submitted to support a company or account claim.
  • Support and safety details: questions, correspondence, reports, appeals, and information you provide when requesting help or exercising a privacy right.
  • Commercial details, where paid features are offered: selected services, billing contact details, purchases, payment confirmations, and transaction records. We explain the payment provider and payment-data handling when you use those features.

Please share another person's reference or contact details only with appropriate permission and for an appropriate purpose. Avoid uploading personal information that is unnecessary for the feature you are using.

Information generated when you use Yenzi

We collect technical information such as IP address, browser or app details, device/platform information, session identifiers, timestamps, and security or error records. Authentication records can include your IP address and user agent.

We record interactions such as content impressions and views, engagement, the part of Yenzi where an interaction happened, and activity used to provide search, recommendations, and content analytics. Some records are linked to your account; others contain content identifiers or aggregate counts. An identifier or aggregated presentation does not necessarily make the underlying information anonymous.

For notifications, we may store a device delivery token, notification preferences, timezone, and delivery status.

Yenzi uses cookies and device storage as explained in section 10. The location you type into a profile is different from device location. If a feature requests access to device location, we explain its purpose and request the required permission before collection.

Information from other people and connected services

Other people may identify you in posts, projects, references, connection requests, employment claims, or safety reports.

If you sign in through Google or LinkedIn, we receive information allowed by the permissions you authorise, such as account identifiers, name, email address, and profile information. We maintain the account-linking and authentication records needed for that connection. These providers also handle information under their own policies.

We may check relevant public company registers and official business sources when reviewing an organisation's identity or a representative's authority. This does not permit unrestricted collection of information about individual users.

3. How and why we use information

PurposeExamples
Provide your account and requested featuresAuthentication, profiles, posting, connections, communities, portfolio access and account management
Help you discover relevant work and conversationSearch, selected interests, recommendations and content ordering
Enable professional sharingAccess requests, authorised CV/video sharing and company relationships
Provide useful reportingAggregate post/reply analytics and appropriate campaign reporting
Communicate with youVerification, security messages, requested notifications and support
Protect users and organisationsAbuse reports, fraud prevention, impersonation review, verification, access control and recovery
Operate and improve YenziReliability, error investigation, performance and service measurement
Provide advertising and paid featuresLabelled sponsored placements, permitted measurement, billing and optional commercial services
Meet applicable obligationsResponding to valid legal requests and handling necessary legal records

Where a legal basis is required, we use the basis applicable to the particular purpose. Depending on applicable law, this may include your consent, providing a service or performing an agreement you requested, a legal obligation, or a permitted legitimate interest after considering your rights and reasonable expectations. We do not rely on a basis that is unavailable for the particular information or purpose.

We request separate consent for processing that requires it, including relevant direct marketing. You can withdraw consent as explained below. Using Yenzi does not serve as blanket consent to every optional use of information.

4. Who can see your profile, posts and communities

Ordinary social posts and selected profile information are intended for public conversation. Public information may be visible to members, visitors, people who receive a shared link, and search engines where indexing is enabled or otherwise applicable to the public content.

You can control supported profile fields and whether your profile is offered for search-engine indexing. Turning off indexing does not make a publicly accessible profile private. Search engines may take time to update previous results.

Open-hub content is available to its permitted public audience. Restricted-hub posts and their attached media are available only to authorised members and staff who need access for defined support, safety or legal purposes. Membership and permission changes govern future access.

Some social actions, including replies, reposts, follows and company affiliations, may be visible to others. Other information, such as private files and bookmarks, is handled according to its feature-specific access rules. We explain the audience at the relevant sharing point.

People who receive information can copy, screenshot or share it outside Yenzi. Changing visibility or deleting content stops the access Yenzi controls, subject to the deletion process in section 13, but cannot recall independent copies already made by others.

Users aged 16–17 receive the additional protections in section 14.

5. Portfolios, CVs, pitch videos and references

Your portfolio starts private. You choose whether to publish eligible professional information or grant access to particular people. A portfolio labelled member-visible is available to signed-in Yenzi users; an internet-public option, if offered, is clearly identified separately.

Publishing a professional summary does not automatically publish your CV, private pitch video, reference contact details, or account telephone number. Private files require the permission applicable to that resource. Where downloading is offered, we distinguish it from access through Yenzi.

An access request identifies the requester, relevant organisation, requested information, purpose and duration. You can approve, decline, limit or revoke a grant. Access is granted to a named individual unless you expressly choose a stated hiring team or organisation scope. Grants expire after the period shown to you; the ordinary default is 30 days.

You can review active grants in your access controls. Removing a grant stops future access through Yenzi. A previously issued short-lived media link may remain usable until it expires, normally for up to [CONFIRM: maximum lifetime for every private media provider]. Files already downloaded are outside Yenzi's ability to recall.

Reference contact information remains private unless shared for an authorised purpose. Making your portfolio member-visible or internet-public does not automatically reveal reference contacts.

We require companies using Yenzi's professional-sharing tools to respect the stated purpose, protect candidate information, and avoid resale or unrelated marketing. We can restrict access where these rules are breached.

6. Applications and information received by employers

If you choose to apply for an opportunity or share materials with an employer, we send the information you select to the recipients identified in that workflow. A recruiting subscription alone does not authorise access to your private materials.

Where a submitted application is retained as a versioned record, we explain that at submission. Changing your current CV or profile does not automatically change a previously submitted application.

An employer may independently retain information you submitted for its recruitment and legal purposes. Its privacy notice and applicable law govern that separate processing. You can contact that employer about its records; contact Yenzi about information and access controlled by Yenzi. Closing your Yenzi account does not automatically erase independently retained employer records.

Recruiter discovery is a separate choice from social-profile publication. We do not treat a public post as permission to distribute a private CV or make your account available for unrestricted recruiting contact.

7. Recommendations, search, AI and analytics

Recommendations can use interests you select, followed topics and accounts, social relationships, content freshness and popularity, and interaction-based estimates of topic interests or affinity for authors. These estimates help order content and are not statements of fact about your character or employment suitability.

You can choose supported feed modes and manage recommendation preferences. Controls explain whether they change displayed results, reset learned preferences, or stop optional learning. A change of feed mode does not by itself erase activity records.

We use Cloudflare Workers AI to create representations of post text and search queries for search and topic classification. Search representations are stored in Cloudflare Vectorize where needed. Those services receive the information necessary for the operation. We do not authorise use of your private CVs, reference contacts or private communications for advertising profiles or general-purpose AI model training.

Authors receive aggregate content analytics, such as impressions, views and engagement. We do not provide an identified list of viewers through these analytics. Underlying operational records can still contain account, content or author identifiers and have the retention periods in section 12.

We do not provide employers with automated scores of a user's worth or suitability inferred from their face, voice, private activity or psychological characteristics.

8. Advertising and how we earn revenue

Yenzi may offer professional subscriptions, company tools, recruiting services, paid placements and advertising. The relevant notice explains information handling when you use a paid feature.

Advertisements and paid promotion are clearly labelled. Our initial advertising model uses general sponsorship or suitable page/topic context. We do not use private communities, private portfolio files, reference contacts, authentication telephone numbers, private communications, or sensitive personal characteristics to select advertisements.

If adult personalised advertising is introduced, it is off until you give the required informed permission. The control explains which eligible information would be used. You can turn it off without losing basic account access or privacy rights. We stop using your profile for that advertising and remove ad-only profile information under the disclosed retention schedule. You may continue to see general or contextual ads.

We do not use behavioural advertising for users under 18. We do not sell personal information or provide advertisers with identifiable viewer lists, private professional files, or reference contact lists. Campaign reports use aggregation and safeguards intended to prevent identification of individuals.

If you follow an advertiser's link or choose to submit information to an advertiser, that recipient handles the resulting visit or submission under its own notice. We explain any Yenzi-controlled submission before you send it. We do not silently attach your account identity to an advertiser's destination URL.

We do not introduce tracking across other companies' apps or websites without a specific notice, required legal consent and applicable platform permissions.

9. Who receives information

We disclose information only for defined purposes, including:

  • Your chosen audiences and recipients: people who can see your content and professional materials under sections 4–6.
  • Organisation administrators: the information necessary to administer a hub, verify an employment claim, handle an authorised application or manage organisation access. Company administration does not provide access to your personal account credentials or unrelated private activity.
  • Service providers: hosting, storage, media delivery, authentication integrations, notifications, operational logging and any separately disclosed payment or verification services.
  • Safety and legal recipients: where necessary and permitted to address abuse, enforce appropriate rules, protect rights or comply with a valid legal obligation. We assess the authority and scope of requests and disclose only appropriate information.
  • Business successors: if Yenzi undergoes a merger, acquisition or similar change, information may transfer subject to applicable law, appropriate safeguards and notice. This is not permission to disregard your existing choices or sell data as an advertising dataset.

Our service integrations include Cloudflare infrastructure, database, storage, search/AI, analytics and email services; Google and LinkedIn sign-in; notification delivery through Firebase Cloud Messaging and applicable operating-system providers; GIPHY media features; and VedaTrace operational logging, where enabled. Relevant integrations can receive technical data when you use them. A connected provider may also act independently under its own notice, for example when you sign in through its account or visit its media service.

We assess providers and require appropriate contractual and security safeguards for services handling information on our behalf. We explain material changes to recipients and purposes. The current provider information is available at [CONFIRM: public provider/cookie information URL, including enabled services, purposes, regions and privacy links].

10. Cookies, device storage and permissions

Yenzi uses essential cookies and local storage to authenticate accounts, maintain sessions, remember appropriate preferences and protect the service. The mobile app can store authentication state and cached content using secure device storage and local databases.

We explain optional storage or tracking separately and obtain required permission before it is used. Browser controls can restrict cookies, although doing so may affect sign-in and other essential functions. Mobile permissions are managed through the app and your operating system.

We request microphone, camera, media-library or other device access when it is needed for a feature you choose. Denying an optional permission does not prevent use of unrelated features.

Logging out clears account-scoped local state controlled by Yenzi on that device. Files you exported or saved elsewhere may remain. If a device is offline, Yenzi cannot remotely guarantee immediate deletion of every previously downloaded copy.

11. Communications and telephone numbers

We send verification, recovery, security and other essential service messages as needed. Social notifications can include activity such as replies, connection requests and relevant organisation events. Notification controls and operating-system settings let you manage supported delivery choices.

Notification previews can appear on a lock screen. You can choose generic previews where supported to reduce disclosure of names, excerpts or professional context.

Telephone numbers supplied for authentication or recovery remain private and are used for those functions and necessary abuse prevention. A number must be verified before it becomes a trusted recovery method. We explain any required number and the consequences of declining it when you set up the feature.

Marketing email and SMS require the permission applicable to the communication. We provide separate channel preferences and an effective unsubscribe method. Withdrawing marketing permission does not stop necessary account-security messages. Essential messages are not used to bypass your marketing choices.

12. How long we keep information

We keep information only for a stated purpose and appropriate period. The applicable schedule distinguishes live service records, provider records, backups and narrowly justified legal records.

InformationRetention rule
Account, profile, content and professional materialsWhile needed for your active account or chosen sharing, until you delete the item/account, subject to the deletion periods and exceptions below
Authentication sessionsNormally expire after seven days; expired or revoked records are removed through scheduled cleanup. Cookie-cache and physical cleanup limits: [CONFIRM: verified periods]
Email OTP verificationCodes normally expire after ten minutes; other verification types follow their own expiry. Expired-record cleanup: [CONFIRM: maximum cleanup delay]
Identified post/reply view deduplicationEligible for removal after 30 days, with scheduled cleanup. [CONFIRM: maximum cleanup delay and account-deletion behaviour]
Portfolio project-view deduplicationEligible for removal after 30 days, with scheduled cleanup. [CONFIRM: maximum cleanup delay]
Read notificationsEligible for removal once their creation date is more than 90 days old; unread notifications remain while needed for delivery or account operation. [CONFIRM: unread-record maximum/review rule and cleanup delay]
Inactive or disabled push-device recordsEligible for removal after 180 days of inactivity or disablement. [CONFIRM: cleanup delay]
Portfolio grants and request historyOrdinary grants expire after 30 days; access expiry is separate from deletion of request records. Request-history retention: [CONFIRM: period]
Learned interests and author affinity[CONFIRM: physical deletion/inactivity period and reset handling]; score decay alone does not delete the record
Aggregate metrics and identifiable telemetryRetained for the stated reporting purpose; aggregate presentation does not necessarily remove author/content identifiers. Analytics Engine currently retains submitted records for three months; [CONFIRM: deletion treatment and retained metric lifecycle]
Company-verification evidence[CONFIRM: raw-evidence period, verification-result period and dispute retention]
Support, moderation and security logs[CONFIRM: separate periods by purpose, including provider-held logs]
Purchases and accounting records, where applicable[CONFIRM: applicable statutory periods and payment-provider handling]
Ad measurement, consent and any ad-only profiles[CONFIRM: separate periods, withdrawal cleanup and necessary billing/security exceptions before enabling]
Backup and recovery copies[CONFIRM: maximum backup/recovery period and restore deletion safeguards]

Where a specific legal obligation or necessary dispute requires retention, we limit the information, restrict access, record the reason and review or end retention when the reason expires. Such retention does not permit continued advertising, recruiting or unrelated use.

Information described as anonymous is retained only where it has been effectively de-identified and cannot reasonably be linked back to you. We do not treat hashing an identifier, removing a name, or displaying a total as sufficient by itself.

13. Deleting information or closing your account

You can remove supported content and request account deletion through account settings or the external deletion page above. Contact the privacy address if you cannot access your account. We use proportionate verification to protect you against fraudulent requests.

Before deletion, you can request a copy of your information. Export is optional and does not need to delay your deletion request. If you administer a company or hub, we provide transfer, closure or assisted resolution so that ownership does not indefinitely prevent you from leaving.

After confirming account deletion, we disable future account access, withdraw grants, stop new optional processing and begin removal of your profile, your content and associated personal information from the systems we control. We also initiate required provider and cache cleanup and prevent delayed jobs from recreating deleted information.

Active-system completion period: [CONFIRM: tested maximum or accurately described target and escalation process]. We send confirmation when the stated active-system process is complete, explaining any remaining lawful retention or backup expiry.

Backup copies are handled within the period in section 12 and are not restored into ordinary use without reapplying deletion. Separate, limited records may remain where required for legal compliance, security, disputes or respecting your request not to receive marketing, under the defined retention schedule.

Others may retain their own copies or records, including an employer's submitted application. Search-engine caches can take time to refresh. Organisation pages that other authorised people continue to administer can remain after your account closes, with your personal access and associated records removed as appropriate.

We explain how deletion affects dependent replies, quotes, applications and shared records in the relevant deletion notice. We remove or appropriately de-identify retained context rather than leaving unnecessary identifiable orphan records.

14. Age eligibility and safeguards for young people

Yenzi's proposed minimum age is 16. Access for 16–17-year-olds is available only where the applicable requirements for their information and participation have been met, including parent or guardian authorisation where required. A product age threshold does not replace local legal requirements.

We apply additional protections to accounts identified as belonging to users under 18: stronger privacy defaults, search indexing off by default, restrictions on unsolicited contact and professional-data disclosure, and no behavioural advertising. We explain publication and sharing choices in age-appropriate language.

We use proportionate age-eligibility checks and request only the information needed for those checks. Age-assurance information is restricted and is not used for advertising.

If you believe a child under the permitted age has an account, or that a young person's information is exposed or misused, contact [CONFIRM: safety/privacy contact]. We investigate, restrict access where appropriate, and remove or otherwise handle information as required by law.

15. Company identity and verification

We use company information, official-source checks and appropriate evidence to assess an organisation's identity and a representative's authority. A person creating a page does not thereby prove authority to represent the company.

Verification labels explain the claim checked. Company identity, page-administration authority, employment association and subscription status are separate matters. Verification does not guarantee every statement or opportunity offered by a company.

Verification documents are accessible only to authorised reviewers and are retained under section 12. We do not expose personal identity documents on company pages. Reports of impersonation, takeover or false affiliation can be submitted through [CONFIRM: report/claim URL or supported contact].

16. Your rights and choices

Depending on applicable law, you may have rights to be informed about processing; access and correct information; request deletion; withdraw consent; object to particular processing or direct marketing; restrict processing; obtain a portable copy; or challenge qualifying automated decisions. We explain the rights applicable to your circumstances rather than assuming every right has identical scope worldwide.

Use available account controls or contact the privacy address above. We acknowledge requests, verify identity only as necessary, and respond within the applicable legal period. Where a restriction or exception applies, we explain the reason and available review or complaint options. We protect other people's information when providing access.

Basic privacy requests, access controls, account deletion and safety reporting do not require a paid subscription. Any charge or refusal permitted by law is explained and assessed individually.

You may complain to Ghana's Data Protection Commission or another competent supervisory authority. You do not have to contact Yenzi first to exercise a regulator complaint right.

17. International processing

Yenzi operates from Ghana and uses service providers whose infrastructure or authorised personnel may process information in other countries. The relevant countries and services are listed at [CONFIRM: provider/transfer notice URL and actual locations]. We do not promise that all information stays in Ghana.

We assess international processing and use the legal and contractual safeguards required for the relevant transfer, including appropriate provider agreements and other mechanisms where applicable. Contact us for information about safeguards and how to obtain relevant details.

Country or regional supplements may provide additional rights, contacts and safeguards. They apply with this policy where relevant, and mandatory local protections are not reduced by this policy.

18. Security

We use access controls, appropriate authentication, encrypted connections, restricted staff access, security monitoring and safeguards for private resources. We assess providers handling information on our behalf and maintain procedures for investigating and responding to security incidents.

Private professional files require authorised access. Staff access is limited to appropriate operational, support, safety and legal purposes. No internet service can guarantee absolute security. If an incident requires notice to you or an authority, we provide that notice as required.

Please secure your account, use available stronger authentication and report suspected compromise promptly through [CONFIRM: security contact].

19. Changes and contact

We publish an effective date and version and provide appropriate notice of material changes. If a change requires new consent, we request it before the affected optional processing begins. Continued use does not replace consent where separate authorisation is required.

Previous versions are available at [CONFIRM: policy archive URL].

For questions, privacy requests or complaints, contact:

[CONFIRM: registered legal entity], operating as Yenzi App Address: [CONFIRM: registered/contact address] Privacy: [CONFIRM: monitored privacy email] Safety/security: [CONFIRM: supported reporting channels]