Privacy Policy

No FlexPockets account

FlexPockets does not require or create an account and does not ask for your Amazon credentials. Your automation settings, filters, session controls, and local activity history remain on your Android device. Clearing the app's storage or uninstalling the app removes that local data.

Accessibility service use

After you review the in-app disclosure and manually enable the FlexPockets Accessibility service, the app can read visible Amazon Flex interface content and perform the visible, user-started actions you configure. FlexPockets uses Android's Accessibility Service for this core automation function; it is not an accessibility tool for users with disabilities.

Visible-content inspection, automated gestures, and optional diagnostic content are scoped to the Amazon Flex app package. The service may observe only the foreground package and window identity needed to hide its overlay outside Amazon Flex and block automation on sensitive system, permission, installer, payment, password, and security surfaces.

Optional diagnostics

If you choose to share diagnostics, FlexPockets sends small technical reports while user-started automation is operating in Amazon Flex. These reports help PocketLab improve recognition and interaction reliability across Android devices and Amazon Flex versions. Reports may include:

• FlexPockets, Amazon Flex, Android, and API-level versions.
• Locale, screen dimensions, density, and orientation.
• Parser and automation state, filter results, attempted actions, and gesture or action outcomes.
• A random, app-generated installation identifier used to group related reports without a FlexPockets account.
• A fixed allowlist of recognized Amazon Flex control labels, such as Refresh, Accept, Reject, Offers, or Offer details. Arbitrary visible offer text—including payout, station, location, time, and duration details—is discarded before upload.
• Accessibility view IDs, node classes and states such as clickable, enabled, focusable, selected, or checked, plus normalized on-screen positions and bounds.
• The report creation time, event occurrence time, and server receipt time used to diagnose ordering and apply retention.

FlexPockets does not intentionally collect screenshots, passwords, credentials, payment-card data, login fields, editable fields, or accessibility information from unrelated apps. The app also discards any accessibility text or label that is not on the fixed control-label allowlist before upload. The server applies additional redaction for common email, telephone, address, URL, and identifier patterns.

Your diagnostics choice

Open FlexPockets, choose App options, then Diagnostics sharing to turn sharing off at any time. Turning it off stops new collection, cancels scheduled uploads, and deletes diagnostic reports still queued on the device. An upload already in progress may finish. If it does, that report remains subject to the retention process described below.

Subscription verification

Google Play manages purchases, trials, renewals, cancellations, and payment details. FlexPockets sends the Google Play purchase token, application package, and subscription product identifier to PocketLab's verification service. The service checks the subscription with the Google Play Developer API and acknowledges eligible new purchases. It does not maintain a FlexPockets account or subscription database and does not receive your payment-card number.

Network and hosting data

When FlexPockets or your browser connects to flexpockets.com, Vercel processes the source IP address, request time and route, browser or device and request details, and an approximate city and country inferred from the IP address. This information is needed to deliver and secure the website and app APIs, apply any configured traffic controls, prevent abuse, troubleshoot failures, and monitor performance. PocketLab does not use it for advertising or precise-location tracking.

Vercel retains service and network logs only as needed to provide, secure, and maintain its services under PocketLab's configuration and Vercel's terms. That operational-log retention is separate from the diagnostic-report process below. Contact PocketLab for a privacy request about website or API use.

Security, storage, and retention

Diagnostic uploads and subscription-verification requests are transmitted over HTTPS. The app-generated installation identifier is included in a diagnostic upload, then the server replaces it with a one-way hash before storing the report as a private object using Vercel Blob. The original identifier is not retained in the stored diagnostic object.

Diagnostic reports use a 30-day age threshold measured from collection. Reports waiting on the device are discarded when the queue is next processed after that threshold. A daily server cleanup deletes uploaded reports after the threshold, so deletion normally occurs during the next cleanup run.

Because PocketLab does not keep an account-to-report mapping or retain the original identifier in the stored report, an email address is not enough to reliably locate and selectively delete a particular uploaded diagnostic report. Uploaded reports instead follow the automatic age-based retention process. See Data controls for steps you can take on your device.

Service providers, sharing, and sale

Vercel processes hosting, network-request, and private object-storage data, and Google processes service data needed for Google Play billing and email data needed to provide Gmail. PocketLab does not sell or rent personal information, including diagnostic, billing-verification, network, or support information, and does not share it for cross-context behavioral advertising. We use service providers only to operate, secure, troubleshoot, support, and improve FlexPockets. Information may be disclosed when required by law or to protect users, the service, or legal rights.

Support communications

If you email PocketLab, we receive your email address and the message, device details, or attachments you choose to provide. We use this information to answer support or privacy requests, troubleshoot reported problems, and prevent abuse. Google processes these communications through Gmail.

PocketLab's support-retention policy is to delete support communications within 24 months after the last related interaction. A message may be kept longer when reasonably necessary for security, fraud prevention, a legal obligation, or a dispute. You may request earlier deletion by emailing the address below; we will delete the message unless continued retention is required for one of those reasons.

Contact and policy changes

For privacy questions, email PocketLab at lfernanrp@gmail.com or visit Support. If this policy materially changes, we will update the effective date and provide any notice or consent required by law or Google Play policy.