1. Who this Notice is for
This Notice applies when Influrs receives or maintains creator personal data from a source other than the creator, for example a permitted official platform API or attributable public editorial source. It covers internal processing as well as any public display that is separately permitted. It supplements the main Privacy Policy.
The per-intake evidence workflow for UK GDPR Article 14 is not yet complete, so broad automated creator discovery, public free-text biography output and public contact/commercial output remain disabled. Identifying YouTube API data about an unclaimed creator is also neither stored nor displayed without separate, durable consent tied to the exact channel; a legitimate-interests assessment and public availability do not replace that consent. Before any other affected collection or first disclosure is enabled, we must assess the Article 14 timing and exceptions for that intake. Where direct notice is required and we have a usable contact, it will be provided within one month of obtaining the data, at first contact, or before first disclosure, whichever is earlier. Any reliance on an Article 14(5) exception must be recorded with safeguards including this notice, a profile notice or link, data minimisation, source attribution, and accessible correction, objection and removal channels. This page does not by itself replace individual notice where it is required.
2. Controller and contact
NETSKY GROUP LTD is a private company limited by shares registered in England and Wales under company number 10677601, with its registered office at 27 Old Gloucester Street, London, United Kingdom, WC1N 3AX.
NETSKY GROUP LTD is the controller. Send a correction, objection, removal request or complaint to influrscom@gmail.com. The “How to correct or remove this profile” link on the relevant creator page opens the applicable instructions and contact route.
3. Categories of creator data
Contact and commercial details are not currently returned by the public creator directory. If this output is enabled after the provenance control is complete, it will be limited to fields a verified creator or authorised representative supplied and designated for public display. We do not intentionally publish private contact details or infer special-category traits for eligibility or high-impact decisions. Please report any sensitive or private information that appears unexpectedly.
- Name, public display name, handle, public biography, profile image, banner, stated location, country, language, website and topic/category.
- Platform, channel/account and public content identifiers; profile, channel, video and source URLs, but identifying YouTube API fields for an unclaimed creator are excluded unless the separate exact-channel consent is evidenced.
- Publicly displayed follower/subscriber and content counts, publication dates and public content metadata where the source permits it.
- For a claimed profile: email, agency name, media-kit URL, rates and visibility choices that may be supplied by the creator or authorised representative. Public output of these fields is currently disabled until field-level provenance is recorded and enforced.
- Attribution, retrieval/verification date, source and data-quality status.
- Claim, correction, opt-out and privacy-request status, requester contact and supporting evidence if you contact us.
4. Sources
Influrs does not use scraping or undocumented interfaces to obtain YouTube data or content. OAuth may be used to verify control or provide a private connected feature, but YouTube Authorized Data obtained through OAuth is visible only to the authorising user or agents expressly approved by that user and is not a public-directory source. A permitted creator profile should show or link to its source platform so you can understand the context and verify it.
- Documented official platform APIs only where their rules and the required consent permit the particular use. YouTube API Services are not a source of unclaimed identifying public-directory data without separate consent tied to the exact channel.
- The creator, channel owner or an authorised representative.
- Licensed suppliers that contractually identify provenance and permitted use.
- Manual, attributable editorial research from information the creator or publisher made public.
5. Purposes and lawful basis
We use creator data to operate an attributed creator-discovery and editorial service, help users find original public sources, maintain accurate profiles, prevent fraudulent claims, respond to rights requests and secure the Service.
For a permitted non-YouTube unclaimed public profile, our proposed basis is legitimate interests under UK GDPR Article 6(1)(f): our interest and users' interest in finding accurate, limited, attributed information about creators who publish publicly. We balance this against the creator's reasonable expectations, the public/professional context, data sensitivity, accuracy, impact, visibility controls and easy correction, objection and removal channels.
Public availability alone is not the legal basis. We do not rely on legitimate interests where the impact overrides those interests, and legitimate interests do not satisfy YouTube's separate consent requirement for identifying API data. Claimed-account and requested connection processing may instead be necessary for a contract or depend on consent for a specific use; legal claims and regulatory duties may rely on legal obligation.
6. Use and recipients
Profile visitors and registered users may see only fields from permitted non-YouTube sources or fields supplied or separately approved for public display by the verified creator. Unclaimed identifying YouTube API fields, public free-text biography and contact/commercial output remain disabled as described above. Workspace members may add their own private notes and tags, which are visible only within their authorised workspace.
Necessary data may also be processed by hosting, database, storage, email, monitoring and security suppliers; Google/YouTube for a permitted private connection, official API operation or external source link, but not an embedded player in the current release; OpenAI only for a specifically authorised AI request; and advisers, regulators, courts or law enforcement where lawful and proportionate.
We do not sell creator personal data or disclose OAuth tokens. The automated authorised-captions workflow is unavailable; while it is blocked, no new authorised caption retrieval, article staging, disclosure to another person or OpenAI processing begins.
7. Accuracy and retention
Legacy identifying YouTube API data without the required exact-channel consent is retained only in restricted quarantine, is not refreshed or displayed, and is deleted when the pending retention deadline of no more than 30 days expires. A permitted non-authorised YouTube API record is refreshed or deleted within 30 days; if it cannot be refreshed, it is removed. Connected-account data follows the 7-day and 30-day deletion rules described in the main Privacy Policy and remains private to the authorising user or expressly approved agents.
Other profile data is retained only while the profile remains relevant, the source and attribution remain valid, and the creator's rights do not require correction, restriction or deletion. Existing contact, agency, media-kit, rate, visibility and free-text biography records are not made public while their release gates are closed. Creator-supplied fields remain until the creator or authorised representative changes them, the claim or profile ends, a valid request requires action, or law requires retention. We review data when it is updated, reported or claimed and do not keep a rejected claim's evidence longer than needed for fraud prevention, complaint accountability or legal claims.
8. YouTube-specific information
YouTube data can include channel/video IDs, titles, descriptions, thumbnails, publication metadata, public statistics and source URLs. Legacy records without the separate exact-channel consent described above remain only in restricted quarantine and are not displayed as identifying data for an unclaimed creator. Permitted YouTube content remains attributed and links to the original channel or video. Influrs is not endorsed by YouTube.
Google processes data under the Google Privacy Policy. Use of relevant features is subject to the YouTube Terms of Service. A connected creator can revoke access in Influrs or through Google Security Settings. Deleting Influrs data does not delete content stored on YouTube. Embedded playback remains disabled until the per-video Made For Kids lookup and required tracking and applicable-law controls are implemented; the current public route provides only an external source link.
9. Scores and automated decisions
A public profile can be ordered or filtered by simple product rules, but Influrs does not use it to make a solely automated decision that has legal or similarly significant effects on a creator. Claim and material moderation decisions can be reviewed by a person.
YouTube-derived influence, suitability, brand-safety and similar scores remain disabled unless the required platform approval and a separate lawful product decision are documented. Influrs users remain responsible for their own decisions and must not use the data unlawfully.
10. Correction, objection, removal and other rights
You may ask for access, correction, erasure, restriction or portability where applicable, and you have a specific right to object to processing based on legitimate interests. Tell us which profile and field is affected, your relationship to the creator, the requested outcome and enough evidence to verify the correction or authority.
We do not require an OAuth claim merely to exercise privacy rights. We may use a proportionate verification method to avoid changing or disclosing a profile to an impostor. We normally respond within one month and explain any lawful exception.
Follow the instructions linked from the profile or email influrscom@gmail.com. The profile link is an information route, not a submitted request by itself. If we uphold an objection or removal request, we will suppress or delete the affected data and take reasonable steps regarding downstream processors. Search-engine caches and the original platform are controlled by their operators.
11. Complaints
We acknowledge a data-protection complaint within 30 days and investigate without undue delay. You may also complain to the Information Commissioner's Office or the supervisory authority where you live or work.