Integration

A day of your team's time — and we're on the call for it.

The SDK is in a closed pilot: access follows the application, there is no self-serve download and we do not pretend otherwise. Here is exactly what your team receives, implements and signs.

sdk_delivery · manifestPACKING
sdk package · per platform
integration guide
consent flow · ready to display
test access · pre-launch
engineer · assigned to you

Platforms, and what ships with them.

The list below is what exists today — "soon" means in development, not on a roadmap slide. No versions and no SDK sizes until we can prove them.

AndroidWindowsAny TV PlatformsiOS · soonmacOS · soon
You receive
SDK package and integration guideConsent flow, ready to displayTest access before launchAn engineer on the integration
You implement
Show the consent dialog before initUpdate your EULA and privacy policyLink to our policies from yours
Support
An engineer until launch — not a ticket queueDirect channel: Telegram, Slack or DiscordStore review support if a reviewer asks questions

From application to first payout.

Every application is reviewed manually. The steps are fixed — the pace is largely yours.

01 · ≤ 1 business day
Apply

One form, no commitment. We reply with next steps and indicative terms for your app.

02 · days, not weeks
Review & terms

We vet your app manually and agree commercial terms — in the agreement, not on a pricing page.

03 · days, not weeks
Kit ships

SDK, docs and a test key arrive after review passes — not before.

04 · your pace
Integrate & test

Async, off the UI thread, consent dialog included. Verify on a test key before anything goes live.

05 · together
First payout

Roll out, watch consented devices come online, get paid monthly per device.

■ SLAs are ours — integration speed is yours

Built to be invisible.

The SDK's job is to never show up — in your frame rate, your battery stats or your reviews.

Execution
async · off the UI thread
Activation
inactive until consent
Device impact
idle only · Wi-Fi · charging
Personal data
none collected

What engineers ask first.

The technical questions that come up in every integration call. Business questions live on the FAQ page.

It's built not to. All work runs asynchronously off the UI thread, and sharing only happens when the device is idle, on Wi-Fi and charging — so it never competes with your app for resources, and never touches the battery or the user's mobile data.

The SDK is designed around store policies: explicit opt-in consent, equal-weight decline, no personal data collected. The integration kit includes the required disclosure texts for your store listing, and we review your submission materials with you before you ship. No one can guarantee a store's decision — but this is exactly what the review process asks for.

One section. Because no personal data is collected, the disclosure is short: what is shared, under what conditions, and how to withdraw consent. The exact wording ships with the integration kit — you paste it, your counsel reviews it.

The SDK side is small — initialization plus the consent dialog, which is included. Most of the calendar time in the process above is our review and the agreement, not your code. There's no deadline on your side — you integrate at your own pace.

Step 01 is a form

The first step takes two minutes.

One form, one business day to a reply. Terms are agreed before you write a line of code — and step 05 pays out monthly.

Start the application