Piko Privacy Policy

1. Scope and current product status

Piko is an offline-first personal scheduler, notes, reminder, alarm, location-trigger, and timer application. Its primary data is stored in a local Drift/SQLite database and local preferences on your device. Core local use does not require a Piko account.

This policy describes the current user-facing product as audited on 11 August 2026. In Piko:

• Available means implemented and reachable in the current app.
• Conditional means implemented but dependent on platform support, credentials, a store product, an account connection, or an Android system setting.
• OS-managed means Piko can inspect or open a relevant setting, while Android or the device manufacturer controls the final behavior.
• Coming soon means unavailable or informational and is not treated as an implemented feature.

The current Calendar is a local projection of Piko schedule occurrences. Although the source contains a calendar-sync abstraction, the current production provider is not configured, and Piko does not request access to the device’s system calendar database.

2. Information Piko processes

The information involved depends on the features you use, the permissions you grant, and the content you choose to create, import, link, back up, export, open, or share.

Public website

This website is a static informational site. Its supplied code does not use analytics cookies, advertising trackers, account login, or contact forms. The hosting or content-delivery provider may process ordinary server information—such as IP address, user agent, requested page, timestamp, and security events—to deliver the site, prevent abuse, and maintain reliability.

3. Typed and voice commands

Typed commands

Piko’s typed command parsing is rule-based and runs on the device. It can resolve supported intent, date, time, delay, duration, recurrence, and location-trigger fields. The current app does not require a downloaded language model, a cloud AI service, a Local AI model manager, or a production Whisper runtime.

Home commands currently create Reminders and Alarms, start a Timer after a valid duration is resolved, or prepare a location-triggered Reminder, Alarm, or Timer candidate. General management actions such as edit, delete, complete, pause, resume, stop, restart, and cancel are handled through direct controls rather than a cloud command service.

Voice commands

Piko requests microphone access only when you start voice input. The phone’s speech-recognition service may process the audio under its own settings and privacy terms. Piko receives the transcript, places it in the Home input, and does not auto-send it; you review the text and press Send.

Piko does not retain raw voice audio. A separate local transcript-logging preference is available in the Privacy Center and requires confirmation.

4. Location triggers and OpenStreetMap

Location Trigger is currently an Android-focused feature using Google Play Services geofencing and a key-free OpenStreetMap map picker. You can choose current location, saved or recent places, manual coordinates, or a point on the map, then set a radius and supported arrival, leave, nearby, or dwell condition.

For closed-app triggers, Piko needs device Location services, foreground Location permission, precise accuracy, Android “Allow all the time” background access, and notification access for alert presentation. One-time triggers disable after the first valid transition; repeating triggers re-arm according to their stored rule.

Piko stores the places and trigger state needed for the automations you create. The current product does not provide a general continuous location-history timeline. Recent and saved places remain local unless included in a backup or sync category you select.

When the map is shown, the tile service receives ordinary network requests needed to return map tiles. Depending on the service, this can include IP address, device/network metadata, requested tile coordinates, and timestamps. Do not place confidential text in a map label. Use of OpenStreetMap Foundation services is subject to the OSMF Privacy Policy and applicable tile-service rules.

The current iOS configuration declares microphone and speech-recognition usage descriptions but does not configure foreground or background Location usage. The Android geofence workflow therefore must not be treated as configured for iOS in the current build.

5. Android permissions and system access

Piko’s Permissions & System Access review handles one capability at a time, shows live state, opens the shortest relevant Android path, and refreshes when you return. Setup can be skipped; Piko does not block entry to local features.

Piko also declares normal or platform-managed capabilities needed for vibration, wake locks, foreground services, reboot/package-replacement recovery, and Internet access for maps, Drive, sign-in, and store billing.

6. Google Drive and Google API user data

Google Drive is conditional on valid Google configuration, explicit account connection, and your consent. Passive app startup does not present account UI. Only an explicit Connect, Reconnect, or Drive operation may request account or consent UI.

Scope and access

Piko requests https://www.googleapis.com/auth/drive.appdata. This scope lets Piko see, create, and delete only its own configuration or backup data in your private Google Drive app-data area. It does not grant access to browse, read, change, or delete ordinary files in My Drive or shared folders.

