What the intake is for
When enabled, the intake collects information needed to understand creator fit, discuss platform and support options, and follow up using your chosen contact method. It asks for confirmation that you are at least 18 and separate consent to NCS follow-up, with this notice available before submission.
Information the intake requests
- Creator type, country, preferred language and whether you are new, currently active or returning.
- Preferred earning path, platforms currently used and the platform being considered.
- Preferred contact method and contact address or username, your main goal, and payout urgency or launch timing when relevant.
- Age confirmation and follow-up consent, together with an allowlisted source page, language, selected platform and package interest where applicable. Arbitrary query strings and referrers are not retained; campaign collection is not enabled.
The intake does not request legal identity documents, platform passwords, payment details or adult media. Do not include these in application answers.
Private records and notifications
The implemented private service stores the authoritative application in a private NCS database, with server-side validation, request limits, rate controls and expiring abuse-check tokens. A successful response is sent only after storage commits. Retries of an unchanged attempt use the same identifier to avoid duplicate applications. Private review and administrative actions are access-controlled and logged through local operator access. There is no public application lookup. Application records and private creator analytics are not public-page content.
Telegram delivery remains disabled. When enabled, after storage a notification may contain an application identifier, submission time, high-level platform or earning-path interest, and instructions for private review. Full contact information, free-text answers, legal names and other sensitive application data must not be included. Telegram is a notification channel, not the application record; notification failure must not discard a stored application.
Site measurement and external platforms
The site is prepared to measure public page and action activity. External reporting is disabled until a provider is approved. Prepared events contain only allowlisted page/source, site language, public platform/package interest or contact-channel type where relevant. They exclude form answers, preferred contact details, creator type, application identifiers, raw URLs and referrers. No analytics provider is connected to this site yet.
Form answers stay in memory in the open page, not browser local or session storage. They are cleared from the form after confirmed storage. The private service uses a keyed hash for short-lived abuse-rate records instead of storing raw IP addresses in application records. Final hosting logs must be reviewed before activation.
When you choose to visit an external platform, its own privacy notice and terms apply to your activity there. Review those before sharing information.
Read about referral compensationRetention, deletion and questions
Production retention periods and request procedures for deletion, consent withdrawal and related requests are not finalized. The service provides configurable retention, private deletion and administrative audit records. A minimal deletion record supports reconciliation before a backup is restored; its configured lifetime must exceed the maximum backup lifetime. The operating schedules and request-verification procedure must be defined, along with a verified contact route, before public intake opens. No production retention deadline or request response time is promised here.
NCS contact channels are not available on this site yet. Updated contact and handling details will be published before applications open.