Legal
Privacy Policy
Last Updated: October 23, 2026
1. Introduction
Trades Support (NEON-Systems, LLC) ("Trades Support," "NEON-Systems," "we," "us," or "our") operates the Trades Support mobile and web application (the "App"), an all-in-one project management tool designed for trades businesses. This Privacy Policy explains how we collect, use, disclose, retain, and safeguard your personal information when you use our App and related services across iOS, Android, and web platforms. By using the App, you acknowledge that you have read and understood this Privacy Policy and consent to the practices described herein.
2. Information We Collect
2.1 Account Information
When you create an account, we collect:
- Full name
- Email address
- Phone number
- Password (stored securely in hashed form)
- Account role (Admin (Executive), Project Manager, Customer, or Field Staff)
- For Customer accounts, optional personal vs business account type and related profile details
Team Member invitations grant Customer-side project access and are stored as Customer-role associations, not a separate account type.
2.2 Profile Information
You may optionally provide:
- Company/business name, address, phone, logo, and branding
- Industry and specializations
- Profile photograph
- Business documents (for example licenses or insurance documents your company uploads)
2.3 Project Data
When you create or participate in projects, we collect:
- Project names and descriptions
- Project addresses and location details
- Scope of Work (SOW) documents
- Bill of Materials (BOM) details
- Project milestones and progress updates (including evidence such as photos, files, notes, or audio notes when used)
- Project status and workflow information
- Scheduled visits and appointments
- Project contacts and assigned personnel
- Proposed visit dates/times for scheduling and your approve/decline responses for scheduling requests
- Team member associations when Customer account holders add or invite team members (we store these associations)
- Parts catalog items and related photos when your company uses the parts catalog
When you connect a calendar (e.g. Google Calendar, Microsoft when offered), we store connection metadata and may receive calendar event data for the date ranges you request, to show availability and scheduling conflicts.
When enabled for your environment, we may also process data related to Subcontractor RFQ workflows (including RFQ content, invites, and related project or chat records) and Customer Proposal Request workflows (including request details, photos, attachments, and invitee emails).
2.4 Media and Attachments
The App may collect and store:
- Progress photos uploaded for projects
- Receipt images and documents
- File attachments (PDFs, spreadsheets, images)
- Chat messages, including text, images, and file attachments
- Cover photos for projects
- Milestone audio notes when you record them
2.5 Mileage and Location Data
When you use mileage tracking (e.g. for field staff trips), we may collect and store:
- Trip start and end timestamps
- Distance (miles), including GPS-derived or manually entered values
- Start and end coordinates (latitude/longitude) when location is used
- Start and end addresses when provided or resolved
- Project and user association for each entry
2.6 Financial Information
For payment processing and project management, we collect:
- Estimated costs and revenue figures
- Actual costs and material expenses
- Proposal and quote amounts, tax, and customer-facing pricing
- Payment status, invoice records, and transaction metadata
- Fee tier and subscription information
Note: We do not store full credit card numbers, CVV codes, or other sensitive payment credentials.
- SaaS subscriptions on web are processed by Stripe. In-app subscriptions on iOS and Android are billed by App Store and Play Store; we receive and store subscription status and validation data.
- Customer payments for project invoices are processed through Stripe Connect to the contractor company's connected Stripe account. Stripe may collect business identity, bank, and KYC information from the company for Connect onboarding. We receive payment status and related metadata needed to operate the App; we do not store full payment card credentials.
2.7 Time Tracking Data
For field staff and project management:
- Clock-in and clock-out timestamps
- Time entry records linked to specific projects
- Work duration calculations
- Payment status of time entries
- Field staff rate or labor-type information when your company stores it for costing
2.8 Device and Technical Information
We automatically collect:
- Device type and operating system
- Platform information (iOS, Android, web)
- Firebase Cloud Messaging (FCM) tokens for push notifications
- App version information
- Crash reports and diagnostic data (via Firebase Crashlytics and Sentry)
- App Check / security attestation signals used to protect our APIs
Sentry is used for error and performance monitoring. When enabled, we may capture error reports, breadcrumbs (e.g. navigation or action trails), and optionally your user ID to help diagnose issues. See Sentry's privacy policy for how they process data.
When you tap Report issue (or Report a Bug), we collect the details you choose to send. Optional diagnostics, if you agree on first use, may include device information and a redacted navigation path (for example /project/:id). You may report without diagnostics or include an optional screenshot in the form.
Meta / Facebook App Events: On iOS and Android we use Meta (Facebook) App Events for marketing attribution and analytics (for example app install, completed registration, and purchase events). Depending on platform configuration, this may involve device identifiers used for advertising measurement (such as an advertising identifier) and related measurement frameworks. This is not a sale of your personal information. See Meta's privacy policy for how Meta processes this data: https://www.facebook.com/privacy/policy/.
2.9 Address and Location for Services
- When you use address autocomplete (e.g. for project or company address), your input and selected place details are sent to our backend and to Google Places API to return suggestions and full address components.
- When you use visit weather forecast, we send project/visit location and date to our backend (and any third-party weather service we use) to return forecast data.
2.10 AI and Automated Processing
When you use AI-powered features (e.g. project support chat, receipt parsing, milestone suggestions, or industry profile generation):
- Chat messages and relevant project context may be sent to our AI/LLM provider (e.g. Grok or a custom endpoint you configure).
- Receipt or document images may be sent for parsing (e.g. Grok Vision) to extract line items or data.
- This data is processed according to our agreements with the provider and their privacy policies.
2.11 Other Data
- Feature voting: If you submit feature votes or feedback, we store your choices and optional comments.
- Report user: If you report another user for safety or policy reasons, we collect and use the report content and related identifiers for safety and support purposes.
- Referrals: If you use referral codes or referral programs when offered, we store referral codes, related events, and eligibility metadata needed to apply rewards or credits.
- QR / invite codes: When you join a team via QR code or invite link, we process the invite token, email, and association details needed to complete registration.
2.12 Communication Data
- In-app notifications and their read status
- Push notification preferences
- Chat message history within projects and direct messages between users
- @mention data for team communication
- Transactional emails related to invites, verification, payments, and account operations
3. How We Collect Information
3.1 Information You Provide
Most information is collected directly from you when you:
- Create an account and complete your profile
- Create or manage projects and companies
- Upload photos, documents, audio notes, or attachments
- Send chat messages within projects or direct messages
- Enter time tracking or mileage records
- Connect a calendar (OAuth and event fetches)
- Use address autocomplete (input and place selection sent via our backend to Google Places)
- Use AI support chat, receipt parsing, or related features
- Submit feature votes or report another user
- Complete Stripe Connect onboarding for your company (via Stripe)
- Update your account settings
3.2 Automated Collection
We automatically collect certain technical data through:
- Firebase (crash reporting, cloud messaging, App Check)
- Firebase Crashlytics and Sentry for error reporting and diagnostics
- FCM for notification delivery
- Meta App Events for marketing attribution and analytics on mobile
3.3 Third-Party Services
We receive information when you:
- Sign in using Google Sign-In or Sign in with Apple
- Complete payments through Stripe (including Stripe Connect) or in-app purchase (App Store, Play Store)
- Connect Google (or Microsoft) Calendar
4. How We Use Your Information
4.1 Core App Functionality
- To create and manage your user account and company membership
- To enable project creation, tracking, and collaboration
- To facilitate communication between project participants
- To process and display project-related documents and media
- To track time and mileage entries for field staff
- To manage project workflows and approvals
- To show calendar availability and scheduling (including external calendar events when connected)
- To support parts catalog, referrals, and invite/QR join flows when you use them
4.2 Payment Processing
- To process SaaS subscription billing (Stripe on web; App Store / Play Store on mobile)
- To facilitate customer project/invoice payments via Stripe Connect to the contractor company
- To validate and reflect subscription and payment status
- To calculate and display financial summaries and reports (including CSV exports your company generates)
- To generate payment receipts and records within the App
4.3 Communications
- To send push notifications about project updates
- To deliver in-app notifications
- To enable chat functionality within projects and direct messages
- To send transactional emails (e.g. password resets, magic-link sign-in, email verification, invites, proposal notifications, payment notices, account deletion notifications) via our email provider (SendGrid)
4.4 Security and Operations
- To verify your identity and authenticate access
- To enforce role-based access controls
- To prevent fraud and unauthorized access
- To maintain and improve app security (including App Check)
- To debug issues and improve app performance (including via Sentry and Crashlytics)
4.5 Service Improvement and Marketing Measurement
- To analyze usage patterns and improve features
- To identify and fix bugs and technical issues
- To develop new features based on user needs
- To use feature voting input to prioritize product work
- To measure marketing effectiveness via Meta App Events (mobile)
4.6 Safety and Support
- To process report-user submissions and take action where appropriate
- To process account deletion requests
5. Information Sharing and Disclosure
5.1 Within Projects and Companies
Information is shared with authorized participants based on their role:
- Admins (Executives): Company administration and subscription management; access appropriate to their role within the company
- Project Managers: Access to company-scoped and project data, including financial information for their projects
- Field Staff: Access to assigned project details; ability to upload receipts and progress photos; track time and mileage; update milestones within their assigned scope
- Customers: Access to shared project information; ability to approve proposals and change orders; optional invoice payment; ability to manage team members for shared access
Company-authored terms and documents shared with customers on proposals are visible to those customers as configured by the company.
5.2 Third-Party Service Providers
Firebase (Google)
- Firebase Authentication: User account management
- Cloud Firestore: Database storage (including a dedicated users database and access-control caches)
- Firebase Storage: File and media storage
- Firebase Cloud Messaging: Push notification delivery
- Firebase Crashlytics: Crash reporting and diagnostics
- Cloud Functions: Backend processing
- Firebase App Check: Security verification
- Firebase Hosting: Web application delivery
Stripe
- SaaS subscription payment processing (web)
- Stripe Connect for customer project/invoice payments to contractor companies, including Connect account onboarding data processed by Stripe
App Store / Play Store
- In-app subscription billing and purchase validation (iOS and Android)
Sentry
- Error and performance monitoring; crash and breadcrumb data
SendGrid
- Transactional email delivery (invites, password reset, account deletion notifications, etc.)
Google (via Google Sign-In)
- Authentication when you choose to sign in with Google
Google Places API
- Address autocomplete and place details (requests sent via our backend)
Google Calendar / Microsoft Calendar
- Calendar connection and event data when you connect your calendar for scheduling
Apple (via Sign in with Apple)
- Authentication when you choose to sign in with Apple on iOS devices
Meta (Facebook)
- App Events for marketing attribution and analytics on iOS and Android
AI/LLM provider (e.g. Grok or your custom endpoint)
- Project support chat, receipt/image parsing, milestone suggestions, industry profile generation
Weather provider
- Visit forecast data when weather features are used
5.3 Legal Requirements
We may disclose your information when required to:
- Comply with applicable laws, regulations, or legal processes
- Respond to lawful requests from public authorities
- Protect our rights, privacy, safety, or property
- Enforce our Terms of Service
5.4 Business Transfers
In the event of a merger, acquisition, or sale of assets, your information may be transferred to the acquiring entity.
5.5 No Sale of Personal Information
We do not sell, rent, or trade your personal information to third parties for their marketing purposes.
6. Device Permissions
6.1 Camera Access
- Required for taking progress photos directly within the app
- Required for uploading profile pictures
- Required for capturing receipt images
6.2 Photo Library Access
- Required for selecting existing photos to upload
- Required for choosing profile pictures from your gallery
6.3 Location
- Used for mileage tracking (trip start/end). Optional if you enter miles manually. You can deny location and still use manual mileage entry.
6.4 Microphone
- Used for speech-to-text in project support chat when you use voice input, and for recording milestone audio notes when you choose that feature. Voice input for speech-to-text is typically processed on-device or by the platform; we do not store raw audio from speech-to-text. Milestone audio notes you intentionally record are stored as project evidence.
6.5 Biometrics (Face ID / Touch ID)
- Used locally on your device for sensitive actions (e.g. confirming financials or completion review). We do not receive or store biometric data.
6.6 Push Notifications
- Required for receiving project updates and alerts
- Can be disabled in your device settings or app preferences
Note: You can manage these permissions through your device settings. Denying certain permissions may limit app functionality.
7. Data Security
7.1 Technical Safeguards
- All data transmitted between the App and our servers uses TLS/SSL encryption
- Passwords are securely hashed before storage
- Firebase Security Rules enforce role-based access controls
- Firebase App Check protects against unauthorized API access
- Payment data is processed through PCI DSS-compliant Stripe infrastructure (web subscriptions and Connect payments)
7.2 Access Controls
- Role-based permissions restrict data access (Admin/Executive, Project Manager, Field Staff, Customer)
- Project data is only accessible to authorized participants
- User data is only accessible to the account owner and authorized administrators within applicable company and project rules
7.3 Security Limitations
While we implement industry-standard security measures, no method of electronic transmission or storage is 100% secure. We cannot guarantee absolute security of your information.
8. Data Retention
8.1 Account Data
- Your account information is retained as long as your account is active
- After you submit an account deletion request and we complete the review, we remove your profile from active systems (including related access-control cache copies used by the App)
- Residual data may remain in backups for up to approximately 30 days
8.2 Project Data
- Project data is retained for the duration of the project and as long as project participants maintain accounts
- Completed projects may be archived but remain accessible to authorized users
- Project deletion by the owner removes the project and associated data according to App behavior
- If you are only a participant on a project, that project data is not automatically deleted when your account is deleted (it remains for other participants)
8.3 Time Tracking and Mileage Data
- Time and mileage entries are retained for payroll, audit, and reporting purposes
- Historical data may be retained for tax and legal compliance
8.4 Calendar Data
- Calendar connection tokens and cached event data are retained until you disconnect the calendar
8.5 Chat Messages
- Chat messages within projects and direct messages are retained as part of App records
- Messages are accessible to participants with appropriate permissions
8.6 Crash Reports and Analytics
- Crash and diagnostic data (Crashlytics, Sentry) may be retained per our and the providers' retention policies (e.g. up to 90 days or as configured)
- Aggregated analytics and marketing measurement data may be retained longer for service improvement
- Meta App Events data is also subject to Meta's retention practices
8.7 AI and Support Data
- Prompts and responses sent to AI/LLM providers are subject to the provider's retention policy and our backend logs as needed for operation and support
9. Your Rights and Choices
9.1 Access and Correction
You can access and update your personal information through the Account screen in the App, including:
- Name and contact information
- Company and industry details
- Profile photo
- Notification preferences
9.2 Data Deletion
Account deletion is by request. You can:
- Submit an account deletion request via the in-app form (Account or landing screen) or via our published API (see our documentation).
- All requests are manually reviewed by our team; processing typically takes 3–5 business days.
- After approval, we remove your user profile from our active database and your access to projects.
- Project data where you are only a participant is not automatically deleted (projects remain for other participants).
- Residual data may remain in backups for up to approximately 30 days before permanent deletion.
9.3 Notification Preferences
You can manage notification preferences within the App:
- Enable or disable app notifications
- Enable or disable project update notifications
- Manage push notification settings on your device
9.4 Data Portability
To request a copy of your personal data, please contact us at the email address below.
9.5 Withdrawing Consent
You may withdraw consent for data processing where consent is the legal basis. Note that withdrawing consent may affect your ability to use certain features of the App.
10. International Data Transfers
Our services use Firebase and other cloud infrastructure that may process and store data in data centers located outside your country of residence. By using the App, you consent to the transfer of your information to countries that may have different data protection laws than your jurisdiction.
11. Children's Privacy
The App is not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13. If we become aware that a child under 13 has provided us with personal information, we will take steps to delete such information.
12. California Privacy Rights (CCPA)
If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA):
- Right to know what personal information we collect and how it is used
- Right to request deletion of your personal information
- Right to opt-out of the sale of personal information (we do not sell personal information)
- Right to non-discrimination for exercising your privacy rights
To exercise these rights, please contact us at the email address below.
13. European Privacy Rights (GDPR)
If you are located in the European Economic Area (EEA), you have additional rights under the General Data Protection Regulation (GDPR):
- Right to access your personal data
- Right to rectification of inaccurate data
- Right to erasure ("right to be forgotten")
- Right to restrict processing
- Right to data portability
- Right to object to processing
- Rights related to automated decision-making
Our legal basis for processing your data includes:
- Performance of a contract (providing app services)
- Your consent (for optional features like push notifications)
- Legitimate interests (improving our services, security, marketing measurement)
- Legal compliance
To exercise these rights or for GDPR-related inquiries, please contact us at the email address below.
14. Third-Party Links
The App may contain links to third-party websites or services (such as opening files in external applications). We are not responsible for the privacy practices of these third parties. We encourage you to review their privacy policies before providing any personal information.
15. Push Notifications and FCM Tokens
15.1 How Push Notifications Work
We use Firebase Cloud Messaging (FCM) to deliver push notifications about project updates, messages, and other important information.
15.2 FCM Token Storage
When you enable push notifications, we store:
- A unique FCM token associated with your device
- Platform information (iOS, Android, or web)
- Timestamp of token registration
15.3 Managing Notifications
You can disable push notifications by:
- Adjusting notification preferences in the App settings
- Disabling notifications in your device's system settings
- Signing out of your account
16. Error Monitoring (Sentry)
We use Sentry for error and performance monitoring. Sentry may receive error reports, stack traces, breadcrumbs (e.g. navigation or actions), and when configured, your user ID. This helps us diagnose and fix issues. Data is processed according to Sentry's privacy policy (https://sentry.io/privacy/). You cannot opt out of essential error reporting while using the App, but you can contact us with questions.
17. Voice (Speech-to-Text, Text-to-Speech, and Audio Notes)
The App may offer speech-to-text and text-to-speech in project support chat. Voice input for speech-to-text is typically processed on-device or by the platform; we do not store raw audio from that processing. When you record milestone audio notes, those recordings are stored as project content. If additional server-side voice processing is introduced, we will update this policy.
18. Meta App Events
On iOS and Android, we use Meta App Events to understand the effectiveness of our marketing and to measure events such as installs, registrations, and purchases. Meta may process device and advertising measurement identifiers according to its policies and your device settings. We do not sell your personal information. For more detail, see Meta's privacy policy: https://www.facebook.com/privacy/policy/.
19. SMS
When you text Trades Support (NEON-Systems, LLC) or otherwise opt in to SMS communications, we collect your phone number and message content. We use this information only to respond to your inquiries. We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.
20. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technologies, legal requirements, or other factors. When we make material changes:
- We will update the "Last Updated" date at the top of this policy
- We may notify you through in-app notifications or other means
- Your continued use of the App after changes constitutes acceptance of the updated policy
We encourage you to review this Privacy Policy periodically for any updates.
21. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us at:
NEON-Systems, LLC
Email: support@neon-systems.com
For data protection inquiries or to exercise your privacy rights, please include "Privacy Request" in your subject line.
22. Consent
By creating an account and using the Trades Support App, you acknowledge that you have read and understood this Privacy Policy and consent to the collection, use, and disclosure of your information as described herein. You may indicate your acceptance of this Privacy Policy through the account settings in the App.
---
Note: This Privacy Policy is provided for informational purposes and does not constitute legal advice. We recommend consulting with a legal professional to ensure compliance with applicable privacy laws in your jurisdiction.