Sid Kicks Privacy Policy

Effective date: November 9, 2026

Sid Kicks is a shoe collection and wishlist app for iOS and Android. This policy explains how its developer handles information when you use the app. For privacy questions, contact the Sid Kicks developer at Sid@sidwin.com. A personalized heading such as “[name] Kicks” does not create an account or change the app’s name.

Your collection and preferences

Sid Kicks stores your inventory and settings in the app’s storage on your device. Records may contain shoe brands and models, sizes, style codes, colorways, condition, box status, purchase prices and currencies, appraisal estimates you enter with their currencies and recorded dates, barcodes, notes, record and manufacture dates, country of manufacture, printed retail prices, and shoe or label photos. Your optional display name, size and brand defaults, collection sorting choice, achievement progress including the highest owned-pair count reached, and backup-reminder dates are also stored locally. These details support your collection, scanning suggestions, summaries, and personalization. An appraisal is your own recorded estimate; Sid Kicks does not automatically calculate or verify it.

Sid Kicks has no developer-operated collection server, account system, advertising, or developer-operated analytics service. Your collection is not uploaded to a Sid Kicks server. Device backups, Android SDK diagnostics, and actions you choose to share information are described below.

In build 14 and later, a newly reviewed box retail price may fill an empty price-paid field as an unconfirmed assumption, labeled “Assumed from box retail.” It does not replace a nonempty price-paid field or set an appraisal. You can edit, confirm, or clear the assumption. The app stores the price’s source and confirmation status locally. Duplicating a pair opens an editable draft and creates a separate record only when you save it; a copied paid amount is marked unconfirmed. The original record is retained, and copied records can safely refer to the same saved local photos.

Camera, photos, and recognition

Sid Kicks uses the camera when you choose to take a photo or scan a barcode. In build 14 and later, new or replacement shoe, box-label, and tag photos are taken with the camera rather than selected from the photo library. Existing saved photos, review of saved labels, and supported file imports remain available. Earlier builds may allow photo-library selection. You can still enter details manually. Barcode and label text recognition run on your device; photos are not sent to a Sid Kicks server for recognition. Android recognition models are bundled with the app. iOS uses Apple’s on-device recognition features. You can manage camera and photo access through your device settings.

In build 14 and later, label recognition may also use temporary close-up crops on your device. Country-of-manufacture suggestions are local, and you can enter or edit the country as free text. These additions do not send photos or label text to a new service or add a new recognition SDK.

Google ML Kit on Android

The Android app uses Google ML Kit. Google documents collection of device and app information, per-installation identifiers, and diagnostic metadata about feature usage, configuration, performance, and errors, including input and output sizes. Diagnostic transmissions can occur even though recognition runs on-device. Google uses this information for diagnostics and usage analytics and encrypts its transmission using HTTPS. See Google’s ML Kit disclosure and Google’s Privacy Policy.

Device backup and transfer

Your operating system may include app data and photos in cloud backups or device transfers, depending on its settings, limits, and behavior. This is separate from the backup and export files you choose to create in Sid Kicks. Android backup is not disabled in this version. Large photo collections may not fit within system backup limits, and a system backup is not guaranteed.

Monthly backup reminders

Sid Kicks can remind you within the app to save a backup of your shoe details, without photos. It stores the next due date, export-attempt date, and date you confirm a backup was saved on your device. You choose whether and where to save the file. The reminder does not upload anything automatically or request notification permission. Dismissing it defers it for seven days. After an export, only your explicit confirmation that you saved the file schedules the next monthly reminder; opening a share sheet is not proof of a saved backup.

Sharing, exports, and imports

When you choose to share selected pairs, Sid Kicks prepares their shoe photos and descriptions or an import file. These include saved manufacture dates, country of manufacture, and printed retail prices when present. Printed retail price is separate from price paid: including price paid is optional and off by default. Recorded appraisals are not included in selected-pair sharing, even when you choose to include price paid. Selected-pair sharing excludes the barcode field and images stored in the box-label and inside/legacy-label slots. It can include the image stored in the shoe-photo slot, even if that image shows a label: Sid Kicks does not classify image contents. Notes are optional in import files and off by default. Selected-pair import files can contain public manufacturer style codes. Shared photos are re-encoded to remove embedded image metadata; information visible in the image remains visible.

