Last updated: October 20, 2026
Version 2026-10-20
Plain-language summary: We collect the information needed to run a marketplace for outdoor tasks and online tutoring — names, dates of birth, emails, listings, messages, and limited location data during active jobs. A teen can't post a service or take a job until a parent links to their account, and parents complete Stripe's payout setup (legal name, date of birth, SSN, bank account, 18+) before any earnings are paid out. We do not store SSNs or ID images. We hold payments through Stripe until the job is done. We do not sell your data. This policy explains what we collect, why, and your rights.
Where we operate. Blockwork is available only in the states where we have opened. The current list is always published at blockwork.online/states. This policy applies to everyone who uses Blockwork in those states, and it applies to you whether or not your state has extra privacy laws of its own.
Account data: Name, email, date of birth, and role (teen, parent, or neighbor). Used to create and manage your account and confirm age eligibility.
Profile data: Display name (first name + last initial for teens), bio, photo, skills, and service area. Used to show your profile to other users.
Teen private data: Date of birth, age, ZIP code, and approximate location. Exact coordinates are used only server-side for distance matching and are never shown to other users.
Payout account data: Parents set up a payout account through Stripe's payout account setup (Connect Express onboarding). Stripe collects the parent's legal name, date of birth, SSN, and bank account under Stripe's own privacy policy. Blockwork does not store SSNs, ID images, or selfie data. We store only the Connect account status and masked bank references (last 4 digits).
Listing and job data: Job titles, descriptions, categories, prices, and photos. Used to display and match jobs. For outdoor jobs, the address is revealed to the teen and parent only after a booking is confirmed.
Messages: The content of in-app messages between users. Every message is screened automatically before it is delivered. We apply our own safety rules, and we send message text to OpenAI's moderation service (omni-moderation-latest) to detect sexual content, harassment, hate, violence, and self-harm; messages that look borderline are also reviewed by a language model to classify grooming, off-platform contact, scams and harassment. Messages that break our rules are held for review or blocked, contact details are hidden, and the teen's parent is alerted. Flagged messages, the outcome, and our safety team's decision are retained for safety and audit purposes. A teen who discloses self-harm is shown crisis resources (call or text 988) and we alert our safety team — that is not treated as a rule violation.
Location data: For in-person jobs we save the teen's location three times at most: when they tap "I'm here" at check-in, when they tap "Done, heading home" at check-out, and if they press the SOS button. We never track location continuously. Each saved location is visible only to the teen's parent and Blockwork's safety team — never to the neighbor — and is deleted 90 days after the job. Online jobs do not use location; joining the video room counts as checking in.
Job photos: The teen can add an optional "before" photo at check-in and must add at least one "after" photo to finish an in-person job. Both are shown to the neighbor, the parent, and our safety team, and are attached automatically to any dispute. Photos are re-encoded on the device before upload, which strips location and other camera metadata (EXIF).
Online session data: When a booking is for online tutoring or tech help, the platform generates a video session link. We log session metadata (start time, duration, participant IDs, and the session link) for safety, dispute resolution, and record-keeping. We do not record, store, or transcribe the audio or video of any session.
Completion photos: When a teen marks an outdoor job as finished, they upload photos showing the completed work. These are shown to the neighbor for confirmation and to administrators during dispute review. They are stored for the life of the booking and any related dispute, then deleted per our retention policy.
Payment data: We do not store your card or bank details. Payment processing is handled by Stripe. We store transaction records, payment status, and masked bank references (last 4 digits) returned by Stripe.
Consent records: When a parent links to a teen, we record each itemized consent acknowledgment with a timestamp, the terms version, the parent's IP address, and user agent. This creates an auditable consent trail.
Device and usage data: IP address, browser type, and basic analytics. Used for security, fraud prevention, and improving the platform.
We process your data to: provide the service you requested (contract), comply with legal obligations including child safety and tax laws (legal obligation), protect the safety of minors and prevent fraud (legitimate interest), and with your consent where required (consent).
Parental consent. We do not knowingly collect personal information from children under 13. For teens aged 13–17, we require verifiable parental consent before the account becomes active. A parent or guardian must link to the teen's account, complete Stripe payout setup (which verifies they are a real adult 18+), and individually acknowledge each itemized consent described in the Terms of Service.
What parents can see. A linked parent can view the teen's profile, bookings, messages (read-only), earnings, online session links, and live location during active outdoor jobs. Parents can request deletion of a teen's data at any time.
Minimization. We expose only the minimum information needed to run the platform. Teens are shown to neighbors by first name and last initial, approximate city, and service area — never exact address. Exact addresses are revealed to the teen and parent only after a booking is confirmed. Online session links are visible only to the teen, the neighbor, and the teen's parent.
All payment information is processed by Stripe. We never see or store your full card number or bank account details. We receive only transaction results, masked references, and payout status from Stripe. See Stripe's privacy policy for how they handle payment data.
For online tutoring and tech-help bookings, we generate a video session link and make it visible to the teen, the neighbor, and the teen's parent. We log session metadata (start time, duration, and participant IDs) but do not record, store, or transcribe the audio or video. Parents can see scheduled session times and the session link so they can monitor their teen's online activity. If a participant reports inappropriate conduct during a session, we may use the session metadata in our investigation.
We share data with:
We do not sell your personal data. We share data with authorities only when required by law or to protect the safety of a minor.
We use essential cookies to keep you logged in and remember your preferences. We may use analytics cookies to understand how the platform is used. We do not use cookies for targeted advertising.
We use a small number of cookies.
We never use cookies for advertising, and we never sell or share data collected by cookies. We honor Global Privacy Control signals. You can change your choice any time with the button below or from Account settings.
We keep your data for as long as your account is active. After account closure, we retain transaction, verification, and consent records for as long as required by law (typically 3–7 years for tax and safety purposes), then delete or anonymize them. Messages are deleted when the account is closed. Completion photos are retained for the life of the booking and any related dispute, then deleted.
We take reasonable, industry-standard measures to protect your data — especially data belonging to minors. No system is perfectly secure and no measure is absolute, but the measures below are genuinely implemented and actively maintained.
In transit. All data sent between your device and Blockwork is encrypted using HTTPS/TLS. The platform enforces TLS on every request; there is no unencrypted (HTTP) path to application data. Our Content-Security-Policy blocks mixed-content loading so page resources are never fetched over an insecure connection.
At rest. The database that stores your account, profile, booking, and message data is encrypted at rest by our hosting provider (Base44, backed by MongoDB Atlas), which manages transparent encryption of all stored data.
Application-level field encryption. A field-encryption module (AES-GCM, key stored in a server-side environment variable, never in code) is available to encrypt the most sensitive fields — dates of birth, addresses, and identity-verification references — so they remain unreadable even with raw database access. Numeric location coordinates cannot be encrypted at the application level without breaking the distance-matching math that depends on them; those fields rely on the database's at-rest encryption plus row-level access controls. Full field-level encryption rollout to existing data is in progress and requires a coordinated migration of every read path.
Card and bank details are never seen or stored by Blockwork. All card data flows through Stripe's PCI-DSS Level 1 infrastructure. Our servers receive only a Stripe token or PaymentIntent ID — never raw card numbers, CVCs, or bank routing numbers. Bank details entered during Connect onboarding go directly to Stripe's hosted form, never through our backend. We store only masked references returned by Stripe (e.g., last four digits of a bank account).
No ID images or selfies are stored. Parents set up a payout account through Stripe's payout account setup (Connect Express onboarding). Stripe collects the parent's legal name, date of birth, SSN, and bank account under Stripe's own privacy policy. Blockwork does not store SSNs, ID images, or selfie data — only the Connect account status and masked bank references returned by Stripe.
Data access is restricted per user by role, enforced on the server — not just in the UI. Every backend function verifies your identity and ownership before returning or modifying data. You can only ever see your own data and what your role permits:
No endpoint returns another user's data by changing an ID in a request — ownership is validated server-side on every call. Role checks (e.g., "admin only") are enforced in the backend, not just hidden in the interface. All money operations — prices, fees, payouts, refunds — are computed server-side; the client never sends an amount that is trusted.
We minimize public exposure of teen data. Teens are shown to neighbors by first name and last initial only — never full name, exact address, or contact details. Exact job-site addresses are hidden until a booking is confirmed, then revealed only to the teen and their parent. Contact information in pre-booking messages is automatically masked (phone numbers, emails, and addresses are redacted server-side). Parents have visibility into their teen's bookings, earnings, online session links, and live location during active outdoor jobs.
Sensitive endpoints are rate-limited per IP address and per user account, with exponential backoff between attempts. The invite-code lookup (used to link a parent to a teen) is the most aggressively protected: after repeated failed attempts, the code is locked and the teen, their parent, and admins are alerted. Payment initiation, payout requests, and wallet cash-outs are also rate-limited to prevent rapid-fire probing. Login, registration, password reset, and OTP verification are rate-limited by our hosting platform's authentication infrastructure.
Security events are logged and monitored, including: failed invite-code attempts, locked invite codes, Stripe webhook signature verification failures, permission-denied errors, and critical payout blocks. Repeated failures from a single IP or account trigger automatic admin alerts. An immutable audit log records sensitive actions — payouts, booking approvals and denials, cash-out requests, and critical security events — with the actor, action, target, and timestamp. Audit log entries are admin-readable and are not modified after creation.
We keep your data only as long as needed. Account data is retained while your account is active. After account closure, transaction, verification, and consent records are retained for as long as required by law (typically 3–7 years for tax and safety purposes), then deleted or anonymized. Messages are deleted when the account is closed. Completion photos are retained for the life of the booking and any related dispute, then deleted. Audit log entries are retained for the legally required period for financial and safety records.
No system is perfectly secure. Blockwork takes reasonable and industry-standard measures to protect your data, and no measure is absolute, so we can't promise that ours will never be circumvented. Security headers such as HSTS, X-Frame-Options, and X-Content-Type-Options are set at the hosting-platform level and may vary depending on platform configuration. If you believe you have found a security vulnerability, please report it responsibly to support@blockwork.online and we will investigate promptly.
You (and, for teen accounts, your parent or guardian) have the right to:
Parents can exercise these rights on behalf of their linked teen. To make a request, use the in-app account deletion option or contact us at support@blockwork.online.
We do not knowingly collect personal information from children under 13. If you believe a child under 13 has registered, contact us and we will promptly delete the account and associated data. For teens 13–17, we obtain verifiable parental consent through Stripe payout setup (which verifies the parent is a real adult 18+) and itemized acknowledgment before activating the account, as described above and in the Terms of Service.
California (CCPA/CPRA). California residents have the right to know what personal data is collected, request deletion, correct inaccurate data, opt out of the sale or sharing of personal data, and not be discriminated against for exercising these rights. We do not sell or share personal data as defined by California law. To exercise your rights, contact us at the email below.
Other states. Whatever state you live in, you can ask us what personal data we hold about you, ask us to correct it, and ask us to delete it. Contact us at the email below and we'll action your request.
These rights are consistent with the rights described in Section 10 and do not limit any other rights you may have under applicable law.
We may update this policy from time to time. We will notify users of material changes through the app or by email. Continued use after changes take effect means you accept the updated policy.
Questions or privacy requests? Contact us at support@blockwork.online.