New Orchards Privacy Statement

New Orchards is owned and operated by General Blue Corporation ("General Blue," "we," "us," or "our"). This Privacy Statement describes how we collect, use, share, retain, and protect information when you use our website and related services. Our intent is to provide meaningful choices and respect the trust users place in us.

Our privacy principles: collect thoughtfully, explain clearly, protect responsibly, and improve continuously.

These principles guide feature design, operations, and communication across New Orchards.

How This Privacy Statement Works

This notice applies to information processed through New Orchards, including our pages, recipes, guides, planners, printable templates, conversion utilities, and other online resources that link to this notice. It also applies when you contact us, subscribe to updates, respond to optional surveys, or otherwise interact with us through forms or email.

This notice does not apply to third-party websites, apps, or services that we do not own or control, even when they are linked from our site. If you visit a third-party service from New Orchards, that service's own terms and privacy notice will govern how your information is handled there. We encourage users to review those notices directly.

We aim to keep this statement current. If features evolve, if legal requirements change, or if our operational practices are updated, we may revise this document. When we make material updates, we may provide additional notice through appropriate channels.

In general, New Orchards is designed to be useful without requiring account creation for most features. Many resources are available to browse and use without providing direct personal information. At the same time, like most modern websites, we do process technical and interaction data to operate the service effectively, understand performance, support advertising operations, and improve user experience over time.

These same privacy principles are reflected throughout this notice and in how we design and operate New Orchards.

Personal Data We Collect

The type and amount of information we process depends on how you use New Orchards. Some information is provided directly by you. Other information is collected automatically from devices and browsers as part of delivering an internet service. We may also receive limited operational data from service providers that support site functionality, communications, and security.

When you contact us or choose to subscribe, you may provide information such as your name, email address, and message content. If you participate in optional surveys or share product feedback, we process the information you choose to submit. If you request support, we may keep correspondence records to resolve your issue, improve support quality, and maintain continuity if follow-up is needed.

When you use the website, we may automatically process technical information such as IP address, browser type, device characteristics, operating system, referral source, pages viewed, timestamps, and diagnostic signals. This kind of information helps us provide pages efficiently, detect misuse, maintain uptime, investigate errors, and make practical improvements.

We also use cookies and similar technologies, including local storage, tags, and pixels. These technologies can support core site functionality, preference memory, traffic measurement, ad delivery and ad performance analysis, and fraud prevention. Some technologies are essential for the site to function. Others are optional or non-essential depending on legal requirements and regional rules.

For tools and templates, we may process data entered into forms, fields, or utilities to generate requested outputs. In some cases, this processing occurs in the browser. In other cases, it may occur on servers when needed for reliability, compatibility, or feature support. Where storage or history is available, we aim to make that context clear in the user experience.

We work with operational partners such as hosting providers, security services, usage measurement providers, and communication delivery services. These providers support website operation and communications under service agreements.

Please do not include sensitive personal information in standard contact forms unless we specifically request it for a clear and lawful purpose. Examples include government-issued identifiers, full financial account details, and health information.

To support transparency, we review data categories periodically and evaluate whether each category remains necessary for site operation, security, communications, or compliance. If a category is no longer needed for those purposes, we work to reduce or retire it from routine processing. This is part of our effort to keep data use proportionate to service needs.

We also distinguish between information that identifies a specific person and technical or aggregate signals used for diagnostics and performance review. While both categories can be important for service quality, they are not treated identically. Identity-linked information generally receives tighter access controls and stricter handling expectations than broad trend data used for product improvement.

Where practical, we design collection flows so users can understand what is optional and what is required for a feature to work. For example, a support form may require an email address so we can respond, while other fields may be optional context fields that users can choose to complete. This approach helps users share only what is needed for the interaction they want.

How We Use Personal Data

We use information to run New Orchards, support users, improve quality, maintain safety, and meet legal obligations. We do not treat personal information as an abstract asset; we use it for concrete and practical service purposes.

A core purpose is service operation. Technical and usage data helps us deliver pages and resources quickly, keep tools available, and troubleshoot reliability issues. Contact and communication information helps us answer questions and provide user support.

We also use information to improve product quality. We review aggregate usage patterns to understand which content people find helpful, where users encounter friction, and which areas may benefit from design improvements. We use these insights to prioritize updates, fix defects, and improve accessibility and readability.

