The wallet where your data, consent and royalties live.

Why people want this

Extra income shouldn't cost another shift.

Millions of Americans already take on side work for extra money, many to cover the basics, and many are worn out by it. Life by IDIA offers a different kind of income: your data, shared with your permission, instead of taking more of your free time.

Royalty estimator · health data

What could your health data earn?

Built on the real Hub prices and the 30% contributor share. Buyer demand is a made-up scenario you can change, because there isn't enough real buying history yet to forecast from.

• This is not a promise of earnings. There is no fixed yield.
• You are paid only when a buyer's purchase includes your consented records.
• Demand, match rates and contributor counts are invented for illustration, not IDIA results.
• Royalties are paid in USDC and IDIA Tokens only, never dollars to a bank account.
• The IDIA Token's market value can rise or fall; this shows token counts, not their price.
• Turning off a stream or purging your identity stops future royalties.

Connect what you already use. Every reading keeps its consent.

The Data tab is where you connect sources, see which streams are active and turn any of them off. Four sources cover your health, your workouts, your car and your home.

Apple Health

Health & wearables

Confirm with Face ID, then choose which Health categories to allow on the iOS permission screen.

What it sends

• Steps and active energy
• Heart rate and heart rate variability
• Breathing rate, blood oxygen and body temperature
• Walking speed, step length and gait
• Sleep
• Noise and UV exposure

Devices that feed it

• iPhone
• Apple Watch
• Smart rings such as Oura
• Smart scales such as Withings
• Garmin watches, through Garmin Connect

Anything that writes to Apple Health on your iPhone. Your readings stay on the phone until it sends them.

Strava

Workouts & sport

Confirm with Face ID, then sign in to Strava and approve Life by IDIA.

What it sends

• Activities and workouts
• Route and distance
• Pace and heart rate
• Elevation and effort

Devices that feed it

• Garmin, COROS and Wahoo devices
• Apple Watch
• Indoor apps such as Zwift
• The Strava phone app

Anything that uploads activities to your Strava account.

FordConnect

Vehicles

Confirm with Face ID, then sign in to your Ford account and approve access to your vehicle.

What it sends

• Location and movement
• Driving dynamics
• EV and battery level
• Vehicle health and security

Devices that feed it

• Mustang Mach-E
• F-150 Lightning
• F-150, Bronco, Explorer and other connected Ford models

Ford vehicles with Ford's built-in connected service switched on. Check yours in the FordPass app.

Nest

Home devices (IoE)

Confirm with Face ID, then sign in with the Google account that runs your Nest devices and approve access.

What it sends

• Thermostat and climate
• Home occupancy
• Device activity
• Energy patterns

Devices that feed it

• Nest Learning Thermostat
• Nest Thermostat
• Nest Temperature Sensor
• The heating and cooling system they control

Nest devices linked to your Google account.

Device names are common examples, not partners or devices IDIA has tested. On Android, Health Connect plays the part of Apple Health.

Turning sharing off

In Life by IDIA

• Data tab: open a source and tap Disconnect. The stream stops and the disconnect is recorded as its own ACA.
• Settings, Privacy: the Health Kit switch turns off health syncing in Life by IDIA.

In your iPhone's privacy settings

iPhone Settings → Privacy & Security → Health → Life by IDIA

Switch off any category, or tap Turn Off All. An app can't take back an iOS permission itself, so this is where you withdraw Apple's permission completely. You can also get there from the Health app: tap your profile picture, then Apps.

For Strava, Ford and Nest, you can also remove Life by IDIA from that service's own account settings.

Turning a source off stops new readings and future royalties from it. It does not undo sales already made under an active consent. Deletion & Revocation

Every consent action leaves a fingerprint you can see.

An Auditable Consent Artifact (ACA) is a digital fingerprint that IDIA creates every time you take a consent action. It records that the action happened, from your account and your device, and when. Each one is a unique code called the ACA hash.

What goes into one

• Your account
• A key held in your device's secure chip, unlocked with Face ID on iPhone or your device's passkey on the web
• What the action was
• The exact time

When one is made

• Connecting or syncing a data source, such as Apple Health or Strava
• Data arriving through IDIA's intake gate, shown as Vulture Gateway
• Accepting the Terms or making your Authority of Record decision
• DAO actions: proposals, votes, vetoes and committee applications

Your transaction log

Open the Data tab, then Transactions. The Audit Log lists every ACA your actions have created: the source, the ACA hash (your audit key) and the time, newest first. Copy any hash with one tap. In Settings, Privacy, you can also export your consent records as a CSV file.

When a buyer's request uses your data, the receipt in The IDIA Hub lists the ACAs it drew on. See step 03 · Egress Logs.

IDIA's Own Method

Proprietary

The ACA is IDIA's own design. How an ACA is built, stored and checked was developed in-house and is not an open standard or open-source code, so we describe it here rather than publish it. What you can see is the result: the ACA hashes themselves, in your Audit Log and on every buyer receipt.

What an ACA does not prove

• An ACA shows that a recorded consent action happened, from which account and device, and when. It does not show that the data is accurate, anonymous or safe for a buyer's use.
• A hash is a fingerprint, not a copy. It contains none of your health data.
• ACAs are kept in IDIA's own records. The on-chain parts of a sale are the Liability Receipt NFT and the USDC and IDIA settlement.
• The method has not been independently reviewed yet. That review is planned.

Provenance vs certification