BulbMatch Privacy Policy

Effective date: November 13, 2026

This Privacy Policy describes how the BulbMatch mobile application for Android and iOS (the “Application”), operated by Sergey V. (the “Service Provider”), accesses, processes, stores, and shares information. BulbMatch helps you turn user-confirmed lamp markings into a conservative replacement shopping profile for 220–240 V / 50 Hz regions. It does not certify a fixture, wiring, dimmer, enclosure, or installation.

Privacy summary: Photos and text recognition are processed on your device. Photos, full recognized text, and unfinished drafts are not saved by BulbMatch or uploaded. Only results you explicitly save are stored in local history. The Application has no user accounts or product analytics. Yandex Mobile Ads and Firebase Crashlytics may process technical information for advertising and crash diagnostics as described below. The core matching, reference, save, and history features work offline.

1. Information Stored on Your Device

When you choose Save, BulbMatch stores a local result containing the lamp fields you have confirmed or entered, the assessment and replacement profile, a save date, a local record identifier, catalog and ruleset versions, and an optional result name. These fields may include the base, voltage, frequency, lamp power, explicitly printed equivalent power, brightness, color temperature, shape, dimmability, and a separately entered fixture maximum wattage. An unknown base marking may be saved as confirmed text with a result that needs clarification. Rejected or unconfirmed OCR observations are not included in saved results.

Language and theme preferences are also stored locally. Local counters and the time of the last interstitial impression are used only to limit advertisement frequency. BulbMatch does not transmit these counters as product analytics or provide your saved lamp values or result names to advertising or crash-reporting providers.

BulbMatch has no account system, application-operated cloud backup, synchronization, cross-device transfer, export, or sharing feature. Device backups or transfers provided by your operating system are separate from BulbMatch and depend on the platform and your settings.

2. Camera, Photo Picker, and On-Device Text Recognition

Camera permission is requested only after you choose Camera. You may deny or revoke it in system settings; choosing an existing photo and manual entry remain available. Photo import uses the system single-image picker without requesting broad access to your photo library. BulbMatch processes only the image you select or capture and does not read or store EXIF location metadata.

Text recognition (OCR) runs locally using bundled PaddleOCR models and ONNX Runtime. No photo or recognized text is sent to a cloud recognition service, and no OCR model download is required. Every detected field remains a draft until you confirm, edit, or reject it.

Images, previews, recognition geometry, full OCR transcripts, and unfinished drafts are held only in memory while the flow is active. BulbMatch releases them when the flow ends or is abandoned, or when the app process ends. They are not written to app storage, caches, history, logs, or crash reports and are not restored after process recreation. An original image selected from your photo library remains under your control in that library; discarding the in-app draft does not delete the original.

3. Information Not Requested and Analytics Not Used

BulbMatch does not require an account or ask for your name, email address, phone number, contacts, date of birth, precise location, or payment information to use its features. If you contact support, you voluntarily provide your email address and the content of your message; these are used to respond to your inquiry or privacy request.

The Application does not use Google Analytics for Firebase, custom product events, funnels, session replay, or custom user profiling. BulbMatch does not send lamp markings, reference searches, result names, or matching history as advertising targeting data.

4. Third-Party Services and Network Data

Yandex Mobile Ads

BulbMatch uses Yandex Mobile Ads for inline advertisements below completed compatible results, banners in History and Reference, and frequency-limited full-screen advertisements when you explicitly leave an eligible completed compatible result. Advertising does not appear during capture, OCR review, or clarification/conflict results. Failed or offline advertisements do not block the core features.

Before initialization, BulbMatch passes a negative personal-data consent state to the SDK, disables location signals, and supplies no custom targeting parameters. It does not request Android advertising-ID permission or display an App Tracking Transparency prompt on iOS. These restrictions do not mean that advertising involves no data processing. Yandex may process IP addresses, device or SDK identifiers available under platform restrictions, device/application and network information, and ad impressions or interactions to deliver, secure, and measure advertisements. An IP address may indicate an approximate location even when device location signals are disabled. Its applicable policies describe provider processing.

Firebase Crashlytics

