Privacy notice

Information we collect

Information may include your name, phone number, email, communication preference, service ZIP, pest concern, property type and size, service address when later required, account and service records, photos or documents you choose to provide, device and security data, and payment status. Payment credentials are handled by the applicable payment processor rather than stored as raw card or bank details by this website.

How we use information

We use information to review service needs, respond to estimate and service requests, perform and document service, communicate about appointments or accounts, operate customer-app features, protect systems, comply with legal obligations, and improve the customer experience.

Customer app and device information

The customer app may process account identifiers, contact and property information, service history, estimates, invoice and payment-status information, notification preferences, referral activity, feedback, and photos or documents you choose to attach. It may also process an app installation identifier, push token, app version, device platform, feature interactions, and technical diagnostics needed to deliver notifications, protect accounts, measure reliability, and troubleshoot failures.

If you enable notifications, delivery is handled through Expo, Apple Push Notification service, and Google Firebase Cloud Messaging. The customer app does not request your device location. Service-day arrival information describes the assigned technician's progress using a privacy-limited arrival range rather than exposing precise vehicle coordinates.

Optional device permissions

Camera or selected-photo access is used only when you choose to attach an image. Calendar access is used to add a confirmed appointment at your request. Face ID, Touch ID, or Android biometric checks can be used for faster sign-in; biometric templates remain under the operating system's control and are not received or stored by Bugged. You can deny or revoke these permissions in device settings and continue using the features that do not require them.

Service providers and disclosure

Information may be disclosed to infrastructure, communications, payment, analytics, professional, and operational providers that support Bugged; to authorities or other parties when required by law or necessary to protect rights and safety; and in connection with a business transaction subject to applicable safeguards. We do not sell personal information.

Push notifications

If you enable notifications, we associate a device push token, app identity, platform, app version, and account session with your account to deliver service, billing, support, and work updates through Expo, Apple Push Notification service, and Firebase Cloud Messaging. Private updates use generic lock-screen text; details require signing in. We retain delivery outcomes and notification opens when available to diagnose failures. Provider acceptance does not tell us whether a notification appeared on your screen.

Optional BUGGED promotional pushes are off by default. They require a separate opt-in in the app, which records the time, source, and consent-text version. Allowing notifications in your phone settings alone does not opt you into marketing. You may withdraw promotional consent immediately in the app notification preferences. We limit promotional pushes to one per customer in a rolling seven-day period, between 9 a.m. and 7 p.m. Central, subject to your quiet hours. You can use the app without enabling push. Email and text-message choices remain separate.

Text messages

If you select text-message follow-up and provide consent, Bugged may send transactional messages about that estimate or service relationship. Message and data rates may apply. Reply STOP to opt out. Consent is not a condition of purchase.

Analytics and diagnostics

The public website uses PostHog Cloud US to understand page visits, traffic sources, device categories, estimate-funnel progress, website performance, and the results of feature-flag experiments. If you allow analytics, PostHog may use browser storage to maintain attribution and experiment assignment. A sampled subset of allowed sessions may be recorded with inputs masked and sensitive estimate regions blocked. If you choose cookieless analytics, PostHog receives aggregate events without persistent browser identity, experiments, or replay. Estimate-field values such as names, emails, phone numbers, ZIP codes, notes, and pest selections are not sent as analytics event properties.

The customer app sends a limited, first-party event stream to Bugged's Supabase environment. Event properties use an approved list of technical values such as screen, outcome, error code, device platform, app version, and duration range; names, contact information, addresses, free-form text, payment credentials, and photo URLs are excluded. Bugged also uses Sentry for customer-app crash and performance diagnostics. Sentry collection is configured without default personal information, screenshots, view hierarchy, or session replay, and request bodies, headers, URLs, free-form context, contact information, addresses, and credentials are removed or redacted before transmission.

Website analytics URLs exclude query strings, replay does not collect network bodies or headers, and Bugged does not send PostHog customer, onboarding, or resume identifiers. PostHog's service is subject to its privacy notice. Sentry's service is subject to its privacy notice.

Your analytics choice

Texas privacy requests

Where the Texas Data Privacy and Security Act applies, Texas consumers may request access, correction, or deletion and may opt out of covered sale, targeted advertising, or certain profiling. Bugged does not sell personal information. Submit a deletion request through the account-deletion process or contact Bugged using the methods below. Appeals may be submitted through the same channel with “Privacy appeal” in the request.

Retention, account deletion, and security

Account and diagnostic records are retained only while reasonably needed for the purposes described above. Service, billing, pesticide-use, safety, tax, audit, fraud-prevention, and dispute records may be retained for the period required by law or legitimate business need, then deleted or de-identified. Signing out or changing accounts clears customer-scoped app caches on that device.

You can request deletion inside the customer app or through the public account-deletion process. Deleting app access does not silently cancel active pest-control service or erase records Bugged must retain. Bugged uses administrative, technical, and physical safeguards, but no internet transmission or storage method can be guaranteed completely secure.

Contact

Bugged Pest Control LLC
Service area: Greater Austin, Texas
(737) 247-7143
hello@buggedpest.com