How Drive data is used

• connect and disconnect the selected Google account;
• upload selected data categories as incremental snapshots and maintain a logical backup index;
• run Sync now or optional automatic upload after a real local change is pending;
• export a backup, preview and validate an import, and apply an explicit Merge or Replace policy;
• create a local safety backup before destructive replacement;
• support Wi-Fi-only, attachment, charging, cancellation, retry, offline-pending, and history controls where the platform adapter supports them;
• create optional passphrase-encrypted backups and, if you choose, store the passphrase securely on the device; and
• delete all Piko Drive backups at your request.

Automatic Drive work is upload/backup only. Download, merge, replace, or restore always requires an explicit user action. Without valid Google configuration, Piko shows Drive as unavailable or not configured while local features continue to work.

Google API Limited Use

Your Drive controls

You can disconnect the account in Piko, revoke Piko’s Google access through your Google Account, delete Piko Drive backups from Piko where supported, or remove Piko’s app data through Google Drive settings. Revoking authorization prevents future access but may not itself delete backup files already stored in Drive.

Google’s own processing is described in the Google Privacy Policy.

7. Attachments, local backup, import, export, open, and share

Piko can create validated .pikozip backups, import supported .pikozip, encrypted .pikoenc, JSON, and batch text files, export JSON data and CSV schedules, and create HTML or PDF summaries. Structured restore requires a preview and an explicit Merge or Replace choice before data is written.

Attachments are inserted into Notes through system-selected file flows. Images can render inside the document; other files appear as typed rows. Attachment order can be included in local backup, optional Drive categories, and restore.

Piko uses Android’s system document picker and scoped MediaStore publishing to Documents/Piko/... where supported. It does not require broad shared-storage access. After a completed file is published, you may choose Open, Open folder, or Share. Those actions give the selected destination temporary access to that specific file.

Files you export or share are outside Piko’s private storage and are controlled by you and the destination you choose. Protect backup files and passphrases appropriately.

8. Piko Pro and platform-store billing

Piko can display Free, Pro, trial, grace, and expired entitlement states. The current billing integration loads only monthly (piko_pro_monthly) and yearly (piko_pro_yearly) platform-store products and supports Purchase and Restore purchases.

Prices, taxes, currency, billing period, renewal terms, trial or offer terms, payment processing, and cancellation controls are provided by the platform store and shown before purchase. If billing or products are unavailable, Piko reports that state rather than simulating a purchase.

The store may provide Piko with product, purchase, transaction, and entitlement information needed to grant or restore access. Piko does not receive your full payment-card number. Google Play’s handling of purchases is governed by the Google Play Terms of Service and Google’s privacy terms.

Manual editing, local data, privacy controls, and basic export remain available without a subscription. The exact benefits attached to a plan are shown in Piko and by the store before you purchase.

9. Notifications, lock-screen surfaces, alerts, and widgets

Piko may place schedule titles, times, status, and action labels in notifications, full-screen Alarm surfaces, Reminder overlays, persistent Timer notifications, snoozed countdowns, follow-up notifications, launcher shortcuts, and Android home-screen widgets. Android and the device manufacturer control whether this information appears while the device is locked.

• Reminder notifications can include Open, Snooze, and Done.
• Alarm notifications can include Snooze, End, and Open, and only Alarm may use a full-screen alert.
• Timer notifications can include Pause/Resume, Stop, Open, or Done depending on state.
• Reminder follow-up payloads exclude Note bodies and list-row text.
• The Piko Schedules widget can hide schedule titles while the device is locked.

Review Android’s lock-screen notification settings and Piko’s widget/privacy options if other people can access or view your device.

10. Providers, transfers, and disclosures

Piko does not operate an account-first cloud database for core use. Information leaves the local app only when a feature requires it or when you direct an export, open, share, backup, account connection, purchase, or support request.

Relevant providers can include:

