Connecting African talent with Gulf opportunityQuestions? Contact Afrolink
AfrolinkGULF CAREERS Ask about app access

Home / App information

Plain-language summary

Data safety

Afrolink uses account and application details to operate a recruitment marketplace. The summary below describes the current app behavior; the publisher must enter and verify the matching answers in Play Console.

Current implementation summary
Play Console reminder. This page is not the Play Data safety form. Re-check the final production build, libraries and operator practices before submitting the in-console declaration.

Data categories

Personal infoName, email, role (job seeker, employer or operator-assigned administrator) and job-seeker location/profile details; employer company name and website.
Files and application contentResume/CV URL and cover-letter text supplied with an application; employer notes/status for that application.
App activityJobs viewed (including an internal job-view event), saved roles, application state and in-app notifications.
Financial infoPayment or transfer method/reference, amount/currency, status and entitlement dates when an available method is used. Google Play checkout is disabled in the current app; if enabled later, Google processes payment credentials and Afrolink does not collect card numbers.
Security and session dataHashed bearer-session tokens, expiry/revocation details and hashed rate-limit keys. Passwords are bcrypt-hashed.
Device identifiersThe backend supports storage of a push-notification token, but the current mobile app does not request notification permission or register a device token.

Sharing and purpose

Application details are provided to the employer for the specific role when a seeker applies. Authorized administrators can access account, job and payment/subscription records, view aggregate application counts and perform restricted application-status or moderation operations; employers can review applications for their own jobs. The app's managed hosting/database provider processes information needed to run the service. Google Play will receive purchase-verification requests only if Android checkout is enabled; that feature is currently disabled. Afrolink does not sell personal information and has no advertising SDK in the current dependency set.

Security practices

  • Passwords are stored as bcrypt hashes, not readable passwords.
  • Server-side bearer sessions are stored as SHA-256 hashes, expire and can be revoked.
  • Role and ownership checks limit access to employer, seeker and administrative workflows.
  • The public API uses HTTPS; the publisher should confirm any additional at-rest controls with the hosting provider.

Retention and deletion

Account and application records are retained while needed to run the service and for applicable legal, security and dispute purposes. The current mobile app does not yet offer in-app account deletion. The website provides a manual deletion-request form; requests require operator review and are not automatically processed by the page.

Payments and purchase tokens

Google Play checkout is disabled in the current mobile app, so the app does not currently receive a Play purchase token. If the operator enables this feature later, the server will send a purchase token to Google Play for verification and retain a hash of the token plus order/status/expiry information, not the raw token. Google Play payment methods are managed by Google. Bank-transfer records are processed only when that method is enabled. Payment or bank details should never be entered into an Afrolink support message.

Publisher checklist: reconcile this summary with production analytics, SDKs, form fields, regional legal requirements and the exact Play Console Data safety questions before public release.