PICKS Support

Provider: FOOTBALL ZON Inc. (formerly Lab3 Corp.) · Developer display name: Lab3tech
Support and privacy contact: gira@lab3.tech

Start with one choice

Start with a choice you remember. It can be a big turning point or a small recent choice. Add your reasons and later updates when you want to. Connect new records to an earlier choice to build branches, and tap a card on the map to read what you wrote. The lines are connections you choose, not location tracking or an automatic explanation of cause and effect.

Where are my records?

No sign-in is required. Records are stored in the app on your device and do not automatically move to another device. The web preview and installed app also keep their records separately.

PICKS does not provide automatic cloud sync or account-based recovery. Device-level backups depend on your operating system and settings; do not treat them as a verified PICKS backup.

Back up a map

  1. Select the intended map and open Settings, then choose “Back up”.
  2. Choose a location and finish the file dialog. Complete any file verification the app requests. A canceled dialog or an unconfirmed save is not a completed backup.
  3. Keep the checked file outside the app and repeat for every map you want to retain. Check the files before removing the app, clearing data or changing devices.

A backup is an unencrypted JSON file. It contains the selected map's records outside Trash, their connections, text, reasons, later updates and map information. It excludes Trash, avatars and the full app setup. Restore any trashed records you want included before exporting. Keep files private.

Import a backup

Select the intended destination map, use “Import backup” in Settings, choose the file, and review the file/map preview before confirming. Files must be 10 MiB or smaller. Matching entries are skipped; conflicting records are blocked rather than overwritten. Importing an older file does not reactivate the same record from Trash.

For a child's map, the backup must match the map type and the current name, or a previous name saved in that map's local history. An older file without child-map information cannot establish the match. This checks labels and local history, not a child's identity. Another device or cleared app data may not have that history. If an import is rejected, preserve both copies and contact support. Do not edit the JSON or rename another map to force a match.

Editing, Trash and child maps

You can edit saved text. Moving a record to Record Trash hides it from the active map and retains it locally for restoration. Connections return when both records are active again. Parents can rename child maps or move them to Map Trash and restore them. These are adult-maintained maps on this device, not shared accounts or joint editing.

There is no permanent Empty Trash action in this version. Trash is not included in exported backup files. Editing or moving records to Trash does not erase earlier files or copies held elsewhere.

If something goes wrong

Keep the existing app data and backup files. Follow the app's check or reopen instructions if it cannot confirm a save, edit, Trash action or import. Do not uninstall, clear data, repeatedly import a conflicting file or edit JSON as a repair step.

Contact gira@lab3.tech with your device/OS, app version, action and visible error. Redact screenshots. Do not include journal text, children's names, backup files, passwords or authentication codes. We do not promise a response time or recovery of lost local records.