Your smile story, one photo at a time.

Overview

SmileTrack is a private, AI-assisted photo journal for recording visible changes in your smile. This Privacy Policy applies to the SmileTrack iPhone app and this website. By using SmileTrack, you acknowledge the practices described here.

This website is a static information page. Our hosting provider may process technical request information needed to serve and protect the website. If you contact support, we process the information you choose to send to answer your request.

Photos, face-related information and generated results

SmileTrack processes a photograph when you choose one from your photo library or take one with the camera and request analysis. It resizes and compresses the entire selected frame; it does not automatically crop the image to the mouth or remove the rest of a face. Depending on what you submit, the image may include teeth, gums, lips, other facial features, other people and background information. Choose a photo you are comfortable sending for processing.

The app creates a full-frame JPEG for analysis and, for saved scans, a smaller full-frame thumbnail. It also processes AI-generated photo-quality feedback, visual observations, an apparent alignment/evenness score and label when available, comparison direction/confidence when a previous photo is used, and suggestions for taking more consistent photographs. These are visual estimates, not physical measurements, a diagnosis, an assessment of dental health, or evidence of treatment success.

SmileTrack does not implement facial recognition, identity matching, facial-landmark extraction, face-geometry measurements, biometric identity templates or a facial-embedding database. This does not make submitted photographs anonymous or mean that a processing provider performs no internal image computations.

Saved scan records include the scan/save time, thumbnail, analysis results and a reference to the full-frame photo. Older records may also contain an encoded full image in the database. The app uses your account's user identifier to associate these records with you. It does not extract a photograph's original capture date for the saved scan timestamp in this implementation.

Why we process this information

We use photos and results to analyze whether a photograph is suitable for comparison, describe visible non-clinical differences, show your private photo journal, and compare a new photo with your most recent saved photo when available. Good or usable analyses are automatically saved to your history. Photos rejected as unsuitable and unsuccessful analyses are not normally saved as scans, but they may already have been transmitted for processing and may still be subject to provider retention and operational records.

We use account information for authentication and account access. We maintain request counts and technical records to enforce usage limits, protect the service, troubleshoot failures, and complete or safely retry saves and deletions. A failed analysis can still count as an attempted request.

The Firebase SDKs also send Google technical user-agent information, including device and operating-system information, the app bundle identifier and developer platform, to understand platform and version adoption and guide Firebase product decisions. This SDK diagnostic information is separate from the photographs and generated analysis submitted for SmileTrack's core features.

Providers, transfers and storage locations

These app-specific privacy controls describe SmileTrack version 1.0 build 3 and later. SmileTrack uses Google Firebase Authentication, Cloud Firestore, Cloud Storage for Firebase and backend functions running on Google Cloud. Firebase Authentication handles sign-in information and account identifiers. The backend receives the submitted current photo and, when available, the previous saved comparison photo. Saved full-frame photos are stored in the app's Cloud Storage bucket. Thumbnails and generated analysis results are stored in Cloud Firestore under the user's account, together with the save time and photo reference.

The currently configured photo bucket and backend functions are in the Google Cloud us-central1 region in the United States. The Firestore database uses the nam5 United States multi-region. Google describes Firebase Authentication as operating in the United States. Google Cloud operational/audit logs use configured global log buckets. These service configurations do not establish that every provider or support process is restricted to the United States.

For analysis, the SmileTrack backend sends OpenAI the full-frame compressed current photograph and, when available, the full-frame previous comparison photograph, along with instructions for the visual analysis. Images are included in the request itself, not supplied as public Firebase download links. The backend also sends a stable safety identifier generated by hashing a SmileTrack-specific prefix and your Firebase user identifier with SHA-256. This supports service safety and abuse prevention. It is pseudonymous, not anonymous: requests from the same account can carry the same identifier. Your email address and password are not included in this analysis request.

OpenAI returns generated analysis through the backend to the app. The app does not send its separate thumbnail to OpenAI for this analysis. The backend's Responses API request sets store:false, disabling normal stored response application state for that request. This setting is not a Zero Data Retention guarantee and does not by itself eliminate safety, abuse-monitoring or applicable model-cache retention. The OpenAI project used by SmileTrack is configured for Global geography, and requests use the default API endpoint rather than a regional endpoint. We do not restrict OpenAI processing to a particular country. The Google storage regions above do not establish OpenAI residency.

Retention and deletion

Saved scans and operational records

There is no automatic age-based expiration of saved scans in the app. Active photos, thumbnails and results remain until you delete the relevant scan, your history or your account. Displaying only the newest 50 scans does not delete older saved scans.

Usage records are not removed by deleting a scan or history. They are removed from the active account database during account deletion. They do not contain the submitted photo or generated analysis text, and currently have no separate automatic age-based expiration.

To prevent interrupted requests from duplicating or restoring data, the service keeps operational save/deletion records containing operation and scan identifiers, photo paths, timestamps, status, an account-generation number, and, for saves, a SHA-256 fingerprint of the save payload. These records do not contain the photo bytes, thumbnail or generated analysis body. Scan/history deletion can leave these records and deletion markers; they currently have no automatic expiration. Account deletion removes the per-photo operational records and fingerprints but retains a minimal account deletion guard and receipt, linked to the user identifier, to reject stale requests and recover a lost confirmation. That minimal guard/receipt has no automatic expiration.

