Your data.
A clear purpose.

Who operates the waitlist

PocketShare is operated by Parker. For privacy questions or to request removal from the waitlist, email [email protected].

What we collect

When you join, we record your email address, the site you signed up on, the signup timestamp, the version of this notice, and any campaign tags included in the link you used. Campaign tags are labels such as a campaign name or the source of a link.

Why we use it

We use your signup to manage the waitlist and email you about PocketShare’s development, availability, and possible early access. Signup source and campaign tags help us understand where interest comes from. Joining is optional and does not guarantee access, device eligibility, rentals, or earnings.

Storage and access

Signups are stored in our waitlist database and accessible to the people operating PocketShare. Your email is not included in operational notification messages.

Cloudflare provides DNS, website delivery, and traffic protection. It processes connection information, such as IP addresses and requested URLs, to provide those services. Avoid putting personal information in campaign tags or URLs.

These sites include Cloudflare’s analytics beacon. It can collect page and referrer URLs and page-load performance measurements. Cloudflare’s RUM documentation describes this collection without cookies or other browser storage.

How long we keep your signup

Active waitlist records are deleted 12 months after signup. You can ask us to remove your record sooner by emailing [email protected] from the address you registered. We may need to verify a request before acting on it. Restricted recovery backups may retain a deleted record until backup rotation removes it; cleanup currently runs during deployments. If a backup is restored, we reapply deletion requests before using the restored waitlist.

Preventing abuse

The signup service uses a limited in-memory set of IP addresses and request counters to limit automated or excessive requests. These records are replaced as that set fills or cleared when the service restarts. They are not added to the waitlist database.

Private pilot accounts and devices

For the private pilot, we store your approved email address, Google account identifier if you choose Google sign-in, account/session records, enrolled device model, manufacturer, Android and app versions, connection timestamps, pause state, and rental/command history. Device identity is self-reported. The Android host app stores its credential encrypted using Android Keystore and reports status while visible. A separately paired USB connector reports readiness and executes approved fixture commands.

If you enable periodic checks in the host app, it sends battery level, charging state, network type, free storage available to the app, and the results of small app-owned storage and calculation checks. It does not collect Wi-Fi names, your files or other apps. We retain the latest accepted health report and its receipt time, visible in your host dashboard. Android may delay these background checks. You can stop reporting in the app; the last report remains until it is replaced or the device record is deleted. Reports do not establish device integrity or rental qualification.

The pilot also records reported temperature and power information, computed device health scores, and server-observed check-in coverage. Check-in coverage uses time bins retained for seven days; it measures contact with the service rather than guaranteed availability. Device scores and health reports are visible to the provider and operator.

When you request verification, we record your dedicated-device statement, review status, evidence snapshots, operator notes, and review history. Operational review records are retained for pilot security and support. Contact us to request deletion; some security records may need to be preserved after a request.

Google processes basic sign-in information when you choose Google sign-in. Resend delivers requested email sign-in codes. Our database stores hashes of credentials and codes; raw session credentials are not placed in URLs or logs. Necessary secure cookies maintain sign-in and prevent replay.

Payment onboarding in the pilot

Stripe Connect onboarding is available only in sandbox mode. Stripe handles the information entered on its onboarding pages. PocketShare stores the connected account identifier and onboarding status, and does not store bank details from that flow. No live charges, earnings, or provider payouts are processed in this pilot. Do not enter real financial information into a sandbox flow.

Pilot screenshots and cleanup

The approved test fixture has no accounts or network permission. Its screenshots and bounded command results may contain text you enter during a test. They are stored privately and accessible through the renter’s authorized session. Use test data only. Fixture cleanup clears that app’s data; it does not erase the whole phone or make it safe for unrelated tenants. The hardware owner controls the physical device.

Screenshots and command results are cleared after one day by periodic pilot maintenance. Account, device and rental metadata remain until operator deletion. You may request deletion at [email protected]. Restricted pre-deployment recovery backups can retain deleted records until backup cleanup during a later deployment. No paid rentals or host payouts are processed in this pilot.

Updates to this notice

If the data handling changes, we will update this page. The version shown above identifies the current notice.