YardBird

Privacy Policy

This Privacy Policy explains how YardBird, the YardBird applications, website, customer-facing estimate and invoice pages, and related services (“YardBird,” “we,” “us,” or “our”) collect, use, disclose, retain, and protect information. YardBird is business-management software for landscaping and field-service businesses.

1. Information YardBird handles

Depending on how the Service is used, YardBird may process:

• Account information: email address, Firebase authentication identifiers, display name, business name, legal-acceptance records, and account status.
• Business profile information: company name, phone, email, website, tax settings, crews, team/roster members, seat assignments, service rates, and subscription status.
• Customer and field-service records: customer names, addresses, phone numbers, email addresses, estimates, jobs, schedules, recurring-service plans, invoices, notes, issue records, service measurements, pricing, and status history.
• Photos: before/after or issue photos a user chooses to capture or upload for YardBird work records. Camera access is used only when a user chooses a photo feature.
• Payment and billing metadata: Stripe customer, subscription, connected-account, checkout, payment, refund, receipt, payout-readiness, and transaction reference data. YardBird does not store full payment-card numbers.
• Sync and technical information: app-generated device/sync identifiers, timestamps, cloud-sync state, diagnostic/error information needed to operate the Service, and security logs maintained by service providers.
• Communications and delivery records: email recipients and transactional email-delivery status for estimates or invoices. When a user chooses “Text secure link,” YardBird opens the device’s normal messaging composer with a link prefilled; YardBird does not send, read, or store the user’s SMS conversation.

2. How information is collected

Information is provided by YardBird account holders and authorized users, generated through use of the Service, supplied by customers who interact with secure estimate or invoice pages, or returned by service providers such as Stripe after payment or subscription activity.

3. YardBird’s privacy roles

YardBird may have different privacy roles depending on the information. For account administration, YardBird subscription billing, security, legal acceptance, support, and operation of the YardBird platform, YardBird generally determines why and how that information is processed.

For customer, job, estimate, invoice, team/roster, and field-service data that a landscaping business places into its workspace, the landscaping business generally decides why that data is collected and used. To the extent applicable privacy law distinguishes controllers/businesses from processors/service providers, YardBird generally processes that workspace data on behalf of and under the instructions of the YardBird business. Requests concerning data controlled by a landscaping business may need to be directed to that business; YardBird will provide reasonable assistance where required by applicable law.

4. Why YardBird uses information

• Authenticate users, record legal acceptance, and operate the YardBird workspace.
• Sync authorized business records across signed-in devices.
• Create, send, display, and manage estimates, jobs, invoices, recurring services, and customer payment links.
• Store and synchronize user-selected work photos.
• Operate YardBird subscriptions, seats, payment status, refunds, and connected Stripe payment features.
• Deliver transactional emails and secure customer links.
• Protect YardBird, users, customers, and payment systems from misuse, fraud, and security threats.
• Comply with legal obligations and enforce YardBird’s Terms of Service.

5. Service providers and disclosures

YardBird may disclose information as necessary to providers that help operate the Service, including:

• Google / Firebase: authentication, Firestore database services, cloud storage, Cloud Functions, hosting, and related infrastructure.
• Stripe: YardBird SaaS subscription billing and, when enabled by a business, customer payments through Stripe-connected payment services.
• Google / email infrastructure: transactional estimate and invoice email delivery.
• Customer recipients: information intentionally included by a YardBird business in secure estimate, invoice, or payment pages.

YardBird may also disclose information when reasonably necessary to comply with law, protect rights or safety, investigate fraud or abuse, or in connection with a merger, acquisition, financing, or transfer of the YardBird business or Service.

YardBird does not currently sell personal information and does not use YardBird business/customer data for third-party targeted advertising. If that practice ever changes, this Policy and any legally required choices will be updated before the change takes effect.

6. Secure customer links

YardBird can generate token-protected public estimate and invoice links. Anyone who receives a valid link may be able to view the information intentionally placed on that customer page, so businesses should send links only to intended recipients. YardBird’s current secure-link implementation is designed to expire links after 45 days. Links may stop working sooner when an estimate is canceled, replaced, or the related YardBird account is deleted.

7. Payments

Payment-card details are collected and processed by Stripe, not stored directly by YardBird. YardBird receives transaction and account metadata needed to show payment status, receipts, refunds, subscription state, and connected-payment readiness. Stripe may retain financial records under its own legal, fraud-prevention, tax, and compliance obligations.

8. Data retention and deletion

YardBird retains active workspace data while an account is in use and as needed to provide the Service. Users can initiate permanent account deletion inside YardBird. When in-app deletion completes, YardBird removes the Firebase authentication account, the primary YardBird Firestore business workspace, YardBird cloud photos, and active public estimate/invoice token records, and cancels an active YardBird SaaS subscription before deletion.

Users who cannot access the app can use the account-deletion request page. Verified emailed requests are normally completed within 7 days. Limited provider logs, security records, system backups, or transaction records may remain for a period when reasonably necessary for security, disaster recovery, fraud prevention, legal compliance, tax, accounting, or payment-processing obligations.

9. U.S. privacy rights and requests

Privacy rights differ by state and some state privacy statutes apply only after specific business-size, revenue, data-volume, or other thresholds are met. Where applicable law gives you rights in personal data that YardBird controls, you may request:

• confirmation of whether YardBird processes your personal data and access to that data;
• correction of inaccurate personal data;
• deletion of personal data, subject to lawful exceptions;
• a portable copy of eligible personal data;
• opt-out rights relating to sale, targeted advertising, or certain profiling where those rights and activities apply; and
• freedom from unlawful discrimination for exercising applicable privacy rights.

Submit a request to yardbird.service@gmail.com. YardBird may reasonably verify identity and authority before completing a request. We will respond within the time required by applicable law. If YardBird denies a request and applicable law provides an appeal right, reply to the decision or email the same address with the subject “Privacy Appeal”. We will review the appeal and provide any further complaint instructions required by applicable law.

If the request concerns information that a landscaping business controls in its YardBird workspace, the individual should ordinarily contact that landscaping business first. YardBird will assist the business with qualifying requests where required by law or contract.

10. Security and incidents

YardBird uses authenticated cloud services, encrypted network connections provided by its infrastructure, backend-managed credentials, and token-protected customer links. No online service can guarantee absolute security. Users are responsible for safeguarding credentials and devices. If a security incident requires notice under applicable law, YardBird will provide the notices required by that law.

11. Age and children

YardBird login accounts are intended for adults age 18 and older and the Service is not directed to children. A YardBird business may maintain lawful roster/work records for workers who do not have a YardBird login, but users under 18 may not create or hold a YardBird login account at launch. YardBird does not knowingly offer login accounts to children under 13.

12. International processing and launch scope

YardBird and its providers may process information in the United States and other locations where those providers operate. YardBird’s initial commercial release is intended for customers in the United States. International availability, if offered later, may be subject to additional terms and privacy disclosures.

13. Changes to this Policy

YardBird may update this Privacy Policy as the Service, legal requirements, or data practices change. The version and effective date above identify the current Policy. When an update requires renewed acceptance or acknowledgement, YardBird may present the updated policy before the workspace becomes available. YardBird records acceptance by individual user and retains version history in the protected workspace.

14. Contact

YardBird is operated by Joseph Bailey, a Texas sole proprietor.
Privacy and support inquiries: yardbird.service@gmail.com
Website: yardbird-services.com