Privacy Policy

Version 2026-10-24-draft-v4 · Draft prepared October 23, 2026
Effective date: pending finalization; this draft is presented for development use.

Draft — business details pending. This is a development-service draft, not a finalized public-launch policy. The operator must complete the details below and review the policy against actual operations before launch.

Operator legal name: [OPERATOR LEGAL NAME — TO BE PROVIDED]
Privacy contact: [PRIVACY CONTACT EMAIL — TO BE PROVIDED]
Mailing address: [BUSINESS MAILING ADDRESS — TO BE PROVIDED]

1. Who handles your information

Streamlined Connect provides QR Hub workspaces and public forms for participating businesses. The platform operator administers account and service data. The business named on a form receives the information submitted to that form and is responsible for its own use, communications, and separate privacy obligations. Submitting a request does not subscribe you to other businesses or a network-wide mailing list.

2. Information currently collected

Account information includes email addresses, password hashes, login-session records, business memberships, and the draft Terms version accepted at registration. Workspace records include forms, published versions, QR destinations, and administrative audit events.

Password recovery stores hashed, expiring reset tokens and short-lived hashed request identifiers for rate limiting. A completed reset invalidates existing sessions and outstanding reset links. For localhost development, recovery and password-change emails are saved in private project-local preview files. Configured SMTP delivery sends these security emails to the account's registered email address through the operator's chosen provider. Marketing delivery remains disabled.

Public forms collect the answers you provide, which may include your name, email, phone number, and service-request details. We also record submission time, originating QR code, published form version, request-consent wording, and any separate marketing choice. If marketing enrollment is offered, we record its wording, business, email when provided, and subscription or suppression state.

The web server may process connection and request metadata, such as IP addresses and requested paths, in operational logs. The app records aggregate QR visits, without advertising tracking or unique-person identification. Do not submit payment details, government identifiers, or sensitive medical or financial information through these general-purpose forms.

QR destinations may be forms, website redirects, or digital coupons. A QR landing request records its business, QR ID, destination type and time. Visit records contain no visitor name, email, IP address, browser ID or tracking cookie. Counts include clicks, reloads and automated visits, not unique people.

Coupon requests record the supplied name and email, source QR, offer version, request consent, optional newsletter choice and email status. Short-lived hashed client-IP records support abuse limits. The store-issued code is shown after submission and, where configured, emailed as a requested offer. These emails include opt-out controls, respect business-wide suppression, and do not enroll the recipient in newsletters. Local previews are stored in .local-mail.

3. How information is used

We use service data to authenticate users, maintain business workspaces, route forms, record customer requests, preserve consent and source history, investigate misuse, and operate the service. The receiving business may use your request information to respond. An optional newsletter choice is recorded separately. General newsletter delivery is currently disabled; submitting a form is not permission for unrelated marketing.

4. Access and service providers

Authorized owners and managers of the receiving business can view and export its submissions. Owners and managers may invite specific signed-in users to view one QR code’s historical and future results, including customer details and recorded consent choices. Invited viewers cannot edit results or use an export action. Sharing is revocable; previously viewed or copied information cannot be withdrawn. Invitation records include the invited email, inviter, expiry, and acceptance or revocation timestamps. Invitation links are not sent automatically. Platform operators with administrative access to the application or database may access data for service administration. Separate organizations do not gain access merely by participating in the platform. Businesses are responsible for information they export and use in their own systems.

The development installation stores data in its configured SQLite or PostgreSQL database on the deployment operator's infrastructure. No newsletter delivery provider is currently connected. Hosting and email-provider disclosures must be finalized when providers are selected. Information may also be disclosed when required by applicable law. Paid lead sales and public marketplace distribution are not enabled.

5. Browser storage

The dashboard uses per-tab session storage for its login token and selected business. An invitation token may be retained temporarily in session storage while you sign in or register to accept a shared-results invitation; it is cleared on acceptance or dismissal. The login token expires after 12 hours; signing out revokes that session. The current app does not install advertising cookies or third-party analytics scripts. Customer forms do not require a customer account.

6. Retention and security

Application records and operator-managed backups are retained until removed through an authorized administrative process. A final retention schedule and automated deletion process have not yet been established. Consent and suppression information may need to be retained to respect communication preferences and document prior actions. No automatic erasure period is promised by this draft.

Passwords are hashed, sessions expire, and private API access is checked against business membership or an accepted, unrevoked grant for a specific QR code. Additional production security and operating controls remain under development. No system can guarantee absolute security.

7. Your choices and requests

You may submit a request without agreeing to newsletters. Where a valid unsubscribe link has been issued, its single-action page stops all marketing from the named business without an account or additional personal information. Ordinary later form submissions do not clear that suppression. Unsubscribing from marketing does not delete your service request or prohibit a response to a request you make. Marketing delivery remains disabled in this development release.

For questions about a business's response or its copies of your data, contact that business through contact information it has independently provided. The platform privacy-request contact and process are not yet configured; the placeholder above is not a working contact channel. Finalize that channel and any applicable access, correction, or deletion procedures before public launch.

8. Changes

This page identifies its version. New material changes require a new version and appropriate notice. Historical published form wording and recorded choices are preserved rather than silently rewritten.