Release versions use Firebase Crashlytics automatically for crash and non-fatal error diagnostics. Reports may include crash times, stack traces, app/build and OS/device information, and SDK-generated installation and session identifiers. These technical identifiers are separate from an account or a custom BulbMatch user ID. BulbMatch may attach fixed technical codes for the screen, operation, failure type, or catalog/ruleset version. App-reported non-fatal errors are sanitized.

BulbMatch does not attach photos, image paths, OCR transcripts, confirmed lamp values, result names, database contents, custom user IDs, user-content logs, or Analytics breadcrumbs. Debug, preview, and test builds do not send crash reports. Reports may wait locally for a later connection. There is no in-app crash-reporting switch; Clear local data does not disable reporting or delete reports already sent to Google.

For details about these providers, including their data handling and privacy rights, see:

5. Purposes of Processing

6. Legal Bases and Your Choices

Where applicable law requires a legal basis, processing to provide features you request may be necessary to provide the service. Limited diagnostic and support processing may rely on legitimate interests in maintaining a reliable and secure Application, subject to applicable law and your rights. Processing may also be necessary to comply with legal obligations. Where consent is legally required, it must be obtained for that processing; this Policy is a notice and does not itself constitute consent.

You control camera permission, which image to select, which detected fields to confirm, whether to save a result, and when to delete local history. The current Application does not offer a personalized-advertising opt-in or an in-app advertising consent toggle. Camera permission does not constitute consent to advertising or crash reporting.

7. Data Sharing

The Service Provider does not receive or sell your in-app photos, recognized markings, or locally saved history. Technical data is processed through Yandex Mobile Ads and Firebase Crashlytics for the purposes described above. Support correspondence is received only when you choose to contact the Service Provider. Information held by the Service Provider may be disclosed where legally required or necessary to address fraud, security threats, or harm, subject to applicable law.

Opening a provider link or advertisement may take you to a third-party service that processes information under its own privacy policy. Those services are separate from BulbMatch's local matching and history features.

8. Retention and Deletion

Saved results remain locally until you delete individual records, clear local data, uninstall the Application, or the operating system removes its storage. Settings → Clear local data deletes all saved results and resets local ad-frequency counters; it keeps your language and theme choices. Unfinished capture/OCR/manual drafts have session-only retention as described above.

Clearing app storage or uninstalling the Application is subject to operating-system behavior. Separately held operating-system backups may require management through your device or backup-provider settings. Local deletion does not delete information already processed by advertising or crash-reporting providers.

Google's published Firebase retention policy states that Crashlytics keeps crash traces and associated identifiers for 90 days before starting removal from live and backup systems. Yandex retention is governed by its linked policies. Support correspondence is retained as needed to handle the request and meet applicable legal obligations. Contact the Service Provider for assistance with privacy requests; some provider-controlled requests may need to be directed to the provider.

9. International Processing

Yandex and Google may process technical information outside your country. Their linked policies describe relevant entities, international processing, and safeguards. Transfers must comply with applicable law; the Service Provider does not promise that all third-party processing occurs in your country.

10. Security

BulbMatch limits persistent content to explicitly saved results and local settings, processes recognition on device, and restricts diagnostic context. The security of local data also depends on your device, operating-system protections, and backup settings. No method of storage or transmission is completely secure, so absolute security cannot be guaranteed.

11. Children's Privacy

BulbMatch is not directed to children and does not ask for a date of birth. The Service Provider does not knowingly collect personal information from children through support communications. If you believe a child has provided personal information to the Service Provider, contact the address below so the matter can be investigated and appropriate action taken under applicable law.

12. Your Privacy Rights

Depending on where you live, you may have rights to access, correct, delete, or receive your personal information; restrict or object to processing; withdraw consent where processing relies on it; or complain to a data protection authority. Contact the Service Provider to make a request. Because BulbMatch has no account and does not upload local history, the Service Provider cannot retrieve your on-device results. Requests concerning technical SDK data may require information sufficient to locate the relevant records. Withdrawing consent does not affect lawful processing that occurred before withdrawal.

13. Changes to This Policy

This Policy may be updated when the Application, integrations, legal requirements, or data practices change. The revised version will carry a new effective date, and material changes will be communicated where required by law. The current policy is available at sedsoftware.com/apps/bulbmatch/policy.html.

14. Contact Us

Service Provider: Sergey V.
For questions or privacy requests related to BulbMatch, contact info@sedsoftware.com.