NOD

Privacy

Current pre-release draft — August 26, 2026

NOD is in development and is not open for public enrollment. This pre-release notice describes the information NOD is designed to process and the commitments governing approved testing. It is not a claim of completed legal, carrier, or app-store approval. Final consumer language, retention periods, service-provider disclosures, and youth-law terms require qualified review against the finished app before release.

Who we are

NOD is a project of Cedar Ridge Creative LLC. Questions about privacy may be sent to privacy@cedarridgecreative.com.

Scope and current status

This notice applies to NOD project pages and specifically authorized pre-release testing operated by Cedar Ridge Creative LLC. The public website does not collect NOD location information. Public consumer enrollment, production location collection, Premium billing, and the Day in Brief service are not currently active through this website.

Information NOD is designed to process

Depending on the features a person chooses and the final release configuration, NOD is designed to process the following categories of information:

• Account and profile information: mobile number, optional verified recovery email, name, username, optional profile photo, Heartwood participation, role, invitation state, and the derived adult or teen age path.
• Communications: Nods, replies, private pairwise messages, and the delivery, receipt, and read states needed to show the conversation accurately.
• Consent and relationship records: Heartwood relationships, organizer authority, sharing choices, named viewers, disclosure versions, and guardian-and-teen acceptance evidence when applicable.
• Device, authentication, and security information:installation credentials, session and active-device state, login and transfer events, push registrations, abuse-prevention evidence, and privacy-safe operational records.
• Location information, only when enabled: current or recent device location, time, freshness and availability facts, the rolling 15-minute Free recent-course window, and—if Premium is activated—the planned seven-day history, broad travel transitions, and approximate time at user-approved saved places.
• Transparency and support records: shared Activity, location-view evidence, sharing and role changes, security events, and information a person chooses to provide when asking for help.

How information is used

NOD is designed to use information only to provide requested features; authenticate accounts; deliver Nods, messages, invitations, and security notices; enforce consent and access rules; display an authorized location or history; prepare a requested Day in Brief; maintain shared transparency; prevent abuse; provide support; protect the service; and meet applicable legal obligations. Information collected for one purpose will not be repurposed incompatibly without an appropriate new disclosure and choice.

Location choice, collection, and disclosure

Location sharing begins off. Joining a Heartwood, becoming an organizer, purchasing Premium, granting an operating-system permission, and granting a particular person access are separate decisions. A person may decline location sharing and continue using Nods and private messaging. Sharing must remain visible and revocable.

Acquiring or storing a location does not authorize anyone to see it. Before coordinates or history are returned, NOD is designed to verify the viewer, active relationship, current person-specific permission, session and device authority, and any required fresh authentication. Every location view must create durable evidence in shared Activity. NOD does not provide a covert or continuously visible tracking dashboard.

Information NOD does not use or infer

Heartwood is designed from bounded event classifications and smoothed patterns—not private message text, semantic content analysis, raw coordinates, or response speed. NOD does not use raw location data for advertising or place raw coordinates in general analytics, crash reports, ordinary logs, or lock-screen notifications.

A requested Day in Brief may describe approximate movement, user-approved saved places, broad transitions, and gaps in available phone evidence. It is not designed to determine why a person traveled, who accompanied them, whether they were truthful, whether their behavior was unusual, or what private messages said. It does not provide a minute-by-minute investigative account.

Service providers and disclosures

Cedar Ridge Creative may disclose only the information reasonably necessary to vetted service providers performing functions such as secure hosting, authentication, SMS delivery, push delivery, maps, weather, payment processing, support, security, or a requested Day in Brief. Provider selection, contract terms, retention, training or secondary-use restrictions, security controls, deletion evidence, and regional processing remain approval gates before activation.

Precise location and private message content are not sold or used for advertising. Mobile numbers and SMS consent records are not sold or shared with third parties or affiliates for advertising, marketing, or promotional purposes. NOD may disclose information when required by law or when reasonably necessary to protect rights, safety, and service security, subject to the final reviewed policy.

Mobile information

Mobile numbers and SMS consent information are not sold or shared with third parties or affiliates for marketing or promotional purposes. They may be provided to service providers only as needed to deliver requested messages, prevent abuse, maintain security, or comply with law.

Children and teens

The planned initial release is U.S.-only and for people age 13 or older. Version one does not support enrollment by children under 13. Teen participation requires the approved guardian-authority and teen acceptance path. Joining, reviewing the exact named-organizer set, and choosing whether to share location remain separate steps. The final youth disclosures and consent language require qualified review.

Retention and control

The approved product direction limits Free recent-course location to a rolling 15-minute window and Premium location history initially to a rolling seven-day window. An upgrade does not create history that was never collected. A downgrade or lapse is designed to stop Premium collection and delete location information outside the Free window. Exact production periods and procedures for messages, Nods, consent evidence, audit records, summaries, exports, account deletion, and legal holds remain release-gated and will be stated before launch.

The released product is intended to provide understandable controls to review sharing, revoke location access, correct appropriate account information, request export where applicable, and request account and data deletion subject to lawful and safety-related exceptions.

Security

NOD is designed around server-enforced authorization, installation-bound credentials, encrypted native session storage, one active phone and session per account, minimum-necessary access, private coordinate storage, and privacy-safe audit evidence. Client statements about identity, device, role, consent, session, or location authority do not establish permission by themselves. No method of storage or transmission can be guaranteed completely secure. Security claims must be verified through independent review and physical-device testing before launch. Additional detail appears in the protected NOD security overview.

Compliance and review status

NOD is being designed around data minimization, purpose limitation, prominent disclosure, affirmative choice, revocation, access transparency, and age-appropriate safeguards. Final compliance cannot be determined from product copy alone. It depends on the released implementation, current law, provider practices, app-store declarations, and qualified legal, privacy, security, and youth-safety review.