We use information for communication as well. If you contact us, we use your information to respond. If you subscribe, we may send updates, guides, or announcements according to your preferences and applicable law. We seek to keep communications relevant and respectful, and we provide unsubscribe options for promotional messages. Where email or SMS delivery is used, messages may be delivered through a cloud communication service provider acting on our behalf.

Information is also used for security and integrity. Technical signals and logs can help detect unusual traffic patterns, reduce abuse, protect systems, and investigate incidents. Security processing supports both user protection and service continuity.

We may also process and retain certain information for legal and compliance support, including to meet legal obligations, enforce applicable terms, protect rights, prevent fraud, and resolve disputes.

Depending on jurisdiction, we may rely on one or more legal bases for processing, including consent, contract performance, legal obligation, and legitimate interests. Where consent is required, we provide opportunities to grant, withhold, or withdraw that consent in line with applicable law.

When we evaluate new uses of information, we consider whether the use is aligned with user expectations and whether a less intrusive option could achieve the same outcome. This review supports practical privacy-by-design decisions and helps reduce unnecessary expansion of data processing.

We also use operational metrics to improve response quality and support timeliness. For example, we may review queue times, completion rates, or unresolved support trends to identify where guidance can be clearer or where technical reliability can be improved. These internal quality activities are intended to improve user experience without changing the core purpose of the data relationship.

In limited situations, we may use de-identified or aggregated information for planning, forecasting, and service reliability analysis. We use this kind of information to understand broad patterns rather than to make decisions about a specific individual.

Cookies, Ads, and Similar Technologies

New Orchards uses advertising and related measurement technologies. To operate these systems, we and our partners may process technical and interaction data using cookies and similar technologies. These technologies can enable ad serving, ad frequency management, ad effectiveness reporting, and audience trend analysis.

We also use site and session-level measurement to understand how pages and tools perform and how users interact with key features. This helps us identify usability issues, improve layout and navigation, and reduce technical friction. Where possible, we use aggregate and trend-level analysis to inform improvements.

Essential cookies and technologies are used to maintain baseline functionality and security. Non-essential technologies, including certain measurement and advertising functions, may be managed through consent tools where required by law. Users can also control many technologies through browser settings, private browsing modes, and device-level ad personalization controls.

Disabling some technologies may reduce convenience or disable specific features. For example, preference memory may not work as expected, some embedded functionality may not load properly, or personalization may become less relevant. Even with these tradeoffs, user choice is important, and we support practical controls.

Some browsers provide "Do Not Track" signals. Because there is no universal standard governing those signals, our response may vary based on technical capability and legal context.

We do not sell contact lists as a standalone business. However, some legal frameworks define "sale" or "sharing" in ways that can include certain advertising-related disclosures. Where those legal definitions apply, we provide rights and controls consistent with the law.

Reasons We Share Personal Data

We share information in limited circumstances and for specific operational reasons. These disclosures generally fall into service-provider support, advertising and measurement support, legal and safety disclosures, and corporate transaction scenarios.

Service providers help us host, secure, maintain, and operate New Orchards. They may process information on our behalf under contractual terms that require confidentiality and appropriate data protection measures.

Advertising and measurement partners may receive technical and interaction data as needed for ad operations, campaign analysis, and performance reporting, subject to legal requirements and applicable user controls.

If referral links are present, merchants may process link identifiers and related technical signals to attribute referrals.

We may disclose information when reasonably necessary to comply with law, respond to lawful requests, protect users and services, investigate misuse, enforce rights, or prevent harm.

If we receive legal requests for information, we review them for validity and scope in line with applicable law. Where allowed, we limit disclosures to what is necessary and appropriate.

If ownership or structure of the business changes, personal data may be transferred as needed to continue providing services, subject to applicable legal requirements and privacy protections.

We do not provide a broad open-ended license for third parties to use user data for unrelated purposes. Our expectation is that data disclosures align with defined operational goals and legal obligations.

How We Keep and Protect Data

We retain information for as long as reasonably necessary to support the purposes described in this notice, including operations, support, security, legal compliance, and recordkeeping. Retention periods vary based on data category, context, and legal requirements.

