Privacy Policy
Version 1.2 — effective 17 September 2026.
This Privacy Policy explains how Kinglify collects, uses, shares and protects personal data, in line with the Nigeria Data Protection Act 2023 (NDPA).
1. Who we are
Kinglify is operated by AUREVA INTERNATIONAL LTD. For personal data you provide directly to Kinglify, we are the data controller. For data you provide to an organisation using Kinglify, that organisation is the controller and Kinglify is the processor.
2. Data we collect
- Account data: name, email, phone, role, organisation.
- Usage data: activity within the Platform, device and log data.
- Payment data: processed by our payment providers; we store references and card last-4/brand, never full card numbers.
- Consent records: your acceptances of our policies with timestamp, IP and user agent.
3. How we use data
To provide and secure the Platform, process payments, communicate service messages, meet legal obligations, and — only with your consent — send marketing. We also use data we already hold to prevent and detect fraud and abuse (for example, manipulation of referral commissions or payment disputes): this analysis is reviewed by a person before any decision affecting you, and no purely automated adverse decision is made. Our lawful basis for it is legitimate interest in protecting the Platform and its users.
4. Lawful bases
We rely on contract performance, legal obligation, legitimate interests, and consent (which you may withdraw at any time).
5. Sharing
We share data with processors (hosting, payments, email) under contract, and with authorities where legally required. We do not sell personal data.
6. International transfers
Where data is processed outside Nigeria, we use appropriate safeguards consistent with the NDPA.
7. Retention
We keep personal data only as long as needed for the purposes above or as required by law (for example, financial records).
8. Your rights
Under the NDPA you may access, correct, export, restrict, object to, or request deletion of your personal data, and withdraw consent. Use the Privacy Dashboard in your account settings, or contact privacy@kinglify.com. We route deletion requests through review because some records must be retained for legal or financial reasons.
9. Cookies
See our Cookie Policy. You can manage non-essential cookies through the cookie banner.
10. Security
We use technical and organisational measures including encryption of sensitive fields and access controls.
11. Contact & complaints
privacy@kinglify.com. You may also complain to the Nigeria Data Protection Commission (NDPC).
12. YouTube API Services
Kinglify publishes its own videos to its own YouTube channel using YouTube API Services. That feature is subject to the YouTube Terms of Service, and information Google receives through it is handled under the Google Privacy Policy.
What we access. Only a Kinglify platform owner with a verified second factor can connect a channel, and only Kinglify's own channel may be connected — any other channel is refused and its authorisation withdrawn immediately. The permissions we request are youtube.upload and youtube.readonly. With them we read the connected channel's own identity — its channel ID, channel title and handle — and we use the upload permission to publish Kinglify's own videos to that channel. We do not access, collect or store the YouTube account, viewing history, subscriptions, comments or any other YouTube data of any Platform user, member, customer or visitor.
What we store. The connected channel's ID, title and handle; which permissions were granted; the date and time of the connection and of the last verification; and Google's access and refresh tokens, which are stored encrypted and are never displayed, exported, or sent anywhere except to Google.
How we use and share it. The channel identity is used to confirm that the channel about to receive a video is Kinglify's own. The tokens are used only to authenticate Kinglify's own requests to Google. This information is not sold, and it is not shared with anyone other than Google in the course of making those requests.
Deleting it, and withdrawing access. Removing the connection deletes the stored tokens immediately; the record that the channel was connected is kept as an administrative record. In addition to that procedure, the holder of the Google account can revoke Kinglify's access at any time through the Google security settings page at https://security.google.com/settings/security/permissions. Questions or complaints about these practices: privacy@kinglify.com (section 11).