Privacy Policy

RafterNod account creation asks contractors for a name, email address, and password. The application also has account and authentication records. Its session model includes optional IP address and browser user-agent fields; the available code does not establish whether those fields are populated for every session or how long session data is kept.

Project records can include a project name and status. Progress records can include draft or published update text and publication times. Photo records are associated with projects and can include a filename, file type, file size, optional explanation, and a customer-visible setting. Voice-note records are associated with projects and can include a filename, file type, file size, and duration.

A contractor can create a customer progress link for a project. The linked view can show the project name and status, published progress updates, and photos marked customer-visible. The public progress route uses the link token to return this information without requiring a contractor sign-in, so anyone who has the link may be able to view the information it exposes.

Review what is published and marked customer-visible before sharing a project link.

These records support contractor account access, project and progress workflows, photo and voice-note attachments, and customer progress views. This describes functions present in the app; it is not a complete statement of legal purposes or legal bases for processing.

RafterNod offers a 14-day free trial that does not require a card to start. The available paid plans are $59 per month or $588 per year. Subscription checkout hands off to a Stripe-hosted checkout page; the RafterNod app does not present an embedded card-entry form.

The exact information sent to Stripe, the payment parties’ legal roles, and any other payment-related disclosures need owner confirmation before this draft is final.

The repository does not establish the following privacy practices. They are left open for RafterNod’s owner to confirm rather than presented as facts:

• The legal name and location of the organization responsible for the service, and the privacy laws and legal bases that apply.
• All hosting, file storage, analytics, email, authentication, and payment providers that receive information, along with their roles and data locations.
• Retention periods, deletion and backup behavior, and how account or project-data deletion requests are handled.
• Whether session metadata, cookies, or analytics are collected in production and what notice or consent is required.
• Security practices, cross-border transfers, privacy rights, and the process and timing for responding to privacy requests.

For questions about this draft, contact RafterNod at rafternod@polsia.app. The owner should confirm whether this is also the correct channel for formal privacy requests.