Privacy Policy
Hope Act Committee Workspace Hub · Effective · Version 2026-09-21.2
This policy explains how the Hope Act Committee Workspace Hub handles information used for committee coordination. The Administrator is the Hub privacy contact. Use the private request form below to contact the Administrator; the committee email inbox is shared with the Circle. Send a question or request through Privacy Requests & Appeals; an account is not required.
Information We Collect
- Accounts And Security: names, usernames, roles, password hashes, sign-in sessions, invitation and recovery records, dated Terms agreements and Privacy Policy acknowledgments with their document versions, and security events. Passwords are not stored as readable text.
- Committee Work: commitments, owners, dates, progress notes, evidence links, research, policy contributions, shared calendar events, meeting availability, minutes, decisions, and follow-ups.
- Member Care: optional capacity and connection check-ins, participation interests, follow-up preferences, Circle replies, and engagement next steps. New check-ins and engagement follow-ups are available to the Administrator and verified Coordinator Circle accounts. Earlier records retain their original author-and-Administrator access until the author explicitly shares a check-in with the Circle. These records are excluded from shared plans, calendar feeds, spreadsheet connections, and public reports. Naming a follow-up owner does not share a record with that person.
- Drafts And Imports: private recovery copies of supported unfinished forms and text extracted from meeting summaries or transcripts. The source-import flow saves extracted text when you confirm the import; it does not upload the original PDF or Word file.
- Preferences And Connections: followed work, reminders, spreadsheet links, hashed connection credentials, and connection activity.
- Requests And Technical Information: privacy-request contact details, correspondence and status, plus operational information needed to serve and protect the Hub. Hosting providers may process IP addresses and request logs. The application uses hashed rate-limit identifiers.
Open And Anonymous Member Care
The public Member Care form does not require an account. You can provide your name and optional email address, or choose Anonymous. Anonymous submissions are not linked by the application to a Hub account and cannot include name or email fields. Your own message may still identify you. Hosting providers may process technical logs such as IP addresses; anonymous submission does not promise network-level anonymity.
The Administrator and verified Coordinator Circle members can read submitted messages and any contact information you choose to provide. A private receipt link lets its holder read that conversation and withdraw the message. Treat this link as a secret. Only a hash of its secret is stored in the database. Replies are available at that link; automatic email notifications are not sent. Public messages and replies are excluded from shared Tracker and spreadsheet exports. Care messages and hashed receipt credentials are included in encrypted recovery backups.
Member Care Email Invitations
The Administrator and verified Coordinator Circle members may save email drafts, recipient addresses, and send records for members who agreed to committee emails. Contact details supplied in check-ins are not added automatically. Drafts, recipient lists, and send history are shared with those accounts. Delivery setup remains with the Administrator. When delivery is connected and a Coordinator Circle member or the Administrator confirms a send, Resend processes the recipient address, message, sender, and reply address. Each recipient receives a separate email. Replies go to the shared Committee Inbox. Care submissions and conversation replies are not sent automatically.
Every invitation includes an unsubscribe link. Opening the link does not change your preference; confirming it, or using an email client’s one-click unsubscribe, blocks future Member Care sends through the Hub. Messages already accepted by the delivery service may still arrive. Unsubscribe records store a hash of the address. Email drafts, send records, and unsubscribe records are included in encrypted recovery exports. The Hub does not add open or click tracking to these messages; the delivery provider has its own processing and retention practices.
Committee Email Updates
Signing up for committee updates is optional and separate from Hub access and Member Care emails. We collect your email address, optional name and interests, consent record, and confirmation and unsubscribe dates. A confirmation email is sent through our existing Resend connection. You join the list only after confirming your address. Only the Administrator can view or export this subscriber list. Use the link in your committee email to unsubscribe without signing in, or contact the committee for help. We retain the minimum subscription and consent record needed to honor your choices. An email already handed to the delivery service may still arrive.
Why We Use Information
We use this information to provide access, coordinate committee work, preserve decisions, support members, prevent abuse, recover records, and respond to requests or legal obligations. Use only information necessary for these purposes. Do not put medical records, government identification, financial account details, attorney-client communications, or confidential Board personnel files into this workspace.
Restricted Documents
Restricted partner workbooks are available only to the Coordinator Circle, including the Administrator, and specifically authorized readers. A one-time code sent to the authorized registered email is required to download a workbook. A specifically authorized email reader receives access only to that document and gains no other Hub permissions. Codes expire after 10 minutes and verified document access after 15 minutes; access linked to a Hub account also depends on its current role, active status and verified email. An existing Hub sign-in session is not required to request a document-only code. Code hashes and temporary verification records are stored to prevent code reuse and abuse. The email provider receives the code message and recipient address, not the workbook.
Who Can See It
Signed-in members can see shared commitments and committee research and policy work. Coordinators can organize policy sprints, research, meeting polls, and minutes and may access imported meeting source text. Draft meeting notes created without an import may be visible to members; imported drafts remain limited to coordinators and the Administrator until finalized. Review meeting notes before saving or finalizing.
Your submitted progress notes and their evidence links are visible to you and the Administrator. Other coordinators receive only their own progress submissions. Private automatic recovery drafts are accessible through the application only to the account that wrote them. Authorized hosting administrators may have infrastructure-level access needed to operate or restore the service. The Hub is not end-to-end encrypted.
Financial Stewardship
Financial requests record the requester, purpose, amount, proposed payee or funder, related commitment, budget line, dates, restrictions, and supporting references. An unsubmitted draft is visible through the Hub only to its author. Once submitted, the requester and the Administrator can read the request and later updates, including a draft made after it is returned for information. Other members and coordinators cannot read individual requests.
The Administrator records organizational review, decision, and payment references and prepares monthly reports. Signed-in members can read published aggregate financial updates and recorded stewardship roles and adoption information. Draft reports and reconciliation and budget source references remain restricted to the Administrator. The Hub records external decisions; it does not verify a person’s organizational financial authority or process payments.
Financial records and change history are retained for accountability and included in recovery exports. Withdrawing a request retains its contents and history; it does not delete the record or reverse a financial decision. Individual requests and private financial references are not copied into shared task exports, Google Sheets, or calendar feeds. Do not enter bank account details, payment credentials, receipt contents, confidential Board records, or sensitive allegations. Keep those in approved, restricted organizational storage.
Committee Inbox And Text Verification
Emails sent to the committee mailbox are processed by Resend and stored in the Hub for authorized Coordinator Circle members and the Administrator. Ordinary email drafts are shared. Prepared personal invitation emails are restricted to the Administrator. Email is not anonymous: sender and recipient addresses, subjects, text, attachment metadata, and delivery references are recorded. Remote email images are not loaded. Attachments are retained by Resend and downloaded only on request; the Hub does not scan attachments for malware. The Hub collects external email addresses into a committee contact directory and flags messages that appear to request Hub access for Administrator review. Automated senders are skipped. A public Request Access form records the supplied name, email, and committee connection. Requests and directory entries do not prove identity, create accounts, or subscribe anyone to Member Care emails. Only the Administrator approves access levels and prepares and sends personal invitations. Request and contact records are included in recovery exports. A coordinator reviews outgoing messages before sending. Replies to committee emails go to the shared mailbox, not a personal inbox.
Optional text verification uses Twilio Verify to send and check security codes. A member must agree to security texts and verify their number before activation. Twilio receives the mobile number and delivery information. The Hub stores an encrypted phone number, its last four digits, hashed recovery codes, consent and security events, and temporary verification references. Phone numbers are not displayed to other members. Text verification does not subscribe anyone to marketing. Message and data rates may apply. Members can remove it with their password and a current verification or recovery code. The Administrator uses the authenticator option.
Providers And Optional Connections
The Hub uses a managed hosting service and Cloudflare infrastructure for records and stored files. Service providers process data to deliver and secure the service under their applicable arrangements. This Hub uses its own sign-in. Draft-minutes formatting and research text stay within the Hub’s existing processing workflow. Minutes Intelligence is an optional Administrator-controlled Claude connection for direct Tracker imports. When connected, analysis sends the uploaded extracted minutes, an optional meeting date, member and task-owner names, and a bounded set of shared Tracker task identifiers, titles, owners, deadlines, and statuses to Anthropic to suggest actions and match stated prerequisites. It does not receive private reminders, Member Care records, inbox messages, or financial requests. Uploaded minutes are treated as source material; the service cannot save tasks, send messages, or finalize records. A permitted coordinator reviews and selects tasks before saving. Built-in extraction remains available without sending text to Claude. The connection key is encrypted, visible only through connection status, and excluded from recovery downloads. Budget Guide is an optional automated conversation service. When it is connected and you ask a question, the current proposal and recent conversation are sent to its service provider to prepare suggestions. Suggestions can be wrong and are applied only when you choose them. The Hub does not request persistent provider storage of these conversations. The conversation is not saved as a Hub record; text you apply becomes part of your proposal. Budget proposals and their change history are included in recovery exports. Draft proposals are visible to their author; submitted proposals are also visible to the Administrator. Preparing an email shares that message and the attached proposal with permitted Coordinator Circle accounts. Sending requires a separate confirmation.
All signed-in members can view the Shared Committee Calendar. If you choose an external calendar subscription, the app receiving your private link can obtain the titles and dates included in that feed. The Shared Committee Calendar feed includes shared task deadlines, dated policy sprints, confirmed meetings, and committee events. My Commitments Only includes assigned or followed task deadlines and confirmed meetings. These feeds exclude member care, event descriptions, and meeting joining details. Anyone with that link can read that feed until it expires or is revoked. The Administrator’s Google Sheets connector copies shared plan records into the connected spreadsheet and can send approved edits back. Google, calendar providers, and sites opened through document links have their own privacy practices. Disconnecting a connection stops future authorized requests; it cannot erase copies already downloaded elsewhere.
Information may also be disclosed when required by law or reasonably needed to protect accounts, people, or the service. We do not sell personal information or use it for targeted advertising or automated decisions with legal or similarly significant effects. The application does not add advertising trackers or optional analytics cookies. Its sign-in cookie is necessary for authentication.
Retention And Recovery
Sign-in sessions expire after seven days unless revoked sooner. Private draft recovery is available for up to 30 days; expired copies are cleared during authenticated use or when accessed. Governance records, contributions, reviews, security records, and source text are retained for committee continuity, accountability, and applicable legal needs. There is not yet a single automatic deletion period for these records. The Administrator reviews deletion requests and records any retention reason or legal hold.
You can withdraw your own check-in, which removes its text and reply from the active Hub while retaining a minimal withdrawal record. Older backups may still contain earlier copies. Member Care check-ins are voluntary, and the Hub does not score engagement or infer personal wellbeing from sign-in activity.
Encrypted recovery exports can contain Member Care records, committee records, account password hashes, request history, and imported source text. They include account permission settings, encrypted authenticator secrets and phone numbers, inbox records, and hashed MFA recovery codes, so security restrictions can be restored. They exclude active sessions, invitations, password-reset recovery codes, connection credentials, provider encryption keys, temporary text verification requests, and private unfinished drafts. Email attachment bytes remain with Resend and are not included in Hub recovery exports. Copies held outside the Hub have to be controlled and retired by their custodian. Provider recovery history may retain older data for its applicable retention period. Approved deletions must be reapplied if an older backup is restored.
Security
Controls include HTTPS, password hashing, secure session cookies, request limits, version checks, and server-enforced role permissions. The Administrator can restrict individual Coordinator abilities. Two-step verification is optional until each account holder completes enrollment. Text verification becomes available after the Twilio connection is configured; existing authentication remains active meanwhile. Authenticator secrets are encrypted with AES-256-GCM using a separately configured hosting secret; recovery codes are stored as hashes. Enabling or removing MFA revokes existing sessions and connection links. A password reset does not bypass MFA. Security changes and recovery use are recorded for accountability.
The hosting service provides the underlying storage and transport protections. The Hub is not end-to-end encrypted. Independent automated backups and a production restoration drill have not been verified. These controls reduce risk but cannot guarantee security.
Optional Passkeys
You can choose to enroll a passkey for hub.therealyb2016.com. The Hub stores its credential identifier, public key, your device label, verification counters, backup-state information, and creation and use times. The Hub never receives your biometric data, device PIN, or private passkey. Your chosen device or password-manager provider may synchronize passkeys under its own policies.
Enrollment requires your current Hub password and any existing verification protection. After enrollment, a password alone cannot sign in. An existing authenticator or text factor can remain a backup. Passkey recovery codes work once with your Hub password and are stored only as hashes. Password resets do not remove passkeys. Enrollment and management actions are recorded; successful changes revoke existing sessions and calendar or spreadsheet connection links.
A Secure, HttpOnly, same-site cookie binds each passkey sign-in request to the initiating browser for up to five minutes. Temporary verification challenges are excluded from recovery snapshots. Snapshots include public passkey records and recovery-code hashes; private keys stay with your device or passkey provider. Passkeys may be removed in account settings after verifying ownership and keeping an alternative sign-in method.
Your Choices And Rights
You may request access or a copy, correction, deletion, information about recipients, or an explanation of processing. You may also submit a privacy question, security concern, or appeal. Rights and exceptions depend on applicable law. We will verify identity where necessary and avoid disclosing other people’s information. There is no account-creation requirement and no retaliation for making a request.
Use Privacy Requests & Appeals. Save the private receipt link and return to it to read the response; the Hub does not automatically email replies. The initial response target is within 45 days. If a lawful extension is needed, the Administrator will explain it at that link before the initial period ends. An appeal uses the same form with Appeal selected and the prior request reference. If you disagree with an appeal outcome, you can contact the Minnesota Attorney General or your applicable privacy regulator.
Children And Policy Changes
The Hub is intended for adult committee participants and does not knowingly seek personal information from children under 13. Report a child’s information through the request form so the Administrator can address it. Material policy changes will be identified through an updated effective date and a Hub notice when appropriate. New uses requiring consent will be addressed before that processing begins.