Privacy Policy

KeyClock LLC (“KeyClock,” “we,” “us,” or “our”) operates the KeyClock web application and website at key-clock.com (the “Service”). For privacy questions, account requests, or support, contact us at info@key-clock.com.

This Privacy Policy describes how KeyClock collects, uses, and shares personal information in connection with the Service. It distinguishes what KeyClock does itself from what our service providers do on their own behalf. It does not describe the practices of our providers — Stripe, Base44, AudD, and Google — each of which has its own privacy policy linked where relevant; we encourage you to review them.

This Policy does not apply to information you provide directly to a provider (for example, payment details you enter into Stripe Checkout).

• ·Account and authentication information: your email address. If you sign in with Google, we receive the name and email Google returns for your account.
• ·Age-screening information: your date of birth, collected at registration to determine whether you are eligible to use KeyClock and whether parent or legal guardian permission is required. The full date of birth is processed transiently to make that determination and is not retained; only the resulting minimum age-status (“eligible adult,” “pending guardian permission,” or “rejected underage”) and, for pending statuses, a recheck date are stored, associated with your account. A rejected or pending status is retained as a restriction marker and cannot be removed by self-service re-screening.
• ·Profile and preferences: your primary instrument, transposition key, voice and stability settings, onboarding state, and other choices you configure in Settings.
• ·Detection and practice data: detected concert key, scale, confidence, accepted notes, clock position, and transposed key; practice session and history records; and validation/QA records, which may include the filename of audio you upload, audio-quality metrics, and the notes you accept.
• ·Song-recognition information: when you enable and consent to song identification, the recognized title, artist, album, artwork, release date, streaming links, and provider track identifiers (such as an ISRC, Spotify ID, or Apple Music ID), along with any song name you add.
• ·Audio from your microphone or uploads: processed in your browser for key detection. It is sent outside your device only when you enable and consent to song identification.
• ·Billing and subscription metadata: limited identifiers and status we receive from Stripe (for example, Stripe customer, subscription, and price identifiers; billing interval; subscription status; trial and period dates; cancellation state; and webhook event identifiers and hashes).
• ·Support communications: the contents of emails you send to info@key-clock.com.
• ·Technical and platform data: session and authentication data and platform logs managed by our hosting provider, Base44; and your song-identification consent preference, which is stored in your browser’s local storage.

• ·Directly from you (your account, uploads, settings, and emails).
• ·Generated in your browser during key detection and practice.
• ·From authentication providers (such as Google).
• ·From service providers (Stripe subscription events, AudD recognition results, and the Base44 platform).

We use your information to:

• ·Provide the Service — key detection, transposition, practice tools, history, and voice output.
• ·Manage your account, preferences, and onboarding.
• ·Provide optional song identification when you enable and consent to it.
• ·Process subscriptions, trials, renewals, cancellations, and billing-portal access through Stripe.
• ·Respond to support and privacy requests.
• ·Maintain security, prevent fraud and abuse, and comply with legal obligations.
• ·Determine age eligibility and whether parent or legal guardian permission is required before allowing account use, trial, or checkout.

Where a law such as the GDPR or UK GDPR requires a legal basis for processing, we rely on the performance of our contract with you, your consent, our legitimate interests, or compliance with a legal obligation, as applicable. You can withdraw consent for processing that depends on it (such as song identification) without affecting the lawfulness of processing that already occurred.

Key detection is on-device. Microphone audio and uploaded files are analyzed in your browser using digital signal processing. This audio is not uploaded for key detection.

Song identification is optional and consent-based. When you enable song identification in Settings and grant consent, a short audio clip or uploaded file is sent to our backend function and forwarded to AudD for recognition. We send a neutral filename (not your original filename). Our backend discards the audio after the recognition request; we do not store the audio file in our storage for this purpose. How AudD handles audio after it reaches AudD is governed by AudD’s own practices.

Song-identification consent is separate from your browser’s microphone permission. Only your consent choice (granted or denied) is stored in your browser. You can withdraw consent at any time in Settings; withdrawal stops future identification but does not affect prior processing.

KeyClock was built with AI-assisted development tools; that is separate from how the Service works while you use it.

At runtime, key detection, transposition, confidence scores, and voice output are produced by deterministic digital signal-processing and music-theory algorithms, not by generative AI. We do not guarantee that musical results are correct.

KeyClock does not use your audio recordings, detection results, or personal information to train its own models.

We have not verified whether our service providers use data they process for us to train AI models; their practices are described in their own policies. We do not represent that recordings or personal information are never used for AI training by providers.

• ·Stripe — payment processing, Checkout, the Billing Portal, subscription management, and webhooks. Stripe receives your payment information and subscription metadata. Stripe Privacy Policy.
• ·Base44, Inc. — hosting, database, authentication, and platform services. Base44 Privacy Policy · Data Processing Addendum.
• ·AudD — optional song identification. audd.io.
• ·Google — optional Google sign-in, and fonts loaded from Google’s servers. Google Privacy Policy.

Service providers need certain information to operate the Service, so we do not state that information is never shared. We may also disclose information when required by law, to protect rights or safety, or in connection with a business transfer (such as a merger, acquisition, or sale of assets).

Stripe handles payment information (such as card details) through Stripe Checkout and the Stripe Billing Portal. KeyClock does not receive or store your full card number or security code; we receive only limited subscription and billing metadata described above. Stripe’s handling of your data is described in its privacy policy.

• ·Local storage: your song-identification consent preference.
• ·Cookies and authentication tokens set by the Base44 platform for session management.
• ·Google Fonts are fetched from Google’s servers when pages load.

