Decibel Privacy Policy

Last updated: October 6, 2026

Aksoy Labs operates Decibel Meter (the “App”). This policy explains the App’s local records, purchase services, analytics and sharing. It applies to Decibel, including its TestFlight versions, and not to our separate Intake app.

Sections marked 2.1 describe Decibel’s 2.1 releases; earlier TestFlight builds may differ. Earlier installed versions can behave differently, as explained below. Updating the App does not automatically delete information already held by a service provider.

1. Microphone, camera and local records

Decibel uses microphone access when you start sound measurement or a noise-monitoring feature. Version 2.1 processes sound on your device. Depending on the measurement mode, it uses a temporary local audio recording for metering and attempts to delete that temporary file after normal recorder release. Interrupted sessions or deletion failures may leave temporary files until cleanup. Saved measurements and Noise log reports contain sound-level data rather than an audio recording.

Camera features can create photos and videos, including video audio, with a sound-level overlay. Photos, videos, reports, names, notes and other saved app records are processed and stored on your device. Version 2.1 does not automatically upload these files through its measurement, camera or export features. It does not create snoring-highlight audio clips or provide a medical diagnosis.

Local records are separate from the purchase and usage information sent to service providers below. Keeping a report on your device does not mean that no information about using the App is collected.

2. Purchases and RevenueCat

Apple processes App Store purchases. RevenueCat receives a persistent app user identifier and purchase information, including product and transaction details, subscription status and access rights. We use this information to unlock Pro, restore valid purchases, understand purchase performance and measure acquisition. We do not receive your payment card number through the App.

The app user identifier is pseudonymous: it identifies an app installation or customer record rather than requiring a named account. It is not anonymous. When Amplitude analytics is configured in a build, the RevenueCat identifier is associated with its analytics profile. RevenueCat also sends configured purchase lifecycle events to Amplitude.

Purchase options, local prices, introductory eligibility and renewal terms are shown before purchase. A one-time purchase and an auto-renewing subscription are different purchase types.

3. Usage analytics and technical information

When analytics is configured, we use Amplitude to understand feature use and technical failures. Version 2.1 sends a limited set of events, such as app opens, permission outcomes, measurement completion, saving, sharing, export, purchase and restore actions. Events can include success or failure, product and transaction information, price and currency, access status, app/build and device/operating-system information, language, storefront, and persistent user, device and session identifiers.

Purchase-screen events can identify the offer, placement and presentation variant. We use these to compare purchase presentations and improve the App. These records are associated with persistent identifiers and are therefore pseudonymous, not anonymous.

Starting with version 2.1.3: product-use analytics also records fixed app-control actions, such as opening or closing a tool, changing a control, starting or stopping an operation, retrying, saving and exporting. If you answer the optional purpose question, we send the selected category—tools/equipment, music/venue, noise at home, sleep environment or curiosity—and where you answered it. This explicit choice is associated with the existing analytics profile. Skipping the question sends no category. We do not upload free-text answers or retroactively upload purpose choices stored by earlier versions.

Tool interactions can identify feature use, including sleep and tone tools; they do not include hearing answers or results, sleep scores or journal contents. Version 2.1.3 does not add session replay, screenshots of your activity or indiscriminate automatic capture of interactions. Development and preview builds use a separate QA analytics project. TestFlight builds made with the production configuration can send client events to the production project; a test purchase is not evidence of a genuine paid sale.

Version 2.1 filters its outgoing usage events. They exclude measured sound levels and samples, measurement duration and calibration offsets, record names, notes, tags, report contents, media files and file paths. Detailed sleep and hearing results, scores and journal factors are excluded from this analytics transport. General navigation can still identify which tool was opened. The version 2.1 analytics configuration disables IP-based location resolution.

Earlier versions: historical analytics includes measurement values and durations, sleep activity and derived sleep results, hearing results and related preferences from earlier implementations. Earlier installed builds may continue using that implementation. The new filters do not erase historical provider records. Historical analytics also includes age or birth-year fields and approximate country, region and city derived from IP addresses. This is approximate network-based location, not evidence of GPS collection. Earlier analytics and app-launch services can also process device, session, network and app information.

4. Apple Ads attribution

Version 2.1 sends Apple’s standard AdServices attribution token to RevenueCat. RevenueCat uses it to request available Apple Ads attribution, such as campaign, ad group or keyword information, and associates the result with its customer and purchase records. We use this to understand which advertising brings installations and purchases. This is separate from the sound or media you measure.

This implementation does not collect the IDFA or request Apple’s detailed, ATT-authorized attribution. Standard attribution does not mean that no advertising information is collected. Our configured purchase and product-analytics integrations are RevenueCat and Amplitude; the Apple Ads integration supplies attribution for our own advertising.

5. Permissions, sharing and support

You do not need a named account to use version 2.1. It does not use GPS. A storefront country or interface language is not your physical location. Text you enter as a place name remains part of the local record unless you share it.

You choose when to share an image, report, photo or video, or save it to Photos. Your selected destination controls that copy and may upload or retain it under its own terms. App versions without a configured share-page address link to the App Store rather than hosting your measurement. If you use a Decibel measurement link, its URL can contain sound levels, measurement time and duration, an optional name and tag, and a short level trace. Anyone with the link can read those details; encoding is not encryption. Opening it sends the URL to our website hosting/CDN infrastructure, whose access logs may retain it. The share viewer decodes the link in your browser and does not add analytics, cookies or a measurement database. Avoid including sensitive names or other information in links you share.

Optional reminders in version 2.1 are scheduled locally. This implementation does not upload a remote push-notification token. You can manage microphone, camera, Photos and notification permissions in iOS Settings.

If you contact support@aksoylabs.com, we receive the message and information you choose to include. The in-app support action prepares an email draft with app/build, operating-system and language details; you decide whether to send it. Do not include recordings or other sensitive information unless needed for your request.

6. Service providers and purposes

We use local data to provide the App’s tools; purchase information to validate and restore access; usage and technical information to understand product use and failures; attribution to measure our advertising; and support messages to respond to you.

Apple handles App Store transactions and platform services. RevenueCat handles purchase validation, access rights, purchase analytics and attribution. Amplitude processes configured product and purchase analytics. These providers process information off your device. Our Amplitude projects use its US region, so processing may occur outside your country. Their policies explain their practices.

7. Storage, deletion and your choices

You can delete local records in the App or remove the App. This does not automatically delete information held by Apple, RevenueCat or Amplitude, device backups, or files you exported or shared. Purchase records may be needed to restore access and handle transactions; historical analytics is separate from local app storage. We have not configured an automatic expiry period for Amplitude analytics. You can contact us to request deletion of information associated with your app use.

Contact support@aksoylabs.com with questions or requests concerning access, correction or deletion of information associated with your app use. Your rights depend on applicable law. We may need information sufficient to locate the relevant provider record; do not send payment credentials. Manage subscriptions through your Apple account. Removing the App does not cancel a subscription.

We take reasonable measures to protect information, but electronic storage and transmission cannot be guaranteed completely secure.

8. Children and policy changes

The App is not directed to children under 13. If you believe a child has provided personal information, contact us so we can review the request and take appropriate action.

We update this page when our practices change and revise the date above. Feature availability and data handling can differ by app version; check this policy when updating.

9. Contact

Aksoy Labs
support@aksoylabs.com
aksoylabs.com