• Android and Google Play Services: notifications, exact scheduling, geofencing, background services, system settings, widgets, and platform behavior.
• Google Sign-In and Google Drive: optional account authorization and private Piko app-data backup, sync, restore, and deletion.
• Google Play or another supported platform store: subscription product display, payment, entitlement, restoration, cancellation, refunds, and fraud controls.
• Your phone’s speech service: audio-to-text processing when you start voice input.
• OpenStreetMap or the configured map-tile provider: map tiles shown while the interactive location picker is open.
• File destinations and sharing apps you choose: the one attachment, backup, or export you open or share.
• Website hosting, content delivery, email, or security providers: public-site delivery, abuse prevention, and support communication.

We may also disclose information when reasonably necessary to comply with applicable law or valid legal process; investigate fraud, abuse, or security incidents; protect users, rights, property, or safety; or complete a merger, acquisition, reorganization, financing, or asset transfer subject to applicable protections.

Each third-party service operates under its own terms and privacy policy. Piko does not control the provider’s independent processing.

11. Retention and deletion

• Local Piko records: remain until you edit, archive, trash, permanently delete, use Delete all data, clear app storage, or uninstall Piko. Notes Trash supports manual retention and Empty Trash; timed auto-delete options other than Off are not currently enabled.
• Home transcript logging: depends on your optional local setting and can be disabled. Raw voice audio is not retained by Piko.
• Timer history: remains when history saving is enabled until you delete or reset it through supported controls.
• Saved and recent places: remain locally until you remove them or delete local data and may be included only in a backup category you select.
• Drive data: remains in your private Drive app-data area until deleted through Piko where supported or through Google Drive controls.
• Exported files: remain at the destination you chose until you delete them there.
• Store, speech, map, and hosting records: are retained by those providers under their own policies.
• Support communications: are kept only as long as reasonably needed to answer the request, maintain security or business records, and meet legal obligations.

Piko’s Privacy Center shows local counts and includes a confirmed Delete all data flow. A successful import or restore refreshes shared repositories so the app converges on the restored state. Device permission grants, notification-channel state, OAuth tokens, debug logs, caches, and absolute device paths are not treated as portable backup truth.

12. Security

Piko uses safeguards appropriate to an offline-first mobile app, including Android app sandboxing, limited OAuth scope, platform-managed credential storage, validated import, explicit restore conflict policy, identity checks for stale or duplicate actions, and optional passphrase encryption for supported backups.

No device, storage medium, software, network, or provider can be guaranteed completely secure. Protect your device lock, Google Account, exported files, backup passphrase, and any destination where you share Piko data. An ordinary Drive backup should not be assumed to be end-to-end encrypted by Piko unless you explicitly create and use the supported encrypted-backup option.

13. Your controls and privacy rights

You can control most Piko data directly:

• create, edit, archive, trash, restore, or permanently delete supported local records;
• export local data and create a validated backup;
• disable transcript logging and use the Privacy Center’s confirmed Delete all data action;
• review, grant, deny, or revoke Android permissions and system access;
• remove saved places and location triggers;
• disconnect Drive, revoke Google access, and delete Piko Drive backups;
• manage or cancel a platform-store subscription and Restore purchases; and
• contact us at frontiertech.one@gmail.com about information held directly by us.

Depending on where you live, applicable law may provide rights to access, correct, delete, restrict, object to, or receive a portable copy of personal information held by us, withdraw consent, or complain to a data-protection authority. These rights may be subject to verification and legal exceptions.

14. Children

Piko is a general productivity application and is not designed specifically for children. A child or minor may use Piko only with the permission and supervision required by the laws, platform rules, and family settings that apply where they live.

Do not enable a child’s Google account connection, platform purchase, background location, or other connected feature unless the necessary parent or guardian has reviewed the feature and provided any required authorization. Contact frontiertech.one@gmail.com if you believe information was sent directly to us by a child in a way that should be reviewed or deleted.

15. International processing

Google, OpenStreetMap-related services, website hosting, email, speech, and platform-store providers may process information in countries other than where you live. Their transfer mechanisms and safeguards are governed by their policies and applicable law. Core Piko data remains local unless you use a connected or user-directed feature.

16. Changes to this policy

We may update this Privacy Policy when Piko’s implemented features, data flows, providers, permissions, platform requirements, or legal obligations change. The revised policy will be posted at this URL with an updated date. Where required, Piko will provide additional notice or obtain consent before using personal or Google user data for a materially different purpose.

17. Contact