In-app deletion and interrupted requests

Deleting an individual scan removes its active stored photograph and scan database record, including its thumbnail and generated analysis. Deleting history removes active scan photos and records for the account, including older scans not currently displayed, while keeping the sign-in account and usage records. Account deletion additionally removes the active account database records and Firebase Authentication user.

Deletion can involve more than one service. The app records a deletion request, hides loaded scan content on the current device, and blocks new scan work while the request is pending. The backend records the operation, rejects stale work, and retries incomplete cleanup. The app does not report completion solely because a button was tapped, a timeout elapsed, or only one service finished. If a request is interrupted, use the retry action to continue it. Some unresolved upload outcomes require support assistance. Completion of active-data deletion is not a promise that every provider recovery copy has already expired, and we do not promise a fixed completion time for a failed or interrupted request.

New saves are tracked before uploading. Failed or interrupted saves can leave a temporary object while recovery determines whether it was saved or must be deleted. Cleanup is retried, and unresolved cases remain pending rather than being declared deleted. Photographs already transmitted to a provider cannot be recalled by cancelling a request on the phone.

Device copies

The updated app uses a memory-only Firestore cache for scan data and clears the app's previous persistent Firestore cache before using it. It clears its loaded scan list and image cache and retires the Firestore cache during deletion/account transitions. Stale callbacks are not allowed to repopulate the current session. The app checks server state when returning from the background before restoring private history.

These actions do not delete originals in your Photos library, your iCloud Photos copies, screenshots, device backups or copies you have made elsewhere. They do not promise secure physical erasure of device memory/storage or immediate erasure on another device that is offline. Provider- and operating-system-managed copies have their own lifecycles.

Google recovery copies and logs

The current photo bucket has a seven-day soft-delete retention setting. Removal of an active photo can therefore leave a recoverable deleted copy under that provider setting. Object-level holds, legal requirements or separately maintained copies can require additional handling; active-object deletion is not proof of immediate irreversible erasure.

The current Firestore database has point-in-time recovery disabled and one-hour version retention. No scheduled Firestore backups or TTL deletion policies were configured when these settings were checked. Database deletion and provider recovery/version retention are separate, and this statement does not represent an inventory of historical exports outside the active database.

Google Cloud's configured general log bucket retains logs for 30 days; the required audit log bucket retains its logs for 400 days. These operational/audit logs are separate from scan history and are not deleted by in-app scan deletion. Application error logging is designed to omit photo bytes and generated analysis text, and OpenAI SDK request/response logging is disabled in the updated backend. Infrastructure request metadata and framework error logging can still occur; we do not claim that every malformed request or provider diagnostic is incapable of containing submitted content.

Firebase Authentication has a separate provider retention policy. Google states that authentication information is removed from its live and backup systems within 180 days after customer-initiated account deletion, and that logged IP addresses are retained for a few weeks. These are Authentication-specific statements, not 180-day retention periods for SmileTrack photos.

OpenAI retention

OpenAI's standard API documentation describes abuse-monitoring logs that may contain submitted content and are normally retained for up to 30 days. Longer retention can apply when required by law or reasonably necessary to protect OpenAI's services or others from harm. Applicable prompt caching can retain encrypted representations for up to 24 hours. Images flagged as potential child sexual abuse material may be retained for manual review, including under special retention controls. SmileTrack does not claim an approved Zero Data Retention or Modified Abuse Monitoring arrangement, or guarantee that every provider-held copy is deleted within 30 days. These are documented provider defaults and exceptions, not a claim that every request is retained for every listed period.

SmileTrack's in-app deletion removes the specified active data it controls; it does not send a per-scan deletion request for OpenAI abuse-monitoring records. Setting store:false must not be understood as deleting all provider-held records or bypassing their retention rules. Contact support@smiletrack.cc for help with a pending deletion or a privacy request.

Sharing, sales, and tracking

We do not sell your personal information. SmileTrack does not use your information for third-party advertising or cross-app tracking. Information is shared with the service providers described above, when you direct us to share it, or when disclosure is required to comply with law, protect users, or defend the service. Sharing of API inputs and outputs, evaluation/fine-tuning data, and model feedback for OpenAI model improvement is disabled in the OpenAI organization used by SmileTrack.

Security

We use reasonable technical and organizational measures intended to protect your information, including authenticated access and user-scoped storage rules. No online service can guarantee absolute security, so please use a strong, unique password and protect access to your device and email account.

Your choices and rights

You can access saved scans in the app, delete scans or account data, sign out, and choose whether to submit a photo for analysis. Depending on where you live, you may also have legal rights to request access, correction, deletion, restriction, or a copy of certain personal information. Contact us to make a request.

Children

SmileTrack is not directed to children under 13. If local law requires parental or guardian consent for a minor to use the service, the minor should use SmileTrack only with that consent. If you believe a child provided information without appropriate permission, contact us.

Health and medical disclaimer

Smile photos and analysis results may be considered sensitive or health-related information. SmileTrack describes visible differences between photographs and does not provide medical or dental advice. Results may be affected by photo conditions and should not be used to make treatment decisions.

Policy updates

We may update this policy as SmileTrack changes. We will post the revised policy here and update the effective date. If a change is material, we may also provide notice in the app or by another appropriate method.

Contact

For privacy questions, requests, or complaints, email support@smiletrack.cc.