1. Introduction
TPASS.calc (hereinafter referred to as "the Application") is developed by Cheng Ruei Hsu (hereinafter referred to as "we" or "us"). We are deeply committed to protecting your privacy and data security. This Privacy Policy explains how the Application handles your data and your privacy rights.
2. Core Data Storage and Collection Methods
The Application's core functionality uses a "Local-First" architecture, and your trips and settings stay on your device by default. The following are exceptions where necessary data leaves your device: automatic-detection usage statistics (counts only, can be turned off), corrections you agree to share and detection-error reports you send yourself in Section 3, route planning, map queries and Google Maps route import in Section 4 (sent to third-party services), voice parsing logs shared with your explicit consent in Section 5, and "Issue Reports and 1-on-1 Support" actively submitted by you in Section 6. Each section explains the content, purpose, identity linkage, and available controls:
- Local Storage: All trip records, favorite routes, TPASS cycle settings, and user preferences you create within the app are stored exclusively on your personal device (via SwiftData and UserDefaults).
- Apple Watch and Widgets: If you use the Apple Watch app or widgets, the app syncs your cycle statistics, quick-record items and pending suggestions to them: to Apple Watch through Apple's device-to-device transfer (WatchConnectivity), and to widgets through a shared container on the same device. This data only moves between your own devices and never passes through our servers.
- Developer Dashboard (Cloudflare): The usage statistics, corrections, detection-error reports, voice parsing logs, issue reports, website support forms and 1-on-1 Support content stored in our Apple CloudKit public database are copied every 15 minutes to our dashboard database (D1) on Cloudflare, and are used only internally by the developer to handle reports, debug and improve the Application. The copy includes each record's text fields and its CloudKit creator identifier, so it may contain the voice transcripts, support conversations, contact emails, station names and times described in Sections 3, 5 and 6. The location-track files in detection reports and support screenshots are not stored in this database; they are read from CloudKit only when the developer views them. Cloudflare is an infrastructure service provider processing data on our behalf, and the dashboard is restricted to designated accounts through Cloudflare Access. Backups in your private iCloud are not copied here.
3. Location, Motion Data and Automatic Trip Detection
Location While Using the App: When you use location while recording a trip, choosing a station, planning a route or logging a Missed Train, the app gets your current location once, to find nearby stations on your device and fill in the origin or destination, confirm you are near a station, or use it as the starting point of a route plan (see Section 4 for the coordinates sent to TDX). This only needs "While Using the App" permission, does not track you continuously, and your location is not uploaded to our servers.
"Automatic Trip Detection" is an optional feature that is off by default. It only works after you enable it and grant location permission:
- Detection Modes: Three levels are offered — "Off (default, no location activity)", "Only While Using the App (one-time foreground sampling)", and "Automatic Background Detection (requires 'Always' location permission; uses low-power Visit and Significant-Location-Change monitoring, not continuous precise tracking)".
- Processed On-Device: All waypoint matching and trip inference happen locally on your device. Apart from the two kinds of sharing you choose below, we do not upload your location or movement history to any server.
- On-Device Detection Log: To make detection more accurate and problems diagnosable, the app keeps a detection log for the last 14 days on your device, including the visit and location-change events delivered by the system (with coordinates), how each one was judged (including a summary of the motion and step-count results), the state of location monitoring, the suggestions produced and what you did with them. This log stays on your device and is never uploaded automatically; it is removed when you turn off detection or delete the app, and entries older than 14 days are deleted automatically.
- Motion and Steps (optional): If you allow "Motion & Fitness" access, the app reads the activity types (such as walking, cycling or riding in a vehicle) and step counts recorded by your device, to tell whether a movement was a walk or a ride and whether you are still on board while a bus is stopped along the way. The raw motion and step records are read only on your device and are never uploaded; only the results and a step-count summary are written into the on-device detection log above, and they are sent along with that period's records when you send a detection-error report. You can turn off "Filter false positives with walking data" in Auto Trip Detection settings or revoke the permission in iOS Settings; detection still works, but makes more mistakes.
- Correction Sharing (optional, requires your consent): On the last page of the Auto Trip Detection introduction, or the first time you change a suggestion (its mode, stations or route, merging two suggestions, or undoing an automatic log), the app asks whether to share such corrections; nothing is uploaded until you tap "Agree and finish" or "Agree and share". After you agree, only suggestions you changed are sent, including: the mode, station names and route that were detected versus what you finally logged, the full times of that trip, the type of change, how it was judged (such as distance moved, nearby candidate station names and distances, and the motion result), plus your region, app version and device model code (such as iPhone17,1, not a device identifier). Corrections contain no coordinates or movement tracks, although station names and times can still reflect roughly where you traveled. You can turn off "Share corrections" anytime in Auto Trip Detection settings.
- Detection-Error Reports (optional, sent by you each time): From the Auto Trip Detection page or its settings, tap "Report a detection problem" (or long-press a suggestion) to report a trip that was detected wrongly, or a period in which you rode but nothing was detected. Before sending, the app shows a map and the time range covered. Only after you tap "Agree and send report" are the detection records for that period (about 30 minutes before and after the trip, up to 6 hours for a missed trip), including precise locations, uploaded together with the state of location monitoring during that period (such as monitoring started, stopped or missing permission), your optional description, the logged trip you chose to fill in the time range when reporting a missed trip (its mode, stations and time), your region, app and iOS versions and device model code. Apart from the last monitoring state before the period begins, nothing outside that period is sent. A report ID is shown after sending. If you can use 1-on-1 Support, the report also opens a support case (see Section 6) so that we can reply to you directly.
- Usage Statistics (on by default, can be turned off): With Auto Trip Detection on, the app sends one entry per day with the previous day's usage counts, so we can understand how many people use it and how often detection is right, and improve it. This does not show a separate consent screen; you can turn it off in settings. It contains only the date, detection mode, region, app version, iOS version, and how many visit events were received and how many suggestions were produced, logged as-is, switched to another option on the suggestion, corrected, re-segmented, ignored, automatically logged, automatic logs undone, merged, and reports sent. It contains no station names, trip times, coordinates or movement tracks, and the app creates no identifier of its own; the number of users is counted from the creator identifier CloudKit records. You can turn off "Share usage statistics" anytime in Auto Trip Detection settings.
- Storage, Access and Identity: Usage statistics, corrections and reports are stored in our Apple CloudKit public database and copied to the developer dashboard described in Section 2. Other users cannot read them; only the developer with administrative access can, to analyze and improve detection accuracy. Apart from Cloudflare acting on our behalf as described in Section 2, we do not transfer them to other third parties or use them for advertising or cross-app tracking. We do not add Apple ID, device ID, email or other identifier fields, and we do not use this data to identify you; however, CloudKit itself records a creator identifier (used only to count users for usage statistics), so we do not claim this data can never be linked to your identity.
- Retention and Deletion: Usage statistics, corrections and reports are kept until analysis and verification of the improvements are complete, and deleted after at most 12 months, including the copies in CloudKit and the developer dashboard. To look up or delete a report you sent, contact us in the app through "Settings → Issue Report" or 1-on-1 Support with the report ID, or email tpasscalc@mail.rayisgenius.cc; for corrections, include the approximate trip time and stations. We will handle it after verification.
- Suggestions Only: Each detected trip is merely a suggestion pending your review, and is written into your records only after you confirm or edit it.
- Turn Off Anytime: You can disable it in the Automatic Detection settings within the app's "Advanced" tab, or adjust/revoke location permission in iOS Settings.
4. Route Planning, Map Queries and Route Import (Third-Party Services)
"Route Planning" and "Google Maps Route Import" are optional features. When you use them, the Application sends the necessary queries to the following third-party services to obtain places and routes:
- Apple Maps (MapKit): When you search for origin/destination places, your typed text and preferred region are sent to Apple for place search, subject to Apple's Privacy Policy.
- Taiwan's Transport Data eXchange (TDX): To plan multi-modal routes, the coordinates of your selected origin/destination (including when you choose your current location as the starting point) are sent to the TDX API (tdx.transportdata.tw) to retrieve routes and schedules, subject to TDX's terms of service.
- Google Maps (Route Import): When you share a transit route from Google Maps to the Application, the app (or its share sheet) reads that shared link's route directly from Google's servers. Google receives the link (which contains the origin and destination you chose in Google Maps) and the information needed for the connection, such as your IP address. The request carries no cookies and does not sign in to your Google account. The retrieved route is stored only on your device. This query is subject to Google's Privacy Policy.
These queries contain only the place text, coordinates or shared link needed to complete the planning or import, and do not include your name, Apple ID, or other identifying information. We also do not retain your query history on our own external servers.
5. Voice Recognition and Optional Parsing-Log Sharing
"Voice Quick Record" works without sharing data. On a new install, its Info sheet initially recommends sharing as enabled, but the Application uploads nothing until you explicitly tap "Agree and Continue":
- Permission Requests: This feature requires your "Microphone" and "Speech Recognition" permissions to function. Your voice audio is processed by Apple's speech recognition technology (SFSpeechRecognizer): when your device is offline, recognition always happens on the device; when online, the audio may be sent to Apple's servers for recognition, subject to Apple's Privacy Policy. The app does not keep recordings.
- Consent Before Sharing: The initially enabled preference is a recommendation, not consent. It takes effect only after you tap "Agree and Continue." To decline sharing, close the sheet from the top-left; Voice Quick Record remains available.
- What Is Shared: After consent, successful, failed, and abandoned voice-parsing attempts may be uploaded to improve the natural-language parser. Records may contain the original transcript, parsed and final results, correction fields, failure reason, confidence data, app or rules versions, and technical details of the parsing process: device model code (e.g. iPhone17,1, not a device identifier), iOS version, the TPASS region of your active plan, the recognition engine used and the time each step took, your editing activity on the result screen (time spent and which fields you changed), and a code generated at random each time the voice screen opens to link retries within the same session (not linked to your identity or device). Shared content does not include audio recordings.
- Private Cloud Compute (iOS 27 or later): If you use "Enhanced Recognition" or choose Private Cloud Compute as the recognition engine, the transcribed text (not audio) is sent to Apple's Private Cloud Compute for parsing. This processing is performed by Apple and is separate from parsing-log sharing; you can turn it off from the engine menu on the voice screen.
- Identity and Sensitive Content: We do not add custom Apple ID, device ID, or email fields. However, dictated text can itself contain names, addresses, or other personal information. Logs are stored in our CloudKit public database and copied to the developer dashboard described in Section 2, and CloudKit may retain system creator metadata. We therefore do not claim that every sample is fully anonymous. Please do not dictate sensitive information.
- Access, Retention, and Deletion: Logs are available only to authorized developers for parsing-quality analysis and are retained only as long as needed for model improvement and quality validation, after which they are deleted or de-identified. To request access to or deletion of a previously shared log, email tpasscalc@mail.rayisgenius.cc with an approximate upload time and a transcript fragment that can identify it.
- Turn Off Anytime: Disable future sharing under "Voice Quick Record → Info → Privacy."
6. Issue Reports and 1-on-1 Support
The following support content is uploaded only when you actively submit it and is read and processed by us (the developer):
- Report an Issue (all users): the description you submit, an optional contact email, and your app and iOS versions attached automatically. When you report a voice recognition problem, the voice parsing log you selected (transcript and parsed result, no audio; same content as Section 5) is attached as well.
- Website support form: the name, email address, issue type and message you submit on the website's Support page, plus the optional app and iOS versions (pre-filled from your browser on iPhone and editable), are passed through our website server on Cloudflare and saved as an issue report as described above, with the same storage location and access scope; the website server itself does not keep a copy. To prevent automated abuse, the form uses Cloudflare Turnstile, which processes the browser and connection information needed for verification; your IP address is used only for verification and rate limiting and is not written into the report. Website reports do not go through an iCloud account and therefore contain no iCloud identifier. To look up or delete one, email us with the report ID shown after submission.
- 1-on-1 Support: the case subject, the full conversation, an optional contact email, optional screenshot attachments, and your app and iOS versions attached automatically.
- Screenshot attachments (optional): in a 1-on-1 Support conversation you may attach screenshots, and we may reply with screenshots to explain a step. Images are always re-encoded on your device before upload, which strips capture location (GPS), device model and other metadata. Note that the screenshot itself may still show your trip history, stops and times, so please review it before sending. We receive an image only when you attach it yourself; the app uses the system photo picker and does not need or request access to your photo library.
- Detection reports and voice logs (optional): in 1-on-1 Support you can attach a detection-error report from Section 3 (including precise locations for the period you reviewed on the map), or your most recent voice parsing log (transcript and parsed result, no audio; same content as Section 5). The app keeps up to 30 voice parsing logs from the last 14 days only on your device; even if you have not turned on sharing in Section 5, they are uploaded only when you choose to attach or report one yourself. Attached content is linked to that support case.
- Where it is stored: in our Apple CloudKit public database, with text content copied to our developer dashboard on Cloudflare as described in Section 2; screenshots and the location-track files in detection reports are not stored in the dashboard database. Apart from Cloudflare acting on our behalf, we do not transfer it to any other third-party server, and never use it for advertising or cross-app tracking.
- Link to your identity: so that you see only your own cases and we can reply to the right person, each case carries a hash derived from your iCloud user identifier; CloudKit itself also records a creator identifier. Support content is therefore data linked to your identity, and we do not claim it is anonymous.
- Who can access it: other users cannot read your cases. Only developers holding support-admin permission can read and reply.
- Your control: open any case under "Settings → Issue Report → 1-on-1 Support" in the app and choose Delete this case from the top-right menu. The entire conversation, including any screenshots in it, is deleted permanently, along with any detection reports and voice logs uploaded only for that case, and becomes unreadable to us as well. The copy in the developer dashboard is removed by a later automatic check, usually within 1 day.
- Retention: case content is kept until you delete it, or until we have confirmed the case is resolved and no longer needs to be retained.
- Please do not share sensitive information: support conversations are free text and may include screenshots. Please do not include passwords, credit card numbers, or national ID numbers in either. We will never ask you for such information.
7. Advanced Features and In-App Purchases
All features of the Application, including advanced features such as Route Planning and Automatic Trip Detection, are currently free and require no payment. Purchase-related data is handled as follows:
- Payment Handled by Apple: Any in-app purchase is made and charged through the Apple App Store (StoreKit). We do not access or store your credit card or other payment information.
- Purchase Status: If you made an in-app purchase previously, the Application determines its status on your device using verified StoreKit transactions and entitlements provided by Apple. We do not create TPASS.calc member accounts, nor do we access your complete payment details or payment method.
- Support Diagnostics: When you actively create a 1-on-1 Support case, the case includes the current purchase entitlement status, entitlement source, and app installation channel so that we can diagnose TestFlight, Sandbox, or production App Store purchase issues. This diagnostic information is stored with the support case in Apple CloudKit and the developer dashboard described in Section 2, and is retained and deleted as described in Section 6.
- Manage and Cancel: Earlier purchases can be managed or cancelled anytime via iOS "Settings → Apple ID → Subscriptions". See the Terms of Use for details.
8. Cloud Backup (Apple iCloud)
The Application does not use any third-party authentication services that require account registration (no login mechanism). We only provide backup services supported by Apple's native platform:
- Apple iCloud (CloudKit): If you choose to enable cloud backup, your data will be encrypted and synchronized to your personal iCloud Private Database. We (the developer) have absolutely no ability to access, read, or modify any data stored in your personal iCloud space.
- Service Configuration Read: The Application reads necessary service configuration (such as the service key required for Route Planning) from our CloudKit public database. This particular operation is read-only and does not involve or upload any of your personal data.
- Writes to the public database: When you choose to use "Report an Issue" or "1-on-1 Support," send a detection-error report in Section 3, or consent to correction sharing in Section 3 or voice parsing-log sharing in Section 5, the relevant content is written to our CloudKit public database and is readable by us. With Auto Trip Detection on and "Share usage statistics" not turned off, the usage statistics in Section 3 are written as well. This content is copied to the developer dashboard described in Section 2.
- Announcement and Reply Notifications: If you turn on announcement notifications, or are waiting for our reply to an issue report or 1-on-1 Support case, the app creates a notification subscription in CloudKit, and new announcements or replies are delivered to your device through the Apple Push Notification service (APNs). The subscription only records which kind of notification to receive and does not upload your trip data; you can turn off the app's notifications in iOS Settings.
9. Purposes of Data Use
All your trip and operation records are used exclusively for functionality within the Application, including:
- Calculating the actual payment and discount amounts for TPASS plans.
- Generating personal commute data dashboards (monthly pass ROI, route rankings, etc.).
- Providing daily reminders and cycle notifications (scheduled locally on your device; for announcement and support-reply notifications, see Section 8).
- Improving the accuracy of automatic trip detection (usage statistics, the corrections you choose to share and the detection-error reports you send; see Section 3).
We will never sell, rent, or share your data with any third party for commercial or marketing purposes.
10. Data Security
To protect your privacy, we implement the following security measures:
- Local Encryption: All data stored locally on your device is protected by iOS's built-in encryption mechanisms.
- Transmission Encryption: When data is synchronized to iCloud, it is protected using TLS/SSL encryption protocols to ensure transmission security.
- Dashboard Access Control: The developer dashboard described in Section 2 can only be entered after account verification by Cloudflare Access, and the dashboard's own code verifies the sign-in credential again.
- Data Minimization: Voice parsing logs do not include audio recordings or custom Apple ID, device ID, or email fields, but transcripts may contain dictated information as explained in Section 5. Automatic-detection corrections contain no coordinates, and detection-error reports include only the period you reviewed and chose; see Section 3.
11. Data Deletion and User Control
You can manage local data, private iCloud data, and the public-database content described in this policy through in-app controls or by contacting us:
- Clear Local Data: You can delete all trip records and settings stored locally by using the one-click clear option in the app's Settings page.
- Delete Cloud Backup: You can directly delete your CloudKit backup data stored in your iCloud space through the app's Settings page.
- Export Data: Anytime in Settings, you can export your trips as a CSV file, or export a full data archive with your trips, cycles, favorite routes and preferences, for offline backup or cross-device migration.
- Access Your Data: You can view all personal data stored in the application at any time.
- Stop or Delete Voice Sharing: Stop new sharing under "Voice Quick Record → Info → Privacy." Request access to or deletion of previously shared samples as described in Section 5.
- Stop or Delete Auto-Detection Sharing: Turn off "Share usage statistics" and "Share corrections" in Auto Trip Detection settings; detection-error reports are uploaded only when you send one yourself. Request access to or deletion of corrections and reports you have sent as described in Section 3.
12. Notice Under Taiwan's Personal Data Protection Act
Under Taiwan's Personal Data Protection Act, we give the following notice about the personal data we collect. Sections 2 to 8 govern the details of each service:
- Collector: Cheng Ruei Hsu, the developer of the Application.
- Purposes: providing and maintaining the Application, handling issue reports and support, and improving the accuracy of automatic detection and voice parsing.
- Categories of personal data: the contact email and name you provide, support conversations and screenshots, voice transcripts, station names and trip times, the precise locations in detection reports you send, and the iCloud creator identifier and hashes derived from it.
- Period of use: the retention periods described in Sections 3, 5 and 6.
- Area of use: data centers of Apple and Cloudflare, which may be located outside Taiwan.
- Recipients: the developer, and Apple and Cloudflare processing data on our behalf. Data may be provided to competent authorities when required by law.
- Method of use: electronic storage, search, statistics and replies.
- Your rights: you may request to inquire about or review, obtain a copy of, supplement or correct, stop the collection, processing or use of, and delete your personal data. Contact us by the email in Section 16. Because the Application has no accounts, we may ask for a report ID, an approximate time or a content fragment to find the data.
- If you do not provide data: the data above is all optional. Without it, core features such as calculating, recording and statistics still work; only the related support, reporting or sharing features are unavailable.
13. Minors
The Application does not ask for your age and has no registration, so we cannot tell whether a user is an adult. If you are under 18, please read this policy with your legal guardian before deciding whether to use features that send data off your device, such as voice-log sharing, issue reports and 1-on-1 Support, and avoid giving your name, school, address or other personal details in them. Legal guardians may request access to or deletion of related data as described in Section 12.
14. Cookies and Tracking
The Application does not use cookies or any similar tracking mechanisms. We do not use third-party tracking tools, advertising technologies, or analytics platforms (such as Google Analytics) to monitor your behavior; the automatic-detection usage statistics described in Section 3 are counts only, stored in our own CloudKit and the developer dashboard described in Section 2, and can be turned off.
15. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect legal changes or updates to our practices. Any significant changes will be notified through the Application or announced on our official website. Your continued use of the Application signifies your acceptance of the updated Privacy Policy.
16. Contact Us
If you have any questions or suggestions regarding this Privacy Policy, please feel free to contact us:
Email: tpasscalc@mail.rayisgenius.cc