Privacy Policy

This service and this notice

D4 Graffiti Operations supports graffiti and maintenance work for authorized operational personnel and approved collaborators. This notice covers the desktop management website at d4graffitiops.com, the native iPhone app, the Android crew tablet app (APK), and their connected operational services.

Dillon Campa administers this service. This is the privacy notice for this application, rather than a department-wide Caltrans privacy policy. Features and information available to a user depend on the platform, account approval, assigned role, and device permissions.

Information we collect and process

• Accounts and access: name, email address, account identifier, approval and verification status, role, position, and an optional profile picture. Firebase Authentication processes credentials for email/password sign-in, verification, and password resets.
• CSR requests and job records: CSR and service-request numbers, requester names and contact details when included in a request or import, descriptions, comments, job status, crew attribution, routes, directions, streets, cities, postmiles, work-order details, dates and times, mileage, gallons, square footage, and related maintenance information.
• Photographs: reference images and before-and-after photographs that users capture, select, upload, or attach using a supported link. Images and photo stamps may contain people, vehicles, time, location, route, and other job information.
• Location and device information: coordinates and related location updates used by enabled map, navigation, job, and crew tablet tracking features; device identifiers and notification registrations; and relevant app or operating-system version information.
• Technical and support information: IP addresses and ordinary connection information processed by hosting and connected providers, error and crash information where diagnostics are enabled, and information users send when requesting help. Android crash diagnostics can include the time, device/app information, error details, and recent app activity.

Only submit photographs and information appropriate for the operational task. Avoid unnecessary personal or sensitive information in comments, attachments, and support reports.

How information is used

Information is used to verify and approve accounts, apply role-based access, receive and review CSR requests, assign and document maintenance work, locate jobs, support crew operations, record completion, calculate route and work totals, display authorized tablet locations, send operational updates, troubleshoot problems, and respond to support or data requests.

Approved users may view, edit, export, or share information as permitted by their role and available features. Operational records may be shared with appropriate personnel, requesters, and other recipients through configured work processes, including completion messages and exports. Access to shared work history does not end merely because the person who entered it leaves the service.

GPS, location permissions, and tablet tracking

Location services support finding the current position, choosing or documenting a job location, maps, navigation, route and visit information, and live crew tablet tracking. Maps and saved work records may include precise coordinates. Selecting an address or map pin can also provide location information without using the device’s current GPS position.

When crew tracking is configured and location permission is granted, the Android crew tablet can transmit its location and related operational updates to the connected service. Tracking may continue while the app is in the background when the tablet’s permissions and configuration allow it. Authorized administrators can view tracked tablet locations from the management website or iPhone app. Viewing a tablet’s location is separate from sharing the viewing phone’s own location.

You can change location permissions in device or browser settings. Disabling permission can prevent locating, navigation, visit, or live tracking features from working; it does not remove coordinates already saved in work records. For a managed crew tablet, discuss tracking and permission changes with the responsible administrator.

Notifications, camera, and photo choices

The iPhone app uses Apple Push Notification service for enabled push alerts. Notification registrations link a device delivery token to an account. Operational updates can also appear inside the website or app; delivery and recipient rules depend on platform, account role, and configured notification preferences. Alerts may include job status, CSR/request references, and location details, which can appear on a device’s lock screen.

You can disable push notifications or hide previews in device settings and change available preferences in the app. Camera and photo access is used for photographs you capture or select for work records or your profile. You can revoke these permissions in device or browser settings; related features may then be unavailable. Removing permission does not delete previously uploaded photographs.

Storage and third-party services

• Google Firebase: Firebase Authentication manages account sign-in and related account-verification functions. Firebase Firestore is the current operational database for work data. Google Sheets is no longer the primary operational database; earlier records or copies may remain in legacy files, migration copies, or exports.
• Google Drive: stores uploaded work photographs and provides access to those files for operational records. A linked file may also remain in its source owner’s Drive. Photo handling can involve configured Google authorization and backend services.
• Netlify: hosts the management website and connected backend services. Backend storage also holds service information such as account profiles/access settings, device registrations, and operational or diagnostic state, depending on the feature.
• Maps, navigation, imagery, and weather: enabled features use Mapbox and connected providers, including Google Maps/Street View, TomTom, OpenStreetMap/Nominatim, and Open-Meteo where configured. Requests can include coordinates, search terms, destinations, IP addresses, and connection information. Opening an external navigation or imagery service shares the selected information with that provider.
• Apple and other delivery services: Apple processes iPhone push delivery. Configured email or notification delivery services process the addresses, delivery identifiers, and message content needed to send operational updates.

Providers process information under their applicable terms, privacy notices, and service configurations. Relevant notices include Google, Netlify, Mapbox, and Apple. Access to Google API data is subject to the Google API Services User Data Policy, including applicable Limited Use requirements.

Local storage, retention, and security

Browsers and apps use local storage for sign-in sessions, preferences, cached records or images, drafts, and pending submissions. Persistent sign-in can keep a session on the device. Clearing local data or signing out does not delete server-side work history or photographs.

Work records, photographs, account information, tracking/route information, and diagnostics are retained according to operational needs, service configuration, and applicable organizational requirements. There is no single automatic deletion period for all information. Exports, backups, legacy copies, and copies held by recipients may remain under their own retention practices.

The implementation uses authenticated requests and account approval/role checks for protected functions. Firebase Authentication manages sign-in; hosting and other providers supply their own security controls. Access also depends on administrator configuration and device security. No system can guarantee complete security. Use a protected device, do not share credentials, and report suspected unauthorized access.

Support, correction, and data deletion

For support, account access, corrections, or a request to delete an account or personal information, contact dillon.campa@gmail.com. Describe the account or record involved and the action you are requesting. Do not send a password. The administrator may need to verify your identity and authority before acting on a request.

The iPhone app also provides an account deletion option in Menu → Profile → Delete account. Follow the confirmation prompts shown in the app. If the request cannot complete, retry or contact support. Account removal and removal of shared operational records are separate: job history, CSR requests, photographs, and attribution in retained work records may need to remain for operational or organizational requirements. A deletion request does not automatically remove copies already exported or shared with others.

This service is intended for authorized operational personnel and approved collaborators, not for children. For assistance with accessibility or using a feature, contact support. See the App Support page for login help and reporting instructions.

Changes to this notice

This notice may be revised when the service’s features, providers, or data practices change. The updated date identifies this revision.