Scope and who we are
Glows Ads LLC operates Clapps, an app studio based in Los Angeles, California. In this policy, “Clapps,” “we,” “us,” and “our” mean Glows Ads LLC. Clapps, SideReader, and the names of other apps we develop and identify as Clapps products are brands of Glows Ads LLC. This policy covers clapps.me, our apps that link to it, and related support. Glows Ads LLC is responsible for the personal information described here (the controller where that term applies). Contact us at hello@clapps.me.
SideReader is local-first and does not require a Clapps account. We do not automatically upload your scripts, recordings, takes, photos, or files to our servers. Optional measurement and information you deliberately send us are separate from that creative content. A product-specific notice will explain any different practices before you use the relevant feature.
Information processed by our apps
SideReader processes your creative content on your devices. Features such as Watch Remote or device pairing can exchange information between devices you connect. If you export, share, back up, or select a cloud file location, your chosen destination and platform may receive the content under their own terms. Sending content to support also gives us the material you choose to send. We do not use your creative content for advertising measurement.
An app may request access to device features such as the camera, microphone, photo library, files, local network, Bluetooth, or notifications. The app uses that access only to provide the feature you choose. Your operating system shows the permission request and lets you change access later in device settings.
Optional SideReader notifications
SideReader versions with notifications can send occasional app news and reminders to record another take. Notifications are off until you choose to enable them in SideReader and allow Apple's notification permission. This choice is separate from Product Analytics and Advertising Measurement.
To deliver these messages, SideReader uses Google Firebase Cloud Messaging. Google receives the Apple push token associated with a Firebase installation identifier and technical information including device model, language, time zone, operating system, and app identifier and version. SideReader uses a notification topic to reach installations that enabled notifications. Notification content does not include your scripts or recordings.
You can turn notifications off in Tools → Settings & Support → Permissions. SideReader saves that choice and asks Firebase to unregister the installation; delivery may continue until that request succeeds if the device is offline. You can also control notification permission in iOS Settings. Turning notifications off does not change Product Analytics. If Product Analytics is on, Firebase may measure notification interactions as part of that separate choice.
Optional SideReader analytics and advertising measurement
This section describes Optional Sharing in SideReader versions that include Meta's Facebook SDK and AppsFlyer's SDK. These versions include Google Analytics for Firebase and Google advertising measurement components, Meta's App Events SDK, AppsFlyer attribution measurement, and Apple's AdAttributionKit and SKAdNetwork conversion reporting APIs. In SideReader versions with Optional Sharing, Product Analytics starts on when no choice has been saved, including upgrades from versions without these settings. A saved off choice remains off. Advertising Measurement stays off until you enable it. Onboarding presents the choices separately; you can turn Product Analytics off and continue with both off. You can change them later in Tools → Settings & Support → Privacy & Support → Optional Sharing. Enabling Advertising Measurement can request Apple's tracking permission; enabling Product Analytics alone does not request that permission. Advertising choices made before the expanded Meta SDK behavior require renewal; an earlier Apple tracking permission alone does not enable it.
While Product Analytics is on, SideReader enables Firebase analytics collection and sends Google a limited set of feature events, such as completing onboarding, creating or importing a script, completing a recording or export, an export failure category, using Voice Pace or Watch Remote, and returning to create again. These events help us understand feature use and improve SideReader. They use fixed categories such as import format and single or dual output. They do not include script text, recordings, audio, photos, filenames, local content identifiers, or the contents of support logs. SideReader does not send email addresses or phone numbers for conversion matching.
Firebase also processes automatic app and session events, an app-instance identifier, and technical information such as app version, device model, operating system, language, and event times. Google may use the network address to derive approximate location. These technical data are separate from your creative content; measurement is not anonymous simply because that content is excluded.
Advertising Measurement is one optional choice covering Apple conversion reporting and Google, Meta, and AppsFlyer advertising measurement, separate from Product Analytics. It requires Product Analytics to be on. Google, Meta, and AppsFlyer identifier tracking additionally requires Apple's App Tracking Transparency permission to be authorized. When all three conditions are met, Google may use the permitted events and identifiers, including the advertising identifier when available, to measure which Google advertising led to installs or app activity. SideReader keeps Google personalized advertising and remarketing consent off.
With Product Analytics and Advertising Measurement enabled, SideReader can submit limited conversion values to Apple's operating-system attribution APIs even if tracking permission is off. The values represent an eligible activation (0), script created (1), script imported (2), recording completed (3), or export completed (4). The corresponding coarse values are low for activation and scripts, medium for recording, and high for export. To avoid lowering a conversion value, SideReader keeps a small local limit and omits new actions below it. The limit reflects earlier submission attempts and is conservative when earlier history is unknown. It remains across app restarts and changes to sharing choices. SideReader only submits new eligible activity and does not replay earlier actions; some lower-value activity may therefore be omitted from Apple reporting. SideReader does not pass script text, recordings, filenames, local content identifiers, advertising identifiers, email addresses, or phone numbers in these Apple API calls. The operating system controls whether and when privacy-preserving attribution reports are sent to eligible advertising networks. Reports can contain attribution and conversion information subject to Apple's limits, delays, and crowd-anonymity rules; this does not mean every activity is reported or that every report contains a conversion value.
SideReader starts Meta's Facebook SDK only when Product Analytics and Advertising Measurement are both on and Apple's App Tracking Transparency permission is authorized. It uses Meta App Events to measure and improve our advertising, including install and conversion campaign measurement and optimization. SideReader supplies selected events for completing onboarding, creating or importing a script, completing a meaningful rehearsal, completing a recording or validated export, using Voice Pace or Watch Remote, and first creating or returning to create again. App-supplied event details are limited to fixed categories such as import format and single or dual output. Meta's SDK manages its own installation and app-session reporting when enabled. First SDK activation can occur in an existing installation and does not establish the operating system's installation time.
Meta's SDK adds app and device information, including app identifier, version and build, operating-system version, device model, language and locale, time zone, carrier, screen dimensions and scale, processor count, and foreground or background state. It uses an SDK-generated installation identifier and can collect the advertising identifier when permitted. Meta also receives the network address used to contact its services. Event timestamps are assigned by the SDK when SideReader hands over events. The SDK also communicates with Meta to obtain technical configuration. These data are separate from creative content and are not anonymous merely because names are absent.
SideReader starts AppsFlyer only while Product Analytics and Advertising Measurement are both on, Apple's tracking permission is authorized, and the app is active. AppsFlyer measures app sessions and selected feature events for install and campaign attribution. Its SDK assigns an installation identifier and receives app and device information, event times, the network address used to contact its service, and the advertising identifier when permitted. SideReader disables AppsFlyer's vendor-identifier collection and does not send scripts, recordings, filenames, local content identifiers, email addresses, or phone numbers in its events. First SDK activation can occur after the app was originally installed. Turning Advertising Measurement off stops new SideReader submissions and stops the AppsFlyer SDK; information already sent cannot be recalled, and SDK-held information may remain on the device. Separately, Apple may send privacy-preserving attribution postback copies to AppsFlyer without tracking permission. SideReader's Advertising Measurement choice controls its conversion updates; Apple controls report delivery.
The custom event names and parameters supplied by SideReader do not include script text or titles, transcripts, recordings, audio, photos, previews, filenames or paths, local script or take identifiers, or support-log contents. SideReader does not provide email addresses, phone numbers, contacts, or an account identifier to Meta for matching. Automatic app-event logging is disabled in our current SDK and Meta configuration; SideReader explicitly supplies the selected events and asks the SDK to report eligible activation. These settings do not remove the SDK's own technical metadata, configuration requests, or event persistence. SideReader does not include an OpenAI advertising SDK; this website's separate measurement choices are described below.
In versions using Meta SDK 19, SideReader explicitly disables the SDK's additional screen-title and app-link metadata collection and its separate product-improvement setting before initialization and when sharing choices change. These controls are separate from SideReader's Product Analytics choice. Disabling them does not remove the technical information, installation identifier, configuration requests, or retained events described above.
You can change either choice in SideReader's Optional Sharing settings. Turning Product Analytics off also turns Advertising Measurement off, stops new measurement submissions by SideReader, disables Google analytics collection, and requests a reset of analytics data and identifiers stored locally by the Google SDK. Turning Advertising Measurement off stops SideReader from submitting new advertising events and Apple conversion updates; Google Product Analytics can continue if its separate choice remains on. SideReader withdraws Google's advertising storage and advertising-data consent. Google personalized advertising stays off.
For Meta, withdrawal stops SideReader's new event and activation calls, disables advertising-identifier collection, keeps automatic event logging disabled in our current configuration, limits event-data use through the SDK's supported settings, and clears optional developer-supplied matching data. The SDK has no supported complete shutdown or event-queue deletion control. Requests already started, queued events, and SDK configuration activity may still be processed or sent. The SDK can retain events on your device and send them later, including after measurement is enabled again. SideReader's own event router does not backfill earlier activity after opt-in; this does not erase or prevent later delivery of events already held by Meta's SDK.
Withdrawing Apple's tracking permission stops new Google, Meta, and AppsFlyer identifier tracking submissions controlled by SideReader, subject to the SDK limitations above. Apple's limited conversion reporting can continue while both in-app choices remain on. Apple may still send reports already scheduled by the operating system after you turn measurement off. SideReader cannot cancel those reports or recall information already received by a provider. Turning sharing off is not a request to delete historical information held by Apple, Google, or Meta; contact us about deletion requests.
Updates that introduce expanded measurement or cannot establish an affirmative choice require a new choice as described above. Apple tracking permission alone cannot turn either in-app choice on. SideReader saves your choice and the start of its measurement window before enabling new collection; if that choice cannot be saved, sharing stays off. Earlier activity is not newly submitted by SideReader merely because you enable a choice. Events already held by a provider or its SDK remain subject to the limits described above. Turning a previous default-on choice off during an update does not delete information already received by a provider.
Apple's processing is described in its Privacy Policy. For more information about Google's handling of measurement data, see Google's Privacy Policy and how Google uses information from apps that use its services. Meta's handling of received information is described in its Privacy Policy and Business Tools Terms. AppsFlyer's handling of received information is described in its Services Privacy Policy.
Website information and local preferences
If you choose “Allow measurement,” this site uses the OpenAI Ads Measurement Pixel and Meta Pixel to understand which page visits, content interactions, support-contact actions, and completed stay-in-the-loop signups are associated with our advertising. Both pixels are disabled by default and do not send measurement events unless you opt in. You can change your choice at any time through “Your Privacy Choices” in the site footer.
The OpenAI Pixel may store first-party attribution identifiers such as __oppref, add the current page source and event time, and send the measurement event to OpenAI. The Meta Pixel may use cookies and similar identifiers to attribute activity and match events under our Meta business settings. After a successful stay-in-the-loop signup, the site may also send OpenAI a SHA-256 hash of the normalized email address for conversion matching; our measurement code does not send the raw email address to either platform. A hashed email address is still personal information and can be matched to an account; hashing does not make it anonymous. The platforms also receive network and browser information when their services are contacted, such as IP address, browser details, page URL, and event time. Clapps marks OpenAI events as opted out of future user-level personalization. See OpenAI's Privacy Policy and Meta's Privacy Policy.
Cloudflare may set the strictly necessary __cf_bm cookie for bot management. It is generated independently for this site and expires after 30 minutes of inactivity. Clapps does not use it for advertising, analytics, or cross-site tracking.
The site stores limited preferences in browser storage: your light or dark theme and advertising-measurement choice in local storage, and a rotating visual accent in session storage. These preferences stay in your browser and can be removed by clearing this site's stored data.
We publish through OpenAI Sites, which uses Cloudflare hosting infrastructure. These hosting and security services process technical request information needed to deliver and protect the site. This can include an IP address, approximate location derived from it, browser and device information, requested page, referral information, timestamps, and security or diagnostic logs.
If you sign up to stay in the loop, we collect the name and email address you submit. We store that information with our hosting provider and send it to HubSpot, our customer relationship and email service provider, so we can manage the signup and send Clapps updates. Joining the list is optional and separate from allowing advertising measurement. Unsubscribe using the link in an update or email hello@clapps.me. See HubSpot's Privacy Policy.
Messages you send us
If you email us, we receive your email address and whatever you include in the message, such as your name, device details, screenshots, or a support description. Please do not send sensitive information or app content that is not needed for us to help you.
We use messages to respond, troubleshoot, keep appropriate business records, prevent abuse, and improve our products. We keep them only as long as reasonably necessary for those purposes or to meet legal obligations.
App stores, purchases, and diagnostics
Apple or another platform provider may independently process app-store downloads, purchases, refunds, subscriptions, and account information. Clapps does not receive your full payment-card details. Those providers handle information under their own privacy terms.
SideReader does not include Firebase Crashlytics. The optional Google, Meta, and AppsFlyer measurement described above includes technical information. Meta's SDK contains crash and error reporting capabilities, but its standard automatic crash and error reporting is disabled in SideReader's current configuration. SDK configuration requests and already queued work may still run as described above. Separately, Apple or another platform may give developers aggregated sales or performance information and, if you choose to share diagnostics through device settings, crash or diagnostic reports. We use these platform reports only to operate and improve our apps and do not combine them with advertising profiles. SideReader's local support archives are not automatically attached to measurement events; if you choose to send one to support, we receive what you send.
How information is disclosed
We do not exchange personal information for money or provide creative app content to advertising partners. Optional advertising measurement does disclose identifiers and activity data to the partners named above. Those disclosures may be treated as a “sale,” “sharing,” or targeted advertising under applicable privacy laws, even without a monetary payment. Use “Your Privacy Choices” in the footer to decline website measurement; use Optional Sharing in SideReader to control app measurement.
We may disclose limited information only:
- to hosting, email, support, and signup providers for the purposes above; to Google for optional app analytics; and, with the relevant permission, to Google, Meta, AppsFlyer, or OpenAI for the measurement described above;
- to app-store or platform providers for distribution and purchases;
- when required by law or reasonably necessary to protect rights, safety, or security; or
- as part of a merger, acquisition, financing, or sale, subject to this policy and applicable law.
Retention and deletion
You can remove local app content using the app's controls or by uninstalling the app. Exports, Photos copies, paired-device copies, and cloud backups may remain and must be managed separately with the relevant device or service. Because we do not keep a server-side copy of your local creative content, we cannot retrieve or delete those copies for you.
For SideReader measurement, Google Analytics is currently configured to retain event-level data for 2 months and user-level data for 14 months. Google also applies the user-data period to events marked as key events. New activity resets the user-data retention period. These settings govern the detailed data covered by Google's retention controls; standard aggregated reports are not affected by those limits. Turning Product Analytics off stops future Google measurement submissions and requests a local Google SDK reset. Turning Advertising Measurement off leaves Product Analytics operating if it remains enabled. Neither choice deletes historical data held by Google. Contact us to request deletion.
Meta retains received measurement information under its own policies and applicable business terms. Google's retention settings do not apply to Meta. Meta's SDK can retain unsent events locally and process or transmit them later, including after you enable measurement again. Turning measurement off stops new SideReader submissions and applies the supported SDK restrictions, but does not guarantee cancellation of every pending request, deletion of SDK-held events, or deletion of data already received by Meta. Contact us about requests concerning that information.
AppsFlyer retains information it receives under its own policies and applicable business terms. Google's retention settings do not apply to AppsFlyer. Stopping AppsFlyer prevents new SideReader submissions while the choice is off; it does not delete data already received by AppsFlyer or guarantee deletion of information held by its SDK on the device. Contact us about deletion requests.
Browser preferences remain until you clear them. Signup details remain until you ask us to remove them or they are no longer needed for Clapps updates. Hosting logs and support messages are retained only as long as reasonably needed for security, operations, support, and legal obligations. We may retain limited opt-out records to respect your choices and records needed to meet legal obligations or resolve disputes. Measurement partners apply their own retention rules to information already received; the Google Analytics settings above do not govern Meta, AppsFlyer, Firebase Cloud Messaging, or OpenAI. Email us for a deletion request or information about the retention that applies to a record.
Your choices and privacy rights
You can manage app permissions in device settings, decline to send a support email, ask us to remove your stay-in-the-loop signup, clear this site's browser storage, change optional advertising measurement through the footer's “Your Privacy Choices,” and control optional diagnostic sharing through your platform settings. In SideReader, you can separately change Product Analytics and the combined Apple, Google, Meta, and AppsFlyer Advertising Measurement choice in Optional Sharing. Product Analytics starts on if no choice is saved; Advertising Measurement starts off. You can turn both off during onboarding or later. Website measurement also remains opt-in. Turning Product Analytics off also turns Advertising Measurement off. Notifications have a separate choice in Tools → Settings & Support → Permissions; Apple's notification and tracking permissions are controlled in device settings.
Depending on applicable law, you may have rights to know, access, correct, delete, or receive a portable copy of your personal information; to object to or restrict processing; to withdraw consent; and to opt out of sale, sharing, or targeted advertising. California residents have these rights where the CCPA applies. We do not use sensitive personal information to infer characteristics about you or make solely automated decisions with legal or similarly significant effects.
Send requests to hello@clapps.me with the subject “Privacy request.” Tell us which app or service is involved and what you are requesting. We may ask for information reasonably needed to verify an access, correction, or deletion request or an authorized agent's authority. Website measurement opt-outs require no account or identity verification. We respond within applicable legal deadlines and explain any exception that prevents us from fulfilling a request. To appeal a decision where that right applies, reply with “Privacy appeal.” We will not discriminate against you for exercising a privacy right.
If European or UK data-protection law applies, you may also complain to your local data-protection authority. Withdrawing consent does not affect the lawfulness of processing before withdrawal. You can contact us about information already sent to a measurement partner. Turning a SideReader choice off stops new submissions controlled by that choice, but Meta's SDK may still process pending requests or retained events, AppsFlyer may retain information it already received, and Apple may still send reports already scheduled by the operating system. The SDK's technical activity may also continue as described above. Turning a choice off is not itself a historical deletion request.
Cookies, Do Not Track, and Global Privacy Control
Optional website measurement is off until you affirmatively allow it. Choose “Decline measurement” or “Turn off” through the footer's “Your Privacy Choices” control at any time. Refusing measurement does not prevent you from using the site or joining the mailing list. The choice applies to this browser; repeat it on other browsers or devices. Clearing browser storage removes saved preferences, and measurement defaults to off.
We honor Global Privacy Control (GPC) as a request to keep optional website measurement off, including when an earlier saved preference allowed it. Your Privacy Choices shows when GPC is active. We do not separately respond to legacy Do Not Track signals. Website controls do not change SideReader's in-app settings or your choices on third-party websites.
If you allow measurement, advertising partners may associate identifiers and activity with information from their own services or other sites and apps under their policies and applicable choices. Our OpenAI opt-out flag and Google personalization setting do not make all partner processing anonymous or establish a blanket exemption from privacy laws.
The strictly necessary Cloudflare __cf_bm security cookie may be used to distinguish legitimate traffic from automated abuse. It is separate from advertising or cross-site tracking and is not used by Clapps to build a user profile.
Third-party sites reached through our links may have different practices. Their policies apply when you visit them.
Purposes and legal bases
We use Product Analytics to understand feature use and improve SideReader. SideReader can start Product Analytics when no choice is saved. This on-by-default setting is not affirmative consent. Where European or UK law requires consent for analytics collection or access to information on your device, that consent is required before collection; this policy and the default setting do not replace it. Advertising measurement and requested marketing emails remain consent-based.
Where European or UK law requires a legal basis, we rely on performance of a contract for providing requested products and support; legitimate interests for site operation, security, abuse prevention, and handling business correspondence, subject to your rights; and legal obligations where we must preserve or disclose a record. Optional data is not required to use SideReader. An email address is needed to send requested updates or reply by email.
Security and international processing
We use reasonable administrative and technical measures appropriate to the limited information we handle. No transmission or storage method is completely secure, so we cannot guarantee absolute security.
Clapps is based in the United States. Our providers may process information in the United States and other countries, where privacy laws may differ from those where you live. Where applicable law requires transfer safeguards, transfers must be supported by an applicable adequacy decision or other lawful safeguards, such as standard contractual clauses. Contact us for information about the safeguards applicable to your information.
Children
Clapps apps and this site are not directed to children under 13, and we do not knowingly collect personal information online from children under 13. Do not submit a child's information or enable optional sharing if you cannot provide legally valid consent. We do not knowingly sell or share personal information of children under 16 for advertising. If you believe a child has sent personal information to us, contact us so we can take appropriate steps to delete it.
Changes to this policy
We may update this policy when our products, providers, or legal obligations change. We will post the revised policy here, update the date above, and provide any additional notice required by law. If app data practices materially change, we will also update the relevant app-store disclosures before the changed behavior ships. We seek new consent when required. Posting this policy does not change a saved app choice, grant tracking permission, or provide consent.