Sid Kicks’ details-only backup exports contain collection records, purchase details, and recorded appraisals including their currencies and recorded dates, but no shoe or label image files. CSV exports also contain these details without images. These exports cannot recover your photos if the device or app data is lost. The app does not include your profile, sorting preferences, achievement-progress, or backup-reminder files in shoe shares, details backups, or CSV exports. Size and brand values saved on individual pairs remain part of those pair records.

In build 14 and later, CSV exports and details-only backups also include saved price-source and confirmation information. Details-only backups still contain no photos or photo paths. When you opt to include price paid in a selected-pair import file, its price-source and confirmation information can also be included. When a selected-pair file is imported, the recipient’s copy clears the sender’s paid price and its source and confirmation information so that it is not treated as the recipient’s purchase price.

On iOS in Sid Kicks 1.0.1 and later, you can choose to create a separate private photo backup (.skphotos). It contains collection records and their saved shoe and label photos, including retained originals when available. It does not include app preferences or achievement history. Sid Kicks prepares the file on your device and does not automatically upload it. You choose whether and where to save it. The backup is not encrypted by Sid Kicks. Its integrity check helps detect a damaged or changed file; it does not encrypt or restrict access to the contents.

Export files are not encrypted by Sid Kicks. Review what you share and choose a trusted destination. The receiving app, person, or service controls its copy and handling.

Importing a details-only backup adds records without photos. It does not remove photos already stored with existing records and cannot restore photos to a new or cleared device. Importing into a collection that already contains shoes may create duplicates, so review the import before continuing. Importing an older photo-inclusive backup or a selected-pair share file can restore any included photos into the app’s local storage.

Web searches and marketplace links

When you tap Search for a style code, Sid Kicks opens Google in your external browser. The search link contains the style code and fixed shoe-research terms, not photos, your display name, notes, price paid, or recorded appraisals. Google handles your search and visit under its own privacy policy. Sid Kicks does not send this search automatically.

When you tap an eBay or StockX search button, Sid Kicks opens that service outside the app and includes search terms in the link. These can include brand, model, style code, and colorway. eBay links can also include size, condition, and box status. The receiving service handles your visit under its own privacy policy. Sid Kicks does not automatically upload your inventory for retail pricing or appraisals. The separate StockX label-matching feature is not connected in this version and sends no lookup requests.

Preparing a sale

Sell prepares an editable draft on your device using the selected shoe’s details. The generated draft excludes price paid, printed retail price, recorded appraisals, private notes, barcode fields, images stored in the box-label and inside/legacy-label slots, and profile name. Asking price starts blank and is optional. Review anything you add before sharing.

Copy buttons place your edited text on the system clipboard. Share sends the draft and, only if selected, a metadata-stripped shoe photo through the system share sheet to your chosen destination. This uses the shoe-photo slot, with the same slot-based exclusions described above. These actions require your choice. Open marketplace buttons open eBay, StockX, or Facebook Marketplace without shoe details in the link. Sid Kicks does not sign in, use a listing API, or automatically post a listing; you complete any listing on the marketplace, under its policies.

Draft edits are temporary and discarded when you leave the Sell screen. Closing it does not clear copied clipboard text or copies already shared. Clipboard handling follows your device’s settings.

Storage, retention, and deletion

Sid Kicks relies on the operating system’s app storage and security protections. Records stay in the app until you remove them or remove the app’s data. Removing a pair also removes its saved photos when no remaining record uses them. Original photos in your device’s photo library are separate. Deleting pairs does not reset your saved name, defaults, sorting choice, highest owned-pair count, or backup-reminder dates; clearing the app’s data removes that local state.

Your device’s delete-app or clear-app-data controls can remove the local app copy; offloading or archiving may retain data. These actions do not remove exports, previously shared copies, or operating-system backups. Manage those copies with their recipients or backup provider. Temporary sharing, sale-photo, and export files can remain in the app’s cache until cleanup by the operating system. Sid Kicks has no user account to delete. Deleting a collection record does not direct Google to erase SDK diagnostics; Google’s policies govern that data.

This policy website

This privacy-policy page is hosted on GitHub Pages. GitHub logs visitors’ IP addresses for security. Opening the policy from Sid Kicks does not include your inventory or profile in the link. See GitHub’s Privacy Statement for its handling of website visits.

Questions and policy updates

Contact Sid@sidwin.com with privacy questions. Updates will be posted on this policy page with the effective date shown above.