Technical logs are often retained for limited windows tied to diagnostics and abuse prevention. Support communications may be retained long enough to resolve issues, maintain continuity, and preserve relevant records. Subscription data may be retained until a user unsubscribes or until the communication program is discontinued. Certain records may be retained longer when required by law or needed for dispute resolution.

If we detect suspicious automated activity, we may apply technical protections such as rate limits, challenge mechanisms, and temporary restrictions designed to reduce abuse while preserving access for legitimate users.

When information is no longer needed, we aim to delete, aggregate, or de-identify it where practical and appropriate.

We maintain administrative, technical, and organizational safeguards designed to reduce risk. These safeguards may include role-based access management, encrypted transmission channels, system monitoring, logging, and vendor oversight controls. Security is an ongoing process, and we adapt controls as operational needs and threat conditions evolve.

No internet-connected system can be guaranteed to be perfectly secure in all circumstances. Even so, we work continuously to reduce risk, strengthen resilience, and respond promptly when issues arise.

Accountability is supported through internal process. We aim to align policy statements with practical operations and to review controls over time so our privacy posture remains effective and credible.

In dispute, audit, or incident contexts, some records may be retained longer than standard windows when reasonably necessary. We seek to keep those extensions limited to the scope and duration required by the specific matter.

Our security and retention approach includes periodic validation activities. These may include reviewing access assignments, checking that retention logic aligns with current policy, and confirming that operational controls are functioning as intended. These reviews help us detect gaps early and support continuous improvement.

We also recognize that security includes both technology and process discipline. Technical controls are important, but clear procedures, role accountability, and consistent operational habits are equally important for reducing risk over time. For this reason, we treat privacy and security as shared responsibilities across product, support, and operational functions.

When third-party service providers are involved, we expect contract terms and technical practices that support confidentiality, integrity, and appropriate data handling. While no vendor environment is risk-free, we seek partners whose controls are suitable for the services they provide and whose obligations align with our privacy expectations.

Where Data Is Processed

New Orchards may be accessed from many regions. We and our service partners may process data in countries other than your own. Data protection laws differ by region, and rights can vary depending on where you reside.

Where required, we use legal and contractual safeguards intended to support lawful cross-border transfers. We also seek to apply consistent privacy practices across operations, while honoring jurisdiction-specific requirements where applicable.

If local law grants you specific rights not fully detailed in this notice, applicable law controls. We will work in good faith to handle requests in accordance with the legal requirements that apply to your location and the nature of your request.

Information for Families

New Orchards is intended for a general audience and is not directed to children under the age of 13. We do not knowingly collect personal information from children under 13.

If you believe a child has provided personal information through our services, please contact us at privacy@generalblue.com. We will review the report and take appropriate steps, which may include deleting the information or restricting associated processing as required.

We encourage parents and guardians to help children understand responsible online behavior, including how and when to share information on websites and digital services.

How to Access and Control Your Data

Depending on applicable law, you may have rights related to your personal information. These may include rights to access information, request correction, request deletion, request portability, object to certain processing, withdraw consent where consent is the legal basis, and opt out of some targeted advertising or sharing activities.

To submit a request, contact privacy@generalblue.com and provide enough detail for us to identify relevant records. Including the email address associated with your interaction and a clear description of your request can help us respond faster.

For some requests, we may need to verify identity to protect privacy and prevent unauthorized disclosures. Verification needs may vary based on the sensitivity and scope of the request.

In some situations, legal exceptions or technical constraints may affect how we can fulfill a request. If this happens, we will explain the basis for our response as appropriate.

If you are subscribed to promotional communications, you can opt out at any time by using the unsubscribe link in the message. Operational communications that are necessary for service management may still be sent when appropriate.

When a user opts out of promotional communication, we process that request as promptly as practical and may maintain suppression records as needed to honor that choice.

We want users to have practical control, not just formal language. If you are unsure how to exercise a choice, contact us and we will provide guidance.

If your request is broad, we may follow up to clarify scope so we can provide a more complete and useful response. Clarifying scope can help reduce delays and ensures we focus on the information or action that matters most to you.

Where local law provides additional rights, we aim to honor those rights in a straightforward process. If a specific right is not available in your jurisdiction, we still try to provide practical assistance where possible, including guidance on available options and settings.

If we deny or partially deny a request, we aim to explain the reason in understandable terms, including applicable legal or operational constraints. Clear explanations help users understand outcomes and next steps.

Privacy in Practice