KeyClock itself does not use advertising trackers in the Service, and no in-app analytics tracking calls were found in the inspected source code. Whether a provider operates analytics, telemetry, or logging that captures app usage is governed by that provider’s practices; we have not independently verified it.

We keep your information while your account is active and as long as needed to provide the Service. You can delete individual detected-song records from History within the app. Other record types do not have a self-service delete control in this version; you may request deletion by contacting info@key-clock.com. Full account deletion is not currently a self-service feature; we will act on verifiable requests to the extent we are able.

Date of birth and age screening. We process your date of birth only to determine your age-screening outcome; we do not retain the full date of birth. We store only the minimum resulting status (“eligible adult,” “pending guardian permission,” or “rejected underage”) and, for pending statuses, a recheck date, associated with your account. Age-screening status is kept until you request correction or deletion or your account is deleted. A rejected-underage or pending-guardian status is retained as a restriction marker so the account cannot regain access by self-reporting a different age; it can only be changed through our controlled review process. We do not retain the full rejected date of birth.

How long our service providers retain data they process for us, including server backups and logs, is governed by their own policies; we have not independently verified provider retention. Where retention is required by law (for example, billing and accounting records), we may retain information as permitted or required.

Depending on where you live, you may have rights to access, correct, delete, or export (port) your information; withdraw consent; object to certain processing; and complain to a supervisory authority. For example, some U.S. state laws and the GDPR/UK GDPR set specific response deadlines (commonly 30–45 days) and allow a short extension where justified, with notice to you.

How to make a request. Email info@key-clock.com with your request. To verify your identity we will use only the information necessary to do so (for example, the email address on your account). We will confirm receipt, review the request, and respond or take action within the deadline required by the law that applies to you. If a permitted extension is necessary, we will notify you of the extension and the reason. We do not charge a fee unless permitted by law.

Account deletion. Full account deletion is not currently a self-service feature. You can delete individual detected-song records from History within the app. For broader deletion, contact info@key-clock.com and we will act on verifiable requests to the extent we are able, subject to legal and provider backup-retention limitations described above.

Withdrawing consent. Withdrawing consent for song identification stops future identification but does not affect prior processing.

If you access the Service from outside the United States, your information may be processed in the United States and by providers in other regions. We have not independently verified the transfer mechanisms used by each provider. Base44’s documentation states it uses approved transfer mechanisms such as adequacy, Standard Contractual Clauses, or the Data Privacy Framework for its vendors (see the Base44 DPA). We do not represent that any particular transfer mechanism applies to every provider.

The Service is not intended for children under 13, and we do not knowingly collect personal information from children under 13. Users who are at least 13 but under 18 may use the Service only with the permission of a parent or legal guardian. We do not treat a user’s self-confirmation as verified parental consent. If you believe a child under 13 has provided us information, contact us so we can delete it.

At registration we ask for your date of birth and use it to determine eligibility. This is a self-reported date of birth; we do not verify age, and a self-reported date alone is not verified parental consent. Users who self-report as 13–17 are placed in a pending state that requires parent or legal guardian permission before they can use the Service or start a trial or checkout; that guardian-permission process is not yet implemented, so such users cannot currently proceed. Users who self-report as under 13 are not allowed to register. Because age is self-reported, these controls do not guarantee that a minor cannot misstate their age, and they do not establish worldwide legal compliance.

We collect your date of birth at registration to determine whether you are eligible to use KeyClock and whether parent or legal guardian permission is required. The full date of birth is processed transiently on our servers to compute an age-screening outcome and is not retained. We store only the minimum resulting status associated with your account — for example, “eligible adult” or “pending guardian permission” — and, for pending statuses, a future recheck date.

Age is self-reported and is not verified against any identity document; a self-reported date of birth is not verified age, and the agreement checkbox is not verified parental permission. Users who self-report as 13–17 are placed in a pending state and cannot use the Service or start a trial or checkout until a parent or legal guardian permission process is completed; that process is not yet implemented, so such users cannot currently proceed. Users who self-report as under 13 are not allowed to register; their rejected-underage status is retained as a restriction marker (without the date of birth) so the account cannot regain access by later self-reporting an adult age. A pending or rejected status cannot be removed by self-service re-screening; correction requires our controlled review process (contact info@key-clock.com).

We do not place your date of birth in URLs, analytics events, logs, public profiles, payment metadata, or song-recognition requests, and we do not store it in your browser. If your age-screening status is incorrect, you may request correction by contacting info@key-clock.com. Because age is self-reported, these controls do not establish worldwide legal compliance.

Accounts that existed before age screening was introduced retain their existing access without being asked for a date of birth and are not given an age-screening record. This grandfathering is based on your account creation date (which we already store), not a self-reported age, and it does not mark those accounts as screened adults.

We use reasonable measures including HTTPS, server-side secret management (API keys are not exposed to the browser), per-user row-level access isolation so each user sees only their own records, consent gating and subscription checks for song identification, and a neutral filename when forwarding audio for recognition. Payment card data is handled by Stripe, not stored by us. No system is perfectly secure, and we do not guarantee absolute security.

KeyClock does not sell your personal information. We share information with service providers as described above, and may disclose it as required by law or in connection with a business transfer. Whether a particular law treats one of these disclosures as a “sale” or “sharing” depends on that law’s definitions; we have not independently verified that classification for every jurisdiction.

We may update this Privacy Policy. We will post the current version with its effective date. For material changes, we will provide notice in the Service or by other reasonable means where required.