This Privacy Policy (the “Policy”) describes the scope, purposes and methods of information processing by Pitchee Project (“we”, “us” or “our”) when providing its iOS application, Android application and websites, and the controls available to you. Please read it before using the relevant features.
Notice: iOS and Android voice analysis takes place on your device; the hosted web voice experience is processed by the website server. Application history, system backups and copies you export have different retention arrangements. Please review Sections 3–6 in particular.
1. Scope
1.1 This Policy applies to Pitchee for iOS, Pitchee for Android, pitchee.dev and articles.pitchee.dev, as published and maintained by Pitchee Project (collectively, the “Products”). It distinguishes on-device application processing, operating-system services and website server processing.
1.2 The Products’ core voice analysis and reading features do not require a Pitchee account. Providers of third-party modifications, independent applications integrating Core, and self-hosted services are responsible for explaining their own information handling.
1.3 This Policy describes processing associated with features offered on each platform. Some features are available only in particular versions or on certain devices; availability and system permissions depend on the version and device you use.
2. Information processed and purposes
2.1Audio and analysis information. When you choose to record, monitor pitch or analyze your voice, the Products process microphone audio, sampling parameters and derived pitch, duration, timbre and scoring results to provide feedback, playback and historical trends. Versions offering the relevant features may also save your selected practice direction, goals and self-assessment feedback. Voice and practice content may contain personal information about you or others; avoid recording unrelated private content.
2.2Preferences and reading information. Applications may store language, theme, practice preferences, dates of use, selected reading passages and custom text on your device. The website stores language, bookmarks, the last article read, text size and reading theme in your current browser. This information supports your chosen features. The current implementation does not synchronize it between devices through a Pitchee account.
2.3Access and network information. When you visit the websites, check for or download Android updates, or open external links, the relevant servers receive basic connection information such as your IP address, requested path and request headers. Hosting and network services may produce access or error logs to deliver the service, investigate faults and handle abnormal requests.
2.4Optional local iOS diagnostics. In iOS versions offering this feature, enabling it allows the application to store on-device summaries of analysis outcomes, duration and latency ranges, as well as categorized counts and coarse differences for score comparisons. It is disabled by default. Summaries may also contain application and model version identifiers. The current implementation does not upload these summaries or include raw recordings or individual self-assessment text in them.
2.5Local operational logs. Android analysis may record scores and usable speech duration in device system logs; iOS may also log local operational errors. The current Products do not integrate advertising tracking, third-party behavioral analytics or crash-telemetry SDKs. The website does not use tracking cookies.
2.6Information you submit. Text, attachments and account information you submit through project pages, external platforms or system sharing are handled by the selected recipient under its own rules. Please provide only information necessary to address your request.
3. Permissions and audio processing
3.1Microphone permission. Recording or live monitoring on iOS, Android and the web requires the applicable system or browser microphone permission. Audio is captured only after you activate the relevant feature and permission is granted. Refusing or revoking permission prevents microphone-dependent features from operating but does not prevent reading or sample features that require no recording.
3.2On-device iOS and Android analysis. Both applications analyze audio using Core and models on the device. They do not upload recordings to Pitchee servers to perform that analysis. “On-device analysis” does not exclude exports or sharing you initiate, or operating-system backups and device transfers, as described in Sections 4 and 5.
3.3Web voice experience. The hosted website sends audio, sampling parameters and the selected analysis reference to the website’s Core server. Recorded analysis clips are limited to 15 seconds. The current Core service processes audio in memory without writing recordings to files, forwarding them to third-party audio services, or logging audio content or analysis values. This does not mean hosting or proxy layers produce no basic access logs.
3.4iOS captions and report export. In versions offering local captions, that feature requires speech-recognition permission and uses on-device recognition, without a cloud-recognition fallback when unsupported. Captions are not stored as persistent recording history. Saving a report image to Photos requests add-only photo permission. Exporting to Files or sharing with another application uses the system picker.
3.5Android update installation. Android version checks and update downloads require a network connection. Installing an APK obtained from GitHub may require system permission to install applications from that source. This permission supports the update installation you select and is not used to capture audio.
3.6Stopping capture and revoking permission. You may stop recording or monitoring and revoke permission through system or browser settings. The website stops microphone capture when you finish or cancel recording, move the page into the background, or leave it. Stopping capture does not automatically revoke permission saved by the system.
4. Storage, retention and backups
4.1iOS audio and history. Live pitch and spectrum monitoring keeps up to the most recent 60 seconds of audio in memory and clears it when you leave the monitor; this audio is not saved in recording history. Ordinary scoring recordings use temporary audio files, with cleanup after analysis or cancellation. Application temporary recordings left by an interrupted session are cleaned up on a subsequent launch. Versions offering A/B playback may retain clips during the practice session until it ends or the relevant cleanup occurs. Analysis results are automatically saved in local application history, which currently has no fixed automatic expiry and does not contain raw audio as a history field.
4.2Android audio and history. After a successful analysis, the application saves a recording copy, an analysis result file, dates and scores in private storage for playback and review. Some live-monitoring audio exists only in short in-memory buffers, while summaries such as average pitch may be stored separately. The number of entries shown or indexed does not mean every associated file has been automatically deleted.
4.3System backups and transfers. The current iOS implementation disables application CloudKit synchronization and marks its private support files and preferences directories as excluded from system backup. This is not a guarantee about every system migration mechanism or copies you export. Android currently allows system backup and device transfer of application files and preferences, potentially including saved recordings and results. Whether a backup occurs, where it is stored and how long it is retained depend on your device, system service provider and settings.
4.4Website data. Website Core does not maintain a server-side recording or analysis history for users to retrieve. Web results are shown on the current page. Browser preferences, reading records and bookmarks may remain after the browser closes until you or the browser clear them.
4.5Optional iOS diagnostic summaries. Local diagnostic and score-comparison summaries use seven-day periods and reset on the next state refresh after a period expires. Disabling or clearing these features removes their summaries, while current-period quota counters and period-boundary information may remain to enforce participation limits. This is not a guarantee that all diagnostic state is completely erased at a fixed time.
4.6Exported files and operational logs. Copies exported to Photos, Files, other applications or cloud file providers are retained according to the selected location and service and must be managed separately. System, hosting or proxy log retention depends on actual operating configuration and applicable law. On-device or in-memory audio processing should not be understood to mean that no information is retained.
5. Network features and third-party services
5.1Android version updates. Automatic update checks are enabled by default in the current Android version and may request a release list from GitHub at launch. You can disable them in Settings or check manually. Requests contain ordinary connection information and an application-identifying header, without recordings, analysis results or custom reading text. Choosing to download an update retrieves the package from its release asset URL.
5.2iOS content and system services. Current iOS article resources are bundled with the application. It does not upload recordings or synchronize history through its own account service. Apple system permissions, sharing, Photos and Files remain subject to your device settings and the relevant service’s rules.
5.3External links and intentional sharing. Visiting external websites such as GitHub, submitting feedback or selecting a system-share recipient establishes a direct interaction with that platform or recipient. Its own policies govern collection, retention, publication and deletion. This Policy does not replace external platforms’ privacy policies.
5.4Service providers. Website hosting and network infrastructure may process connection information needed to deliver the service. Android system backups may be handled by device or system service providers. The Products’ on-device analysis and current web Core do not use third-party remote audio analysis interfaces.
6. Your rights and controls
6.1Permissions and feature choices. You may refuse or revoke microphone, speech-recognition and add-only photo permissions in system settings, and stop the related features. You may also disable Android automatic update checks or optional local iOS diagnostics. Revoking permission does not automatically delete existing local history, exported files or system backups.
6.2Android local records. The history screen supports deletion of selected analyses and their associated files. This does not clear every separately stored metric or other application data. To clear all local application storage, use Android’s system application-storage controls. Manage system backups and transferred copies separately.
6.3iOS local data. You may adjust relevant preferences and disable or clear optional diagnostic summaries in the application. The current iOS version does not provide individual analysis-history deletion. You can use the system’s Delete App operation to remove local application data. Offload App may retain documents and data, and exported files or photos are not automatically removed.
6.4Browser data and exported copies. You may clear site data to remove browser preferences, reading records and bookmarks. Reports, images, files and backups already downloaded or shared must be deleted from their actual storage locations or recipient platforms separately.
6.5Information processing requests. To request access, correction, deletion or exercise other rights under applicable law concerning information about you, contact the project maintainers through Section 8. Data stored only on your device or in your browser generally requires the local controls described above. We do not operate a Pitchee account system for remotely retrieving that data.
7. Information security
7.1 The Products use private application storage, system permissions and applicable platform protections to manage data. The current iOS implementation applies system file protection to relevant private files. Website Core uses origin checks and limits on request size and processing resources to reduce unauthorized access and abnormal requests.
7.2 No transmission or storage method can guarantee absolute security. Use trusted devices and networks, and manage system permissions, device backups and exported files appropriately. Recordings, results and practice self-assessments may contain private information; choose shared content and recipients carefully.
8. Policy changes and contact
8.1 This page may be revised when Product features or information handling change. The date at the top identifies the latest revision. Please also consider the information provided with the application version you use.
8.3 For requests involving personal information, first agree on an appropriate communication method with the maintainers. Public issues, discussions and comments are not confidential channels. Do not post recordings, results, identity documents or other information you wish to keep private there.