Privacy is not only policy language; it is also daily operational practice. In day-to-day service delivery, privacy decisions can involve tradeoffs among usability, reliability, security, and legal requirements. Our objective is to make proportionate decisions that support users while keeping processing appropriate to the purpose.

For example, when a feature is unstable, we may temporarily collect additional technical diagnostics so we can resolve reliability issues and restore service quality. We then evaluate whether those diagnostics can be reduced, narrowed, or retired after the issue is resolved. This helps us avoid indefinite collection that is no longer necessary.

In communications workflows, we focus on avoiding over-collection. If a support issue can be resolved without additional personal details, we do not request more information. If added context is necessary, we ask only for information reasonably needed to investigate and respond.

For measurement and performance analysis, we emphasize trend-level insights that help identify page friction, usability concerns, and reliability issues. We use this information to improve design and functionality and to prioritize practical product updates.

For advertising-related processing, we aim to explain clearly that technical identifiers and interaction signals may be used for delivery, frequency management, and measurement functions. Where required, we provide controls and consent options so users can make informed choices.

In vendor relationships, we assess whether each provider serves a defined operational purpose and whether contractual and security protections are appropriate to that purpose. We expect service providers to operate within agreed boundaries and to support confidentiality obligations.

In security operations, prevention and response work together. Prevention includes controls such as role-based access, monitoring, and secure transmission channels. Response includes identifying anomalies, triaging incidents, containing risk, and applying corrective actions.

In retention management, we balance practical needs and privacy principles. Retaining data indefinitely is generally not a strong privacy practice, while retaining too little can impair security review, support continuity, and legal compliance. We therefore use category-based retention logic and periodic review.

As part of implementation quality, we also look for opportunities to simplify data pathways. Simpler pathways are generally easier to monitor, easier to document, and less likely to produce unintended data handling side effects. This helps us keep real-world operations aligned with the commitments described in this statement.

We encourage teams to document meaningful changes in processing behavior so policy updates can remain timely and accurate. Maintaining this linkage between operations and policy helps avoid drift between what is written and what is done.

When issues are identified, remediation may include process updates, control refinements, documentation changes, and monitoring enhancements. We view these adjustments as part of routine stewardship rather than one-time corrections.

Keeping This Privacy Statement Clear and Current

We want this notice to remain understandable, accurate, and useful over time. Readability is a privacy feature: when people can easily understand a notice, they can make better decisions about their information.

Where this notice uses terms such as "may," that wording reflects variation by feature, region, legal context, and configuration. It does not mean every practice applies in every circumstance. It means processing depends on context, and we aim to describe that context as clearly as possible.

When users submit information in free-form fields, we encourage limiting sensitive details unless specifically requested. This reduces the risk of unnecessary data exposure and helps keep support processing proportional to the request.

We keep statement commitments aligned with real operations as products and legal requirements evolve.

We also review common support patterns to identify where users need stronger privacy controls or clearer choices in product flows.

When introducing new features or changing data flows, teams are expected to evaluate privacy impact early, including whether the change is necessary, proportionate, and secure.

If changes affect how personal data is used or shared, we update controls and disclosures so users can make informed decisions.

We aim to keep rights-request handling predictable, with clear outcomes and next steps when requests are fulfilled, partially fulfilled, or denied under lawful exceptions.

Updates and How to Contact Us

We may update this statement from time to time to reflect feature updates, legal requirements, or operational refinements. If changes are material, we may provide additional notice through the site or other appropriate channels.

For privacy questions, concerns, or requests, contact:

General Blue Corporation
privacy@generalblue.com

We are committed to treating privacy as an ongoing responsibility. Our goal is to keep New Orchards helpful, respectful, and trustworthy by pairing clear communication with practical safeguards and user-focused controls.

We appreciate your trust and your feedback. If any part of this notice is unclear, we invite you to reach out. We value the opportunity to improve and to support our users with transparency and care.

Our commitment is to keep this privacy statement accurate and aligned with real operational practice so users can understand how information is handled.

If you contact us with a privacy concern, we will make reasonable efforts to respond with clear next steps, expected timing, and any information needed to move your request forward. We value respectful communication and aim to handle privacy inquiries with care.

We appreciate users who raise privacy concerns or requests. That feedback helps us improve controls, strengthen safeguards, and support a more reliable privacy experience.