Privacy Policy

1. Introduction

Neighborhood Technology Solutions LLC ("we," "us," or "our") respects your privacy and is committed to protecting the personal information of our users in Illinois and beyond. This Privacy Policy explains how we collect, use, and safeguard the information you provide through our various applications.

2. Information We Collect

Across our products, we collect information you provide directly and limited operational information needed to deliver, secure, bill, and support the features you choose to use. Through our feedback form, this includes:

• •Name (First and Last)
• •Date of Birth
• •Phone Number
• •Email
• •Feedback Content (The specific comments or issues you submit)

Information Collected by Town Square

Use of the Town Square App and its features is optional. You may browse public community content without creating an account; creating an account enables additional functionality such as posting, private messaging, neighborhood connections, and notifications.

• •Profile Information: Name, email address, date of birth, and optional profile photo provided during signup.
• •Neighborhood and Address: Neighborhood selection and address (if provided) to connect you with your local community. Location is not tracked automatically.
• •Community Posts and Media: Content you post in the community hub, including text, photos, and videos. Media is stored securely and associated with your user profile.
• •Private Messages: Direct messages between users are encrypted in transit and not proactively monitored. If a conversation is reported for abuse, moderators may access the relevant messages to investigate.
• •Notifications: Device notification tokens are collected to send you important app updates and community alerts. You can opt out of notifications at any time in your device settings.
• •Account Authentication: We use Firebase Authentication to securely manage your login credentials. We do not store your password.
• •Usage Data: We may collect limited technical information (such as device type and app version) to improve app performance and security. No third-party analytics or advertising trackers are used.

All information collected by the Town Square app is used solely to provide and improve community features, ensure user safety, and comply with legal requirements.

Information Collected by RoozCast

RoozCast is a voice-first personal productivity app that helps you capture daily check-ins, organize tasks, and optionally sync selected information with services you connect. RoozCast collects only the information needed to provide those features.

• •Account and profile information: RoozCast starts with a pseudonymous Firebase anonymous user ID, so a name or email address is not required to use native subscription features. If you later link Apple, Google, or another supported sign-in, we may receive your email address, display name, and provider identifier. We do not store your password.
• •Check-ins and personal content: RoozCast stores the typed or spoken check-ins you submit, including raw text, generated transcripts, AI-generated summaries, accomplishments, task suggestions, task status, categories, due dates, reminders, and related notes you choose to save.
• •Temporary audio files: If you record a voice check-in, RoozCast uploads the audio to Firebase Storage so it can be processed by the backend. Audio files are temporary and are deleted after processing where possible.
• •Schedules, reminders, and device tokens: We store your check-in schedule, notification preferences, timezone, and Expo push notification token so RoozCast can send reminders and notify you when check-ins or summaries are ready.
• •Optional integrations: If you connect Google Calendar or Google Tasks, Notion, or Fireflies, RoozCast stores the minimum integration metadata and OAuth/API credentials needed to sync data on your behalf. Integration secrets are stored separately from ordinary profile data and are not included in normal user data exports.
• •Subscriptions and purchase records: Apple App Store and Google Play process native subscription payments. RoozCast receives limited purchase, product, transaction, entitlement, and pseudonymous account-linking records needed to verify access, prevent fraud, restore purchases, and meet billing and legal obligations. We do not receive or store your full payment card or bank account number.
• •Third-party AI processing with your consent: Before RoozCast sends personal content to an external AI provider, it asks for explicit consent. Depending on the feature and available provider, selected check-ins, transcripts, prompts, task or planner context, and selected Google Calendar, Tasks, or Drive content may be sent to Google Gemini/Vertex AI, OpenAI, or Anthropic to provide transcription, summaries, search, briefings, and assistant features. You may decline or later revoke this consent in Settings; features that require external AI processing will then remain unavailable.
• •Shared-content safety: If you choose to share a planning space, RoozCast applies automated high-confidence filtering and provides controls to report objectionable content and block another user. A report may include the selected reason, optional details, a short content excerpt, hashed technical references, and moderation status. Safety reports are restricted to authorized review and retained for up to 180 days unless a longer legal or security hold is required.
• •Diagnostics and support information: We may collect crash reports, error logs, app version, and limited device information through tools such as Sentry to troubleshoot bugs and improve reliability. We avoid intentionally sending personal check-in content in crash reports.

RoozCast does not collect advertising identifiers, precise location data, or address-book contacts. Native stores handle payment credentials; RoozCast receives only the limited subscription and purchase records described above.

RoozCast privacy settings and visibility

RoozCast is designed for private daily reflection. Your check-ins, transcripts, summaries, tasks, and notes are private to your account by default and are not visible to other RoozCast users. RoozCast does not include a public feed or follower-based sharing for personal check-ins.

• •Limited internal access: We do not routinely read, monitor, or review your personal check-ins. Authorized personnel may access account data only when needed to provide support you request, investigate security or abuse reports, maintain the service, comply with legal obligations, or protect the rights and safety of users and the company.
• •Optional sharing through integrations: If you connect services such as Google Calendar, Google Tasks, Notion, or Fireflies, RoozCast syncs only the information needed for the features you choose to enable. Information sent to connected services is then handled under those services' privacy settings and policies.
• •User controls: You can manage notification preferences, disconnect optional integrations, revoke third-party AI consent, report shared content, block another sharing participant, export supported RoozCast data, and permanently delete either an anonymous or linked account from the app.

Independent Contractors

We offer an optional program for users to register as independent contractors. The following describes the data we collect and how it is used when you register to work through Town Square.

• •Eligibility: Individuals aged 16 and older may register as contractors. Users under 16 are not eligible. Contractors aged 16–17 must be linked to a parent or guardian account; the linked parent/guardian can view the contractor's accepted and active jobs.
• •Profile & equipment: Contractors provide profile information and select the equipment they use. Equipment selections are used to match appropriate jobs.
• •Identity verification: We verify contractor identity using Persona; we collect the identifying information necessary for that verification.
• •Background checks: Where required, we request background checks through Checkr and store results only as necessary to evaluate eligibility.
• •Banking & payouts: Contractors connect bank details via Stripe for payouts. Stripe handles payment processing and bank verification; we do not store full card or bank account numbers but may retain transaction identifiers and receipts.
• •Calendar integration: Contractors may connect Google Calendar so the app can match jobs to available times. Calendar access is optional and may be revoked at any time.
• •Availability & scheduling: Contractors control an availability toggle (on/off) and may set a buffer time between jobs. Jobs may be scheduled with as little as 30 minutes' notice and up to one day in advance, subject to contractor settings and job type.
• •Earnings & records: We retain earnings records, payout history, and job history to display to contractors and to support payments, disputes, and recordkeeping.
• •Retention & third parties: Contractor data retention follows Section 4 (Data Retention). We share contractor data with third‑party providers (Persona, Checkr, Stripe, Google) only as necessary to provide verification, background checks, payments, and calendar sync, in accordance with this policy.

Information Collected by CommonShelf

CommonShelf is an open shared inventory product. It is designed for collaborative location tracking and accountability in a shared environment, not for confidential or private recordkeeping.

• •Account and access information: CommonShelf may process Firebase anonymous authentication identifiers, an optional display name or other attribution text you choose to provide, and limited technical data such as browser, app version, and device information needed to operate, secure, and troubleshoot the service.
• •Location and inventory records: We process location names, categories, items, quantities, notes, stock and restock fields, deleted-item records, and related inventory history that users create or update in CommonShelf.
• •Notifications and communication: If you enable CommonShelf notifications, we process notification preferences, verified notification email addresses, push-device tokens, verification status, and delivery records needed to send alerts and digests.
• •Operational and administrative records: CommonShelf may process on-behalf attribution, support-workflow records, deletion-review records, name or attribution moderation decisions, and other service-integrity records needed to operate shared inventory responsibly.
• •Visibility model: Because CommonShelf is an open shared product, information you place in CommonShelf may be visible to other CommonShelf users who participate in the shared system and should not be treated as private or confidential.

We use CommonShelf data to run shared inventory tracking, notification delivery, support workflows, deletion review, naming-rule enforcement, and service integrity in an open shared environment where users should avoid storing confidential or private records.

Information Collected by SecureShelf

SecureShelf is a paid private inventory product designed for role-based location access, accountable updates, and export-friendly continuity.

• •Account and access information: We process account identifiers such as your user ID, email address, display name, sign-in provider, and related authentication metadata from email-link, Google, Apple, or other enabled sign-in methods. We do not store your password.
• •Location and inventory records: We process secure location names, categories, items, quantities, notes, stock tracking, restock-related fields, and transaction history associated with a secure location.
• •Notifications and communication: If enabled, SecureShelf processes verified notification email addresses, push-device registrations, notification preferences, and notification delivery history needed to support member notifications.
• •Operational and administrative records: SecureShelf processes member roles, invites, immutable audit events, deletion requests, export metadata, support-view records, customer IDs, subscription IDs, billing state, invoice or payment-status metadata, and related accountability records needed to operate paid secure locations. We do not store full payment card numbers.
• •Visibility model: SecureShelf is designed so supported secure-location content is available only to authorized members of that location and authorized administrators who access data for support, security, billing, or legal reasons.

We use SecureShelf data to operate private role-based inventory, audit and accountability records, notifications, billing, exports, and authorized support or administrative workflows for secure locations.

Information Collected by MyCircles: Concentric Circles

MyCircles is local-first by default. You can create and manage projects on your device without an account. If you create an account or choose features such as cloud projects, snapshot sharing, Live Share, AI Ask, billing, or map tools, we process the information needed to provide those features.

• •Account and sign-in information: If you create an account, we use Supabase Authentication and may process your email address, account ID, sign-in provider, and authentication metadata for email magic link, Google, or Apple sign-in. We do not store your password.
• •Profile information: You may provide a display name and optional avatar or profile image. Profile images may be stored in account metadata or product storage so your account can be personalized across signed-in sessions.
• •Project content: MyCircles projects may include people, names, bios, notes, custom attributes, relationships, connection labels, rings, positions, colors, narratives, view settings, color labels, local activity history, imports, exports, snapshots, and related metadata you choose to create or save.
• •Cloud projects, snapshots, and Live Share: If you use cloud projects, snapshot sharing, or Live Share, we store the project data and share metadata needed to create links, restrict access to invited email addresses where configured, maintain share slugs and signatures, sync collaborators, and show presence or activity in real time.
• •AI Ask and semantic search: If you use AI Ask, we process your project query, bounded project context, person summaries, relationship context, embeddings, usage counts, hashed IP/request metadata for rate limiting and abuse prevention, and AI response metadata. AI processing may use Google Gemini/Vertex AI, OpenAI, or Anthropic through our Supabase Edge Functions; embeddings currently use Google Gemini.
• •Map and geocoding features: If you use map tools, address search, or address-to-coordinate features, we may send the address text or search input needed for autocomplete or geocoding to Google Maps Platform through our backend. Map displays may also load OpenStreetMap tile data. We use this only to provide the requested map feature.
• •Subscription and billing metadata: If you subscribe or request account changes, we may process plan, tier, product key, provider, status, purchase identifiers, subscription identifiers, customer identifiers, billing event metadata, and support notes from Apple App Store, Google Play, Stripe, or manual support workflows. We do not store full payment card numbers.

Information Collected by Unveiled: Commit to Heart

Use of Unveiled: Commit to Heart is optional. You may use the app without linking an account; linking an account enables project synchronization across devices and other personalized features.

• •Account linking (optional): If you choose to link or create an account to enable synchronization, we collect your name, email address, and account identifiers required to sync projects across your devices.
• •Project data: Projects you sync are stored to provide cross-device synchronization and access.
• •Purchases & payment information (optional): Unveiled offers an in-app purchase for full access. Payments are processed by the app store or third‑party payment providers; we do not collect or store full payment card numbers. We may retain transaction identifiers, purchase receipts, and billing contact information necessary to provide the service and for recordkeeping.
• •Retention: Retention of synced data follows Section 4 (Data Retention). Any differences in retention for paid subscriptions are described above.

Information Collected by Monet or Manet

Use of the Monet or Manet app is optional. The app is designed as an interactive art gallery and game. We collect limited information to provide features like score tracking and gallery progress.

• •Game Progress & Leaderboard Submissions: We collect and store data related to your game performance, including correctly identified paintings, streaks, and total scores. If you submit your score to the global leaderboard, your player name and performance metrics are stored securely and displayed to other users.
• •Local Storage: We use local storage (Shared Preferences) to save your preferences and progress on your device.
• •Cloud Synchronization: If cloud features are enabled (such as global leaderboards), your progress and scores are synced to our secure database (Cloud Firestore). We do not currently require an account to use these features.
• •Usage Data: We may collect limited technical information (device type and app version) to ensure compatibility across different mobile devices.
• •Advertising (Google Mobile Ads): The app serves banner advertisements through Google AdMob. Google may collect advertising identifiers (IDFA on iOS, Google Advertising ID on Android), device information, and app usage data to serve relevant ads. On iOS, the app requests permission through Apple's App Tracking Transparency (ATT) framework before accessing your advertising identifier. If you decline, ads will still be shown but will not be personalized. You may review and update your ad preferences at any time through your device settings. For more information, see Google's Privacy Policy.
• •In-App Purchases: The app offers a one-time in-app purchase to remove advertisements. All payment transactions are processed exclusively by the Apple App Store (iOS) or Google Play Store (Android). We do not collect, store, or have access to your payment card information or billing details. Please review the applicable store's privacy policy for information on how your payment data is handled.
• •Children's Privacy (COPPA): The app is available to users aged 13 and older. For users under 13, advertising may be limited or restricted in accordance with the Children's Online Privacy Protection Act (COPPA) and applicable platform policies. We do not knowingly collect personal information from children under 13 for advertising purposes.

Information Collected by Inkify

Information We Collect from Form Owners and Admins

During installation and configuration of the Inkify Add-on, we process limited admin and operational information required to manage licensing, provide support, and run the features a form owner chooses to enable. This may include:

• •Admin Email Address: Used to verify license status, manage subscriptions, send operational notices, and provide support.
• •License, Voucher, Subscription, Team Seat, and Billing Metadata: Used for activation, tier checks, Enterprise access, organization-owned transferable seats, signer-profile subscriptions, payment-collection readiness, billing support, fraud prevention, and abuse prevention.
• •Organization Seat Metadata: For Inkify Team Seats, the website and Inkify Hub may store the team or organization name, owner email, seat admin emails, assigned seat emails, seat tier and status, requested and approved domains, Stripe customer, checkout, subscription, and webhook identifiers, auth/session records, audit events, and finalized-submission usage counters by organization, user, and day.
• •Inkify Help Metadata: If you use Inkify Help on the setup guide, we may process your signed-in email, helper auth/session records, rate-limit hashes, aggregate daily usage counts, approved knowledge source references, and the question you submit for AI processing. If you opt in to Setup Coach, we may store hashed-email setup progress metadata such as setup step, safe counts, booleans, status categories, an opaque setup session, and sync state for up to 90 days after last activity. Inkify Help does not store chat transcripts by default.
• •Configuration Metadata: Settings such as form IDs and titles, published form URLs, hidden payload configuration, branding preferences, delivery settings, workflow mode, counts, timestamps, redacted operational status, and customer-selected storage/template labels where needed for display. Inkify Hub configuration metadata must not include customer Drive file IDs, storage references, template contents, signed PDFs, response Sheet rows, signatures, private keys, or customer file contents.

Information Processed for Form Respondents and Signees

Inkify helps form owners collect information from individuals who respond to connected Google Forms. Depending on the form and enabled features, this may include:

• •Form Answers and Signatures: Used by the form owner's Google Workspace add-on to generate signed records, populate templates, and create signed PDFs in the form owner's Google Drive.
• •Signer Identity and Evidence: Signer names and emails when collected by the form, consent version/hash, consent timestamp, IP address where available, user agent, transaction ID, signed-record hash, PDF hash, and audit metadata.
• •Signed-Copy Delivery Data: The email address a signer provides for a signed copy is included in the native Google Form submission so the form owner's add-on can send the signed copy from the form owner's Google context.

Customer-Owned, Zero-Knowledge Custody Boundary

Customer-Controlled Workspace: Generated signed PDFs, signatures, form answers, response rows, templates, Drive files, private signing keys, signed-copy email content, and customer-owned workflow records are processed in the form owner-authorized Google Workspace and add-on context. Zero-knowledge custody means naborlydone-controlled hub and short-link systems are designed not to retain customer-owned signing records, including submissions, signatures, signed PDFs, response Sheets, templates, private keys, signed-copy email content, member sheets, or private workflow state.

Inkify Hub Processing: The Inkify Hub may retain admin/license/support metadata, organization seat metadata, form configuration metadata, safe form registry records, redacted workflow projections, finalized-submission usage counts, timestamps, policy modes, and similar service metadata needed to render and coordinate the service. It may also store encrypted signer-owned profile values when a signer chooses to create a saved profile.

Payment Metadata: When enabled, form-owner license billing, organization Team Seat billing, signer saved-profile billing, Stripe Connect readiness, and redacted in-form payment attempts may be stored as operational payment metadata. Inkify payment metadata must not include customer form answers, signatures, PDFs, Drive files, signed-copy email content, or private workflow records.

Branded Short Links: Short links at forms.naborlydone.com store only non-PII routing metadata: slug, link kind, opaque form/event/workflow/invite handles, click count, and last-used timestamp. They must not store full destination URLs, owner or signer emails, prefill payloads, decoded signer tokens, answers, signatures, signed PDF links, member profiles, or signer rosters. No third-party advertising or marketing trackers are used for Inkify.

PDF Verification Tool: The Inkify verification page is designed to inspect signed PDFs locally in your browser. The PDF file, extracted text, embedded evidence block, verification result, and cryptographic checks are not uploaded to naborlydone unless you separately choose to share that information with us for support.

Signer-Owned Saved Profiles

Signers may choose to create an optional Inkify saved profile so matching fields can be prefilled on future Inkify forms. A profile is owned by the signer, not by the form owner. Creating a profile is not required to submit a form.

• •Profile Login: Inkify uses email-code login for signer profiles. Profile login codes are sent only for authentication and do not include form answers, signatures, PDFs, or signed-copy email content.
• •Profile Values: Saved profile details are encrypted in Inkify-controlled profile storage and used only for signer-approved prefill and profile management. Profile values are not sold, used for advertising, or shared with form owners as a member database.
• •Review Before Save: After submitting a form, signed-in users may be asked whether reviewed answers should be saved to their profile. Suggested updates start unselected and are saved only after the signer chooses them.
• •Delete Profile: When a signed-in user deletes their profile, Inkify hard-deletes the encrypted profile row plus related profile authentication, session, and consent rows from the profile database. Deleting a profile does not delete forms, PDFs, emails, or records already submitted to a form owner.
• •Profile Billing: Saved profiles are a separate signee-paid feature priced at $2/month or $20/year per profile, before any payment processor or checkout fees shown before purchase. Billing metadata is handled only as needed to operate the profile subscription and does not include form answers, signatures, PDFs, or customer-owned signing records.

License Usage and Subscriptions

Inkify owner licenses and Enterprise subscriptions are intended for the single authorized Google Account that activates or subscribes to the service unless the customer has officially purchased organization-owned transferable seats. Official organization seats may be assigned, revoked, and reassigned by authorized organization admins through the Inkify organization hub; those records are limited to operational license metadata and do not include customer-owned signing records.

Organization-owned Team Seats support exact-email assignment so a seat can be moved when an employee or contractor changes roles. Exact-email assignment works immediately after a seat is available. Domain controls may be requested by an organization owner, but requested domains are not treated as verified or approved until naborlydone staff approves them. Removing or changing a domain does not by itself delete existing customer-owned Google Workspace records.

Team Seat entitlement checks and finalized-submission usage increments are metadata-only. We may receive the assigned user's email, organization and seat identifiers, tier, status, and a metadata-only idempotency key for counting finalized Inkify-hosted submissions. We do not receive form answers, signatures, PDFs, response Sheet rows, Drive file contents, templates, private signing keys, member profiles, signer workflow state, or raw form content for Team Seat license validation or usage counting.

We may monitor operational license metadata for billing support, fraud prevention, abuse prevention, and enforcement of authorized seat boundaries. Credential sharing, informal pooling, resale, or using one paid account as a shared administrative account outside an official organization seat is not permitted.

Inkify Help AI Assistant

Inkify Help is an optional setup-guide assistant for recognized Free Trial/free-tier, personal paid, personal Enterprise, and organization seat users. It answers from approved product, setup, privacy, terms, and public-support-safe Inkify knowledge and may show illustrative sidebar or form guidance from an allowlisted map.

Inkify Help uses Google Gemini/Vertex AI for AI processing when enabled. We send the question you type and approved knowledge context to the AI provider so it can answer. We do not send or ingest customer-owned form answers, signatures, PDFs, response Sheet rows, Drive file contents, templates, private signing keys, member profiles, signer workflow state, or raw form content.

Inkify Help does not store chat transcripts by default. We store only metadata needed for sign-in, rate limiting, aggregate usage, model-error counting, optional Setup Coach progress, and security. Setup Coach and automatic setup sync are opt-in; synced setup data is limited to counts, booleans, and categories, expires after 90 days of inactivity, and can be cleared by the user. If Inkify Help drafts a support ticket, the draft is not submitted automatically; you must review it and choose to submit it through the support form.

Technical Trust: Authorized Scopes

To maintain a secure and functional integration, Inkify operates within your Google Workspace using specific, authorized permissions. Each "scope" serves a direct functional purpose:

• •drive.file: Creates, opens, copies, and stores files the Admin selects or the app creates, including signed PDFs, preview PDFs, managed templates, and compliance exports.
• •documents: Merges form answers into Admin-selected Google Docs templates and converts the resulting record to PDF.
• •spreadsheets: Reads and writes configured response, audit, member, event, voucher, and workflow sheets in the Admin's Google Workspace.
• •forms.currentonly: Inspects and configures only the active Google Form where the add-on is installed.
• •script.external_request: Calls the Master Hub, short-link service, IP evidence service, and configured add-on relay endpoints needed for visible product features.
• •script.send_mail: Sends signer invites, reminders, signed copies, and owner notices for workflows the Admin configures.
• •script.container.ui & script.scriptapp: Displays the add-on sidebar and installs/manages submission or maintenance triggers required for the configured workflow.
• •userinfo.email: Identifies the active Admin for license checks, owner-only controls, audit/export access, and support.

User Control and Access Revocation

You can revoke Inkify's access to your Google account at any time by visiting myaccount.google.com/permissions.

All information collected and processed by Inkify is used solely to provide and improve the application's features, ensure user safety, and comply with legal requirements.

3. How We Use Your Information

In compliance with Illinois law, we only use your data for the purposes disclosed at the time of collection:

• •To Respond to Feedback: We use your name and phone number to contact you regarding the specific feedback or support request you submitted.
• •To Provide RoozCast: We use RoozCast data to authenticate your account, verify subscription access, organize transcripts into summaries and tasks, maintain categories and schedules, send reminders, and support export or account deletion requests. Only after explicit consent, selected content may be processed by Google Gemini/Vertex AI, OpenAI, or Anthropic for the external-AI features you request.
• •To Sync Connected Services: When you connect Google Calendar or Google Tasks, Notion, or Fireflies, we use your authorization only to read, create, or sync the information needed for the features you choose to enable.
• •To Provide CommonShelf: We use CommonShelf data to maintain shared inventory locations, process inventory and history changes, support notification delivery and verification, and handle support or deletion-review workflows.
• •To Provide SecureShelf: We use SecureShelf data to authenticate members, enforce roles and billing state, process server-mediated inventory and membership changes, generate audit records, deliver notifications, provide export and continuity features, and support billing or administrative workflows.
• •To Provide MyCircles: We use MyCircles data to save local and cloud projects, authenticate signed-in accounts, generate share links and Live Share sessions, sync invited collaborators, process AI Ask queries, provide map/geocoding tools, manage subscriptions, enforce plan limits and abuse/rate limits, support exports/imports, and handle account deletion requests.
• •To Support Billing and Continuity: Where a product includes paid plans or export tooling, we use limited customer, subscription, audit, and export metadata to operate billing flows, prevent abuse, preserve accountability, and help users retrieve supported data.
• •To Provide Inkify: We use Inkify admin, license, organization seat, configuration, profile, and support metadata to render signing pages, verify access, operate optional saved profiles, send profile login codes, support PDF verification, and coordinate customer-owned Google Workspace processing.
• •Service Improvements: We analyze feedback data to improve our app's performance and user experience.
• •Consent-Based Communication: We will not use your phone number for marketing or automated messages unless you have provided separate, explicit consent.

4. Data Retention and Disposal (Illinois PIPA Compliance)

Under the Illinois Personal Information Protection Act (815 ILCS 530/), we are required to safely dispose of data that is no longer needed.

• •Retention: We retain your contact information only for as long as necessary to resolve your inquiry or for a maximum of 90 days following your last interaction with us.
• •RoozCast Retention: RoozCast check-ins, summaries, tasks, categories, schedules, and profile settings are retained until you delete them or delete your account. Temporary audio uploads are deleted after processing where possible. Crash and diagnostic records are retained only as long as needed for troubleshooting and service integrity. Shared-content safety reports are retained for up to 180 days unless a legal or security hold requires longer retention. Purchase, transaction, entitlement, tax, fraud-prevention, refund, dispute, and audit records may be retained after account deletion for the period required by law and provider, security, and accounting obligations.
• •Account Deletion: RoozCast includes an in-app deletion flow for both anonymous and linked accounts. It removes the authenticated user's ordinary product data, stored check-in audio files, third-party AI consent record, and Firebase Authentication account. It redacts the user's identity from retained shared-content safety reports. Limited billing, fraud-prevention, security, legal-hold, and audit records may remain as described above. This action is intended to be permanent and does not cancel a store subscription.
• •CommonShelf Retention: CommonShelf location names, inventory data, history, notification preferences, delivery records, and deleted-item records are retained until they are edited, removed, or no longer needed to operate the service, support users, investigate abuse, or maintain service integrity.
• •SecureShelf Retention: SecureShelf secure-location content, membership records, audit events, deletion requests, billing metadata, support records, notification history, and export metadata are retained as needed to operate paid locations, support continuity and exports, prevent fraud or abuse, resolve disputes, and comply with legal obligations. Generated export files may expire from storage after their availability window closes even though related audit or billing records may remain longer.
• •MyCircles Retention: Local project data remains on your device until you delete it or uninstall/reset the app. Cloud projects, live-share projects, snapshots, account metadata, AI metadata, and billing records are retained as needed to provide the service, enforce plan limits, support billing/security, or comply with legal obligations. Non-live shared snapshots may expire based on plan limits; live-share projects may remain available until disabled, deleted, or the account is deleted.
• •Inkify Profile Deletion: Inkify saved profiles are retained until the signer deletes the profile or the account is otherwise closed under the applicable product rules. Profile deletion hard-deletes the encrypted profile row and related profile authentication, session, and consent rows, but does not delete records already submitted to a form owner.
• •Secure Disposal: When your information is no longer required, we use industry-standard methods to delete electronic records, ensuring they are rendered unreadable and unrecoverable.

5. Third-Party Sharing

Data is a responsibility, not an asset.

We do not sell, rent, or lease our user lists to third parties. Because we are self-funded and owner-operated, your data is not—and will never be—treated as a financial asset to be sold, licensed, or leveraged to increase company valuation. We only share information with trusted service providers (who must comply with our strict privacy standards) to the extent necessary to provide our services.

Across all of our products, we do not sell personal data and we do not share personal data with third parties for their own marketing purposes.

CommonShelf uses third-party providers only to operate selected features: Firebase and Google Cloud for anonymous authentication, Realtime Database, functions, infrastructure, and push messaging; Zoho ZeptoMail for notification email delivery and verification; and browser or device notification services when you enable push notifications.

SecureShelf uses third-party providers only to operate selected features: Firebase and Google Cloud for authentication, Cloud Firestore, storage, functions, infrastructure, and push messaging; Stripe or another disclosed processor for checkout, subscriptions, invoices, and billing-portal flows; Zoho ZeptoMail for verification and notification email delivery; and browser or device notification services when you enable push notifications.

RoozCast uses third-party providers only to operate selected features: Firebase and Google Cloud for authentication, database, storage, functions, and infrastructure; Google Gemini/Vertex AI, OpenAI, and Anthropic for external AI processing after explicit user consent; Apple App Store and Google Play for native subscription billing; Google Calendar, Google Tasks, and Google Drive for optional user-authorized features; Notion for optional workspace sync; Fireflies for optional meeting context; Sentry for crash reporting; and Expo for push notifications. The website may also use Loops to process mailing-list email subscriptions.

MyCircles uses third-party providers only to operate selected features: Supabase for authentication, database, realtime collaboration, storage, and Edge Functions; Google Sign-In and Apple Sign-In for optional account login; Google Gemini/Vertex AI, OpenAI, and Anthropic for AI Ask, semantic processing, and AI response generation where configured; Google Maps Platform for optional autocomplete and geocoding; OpenStreetMap for map tile display; Apple App Store, Google Play, Stripe, or another disclosed processor for subscription billing; and device/platform services for sharing, file import/export, camera/photo selection, QR scanning, and deep links.

Inkify uses third-party providers only to operate selected features: Google Workspace for form-owner processing, Cloudflare for Hub, routing, organization seat management, Inkify Help metadata, and encrypted profile storage, Zoho ZeptoMail for profile login-code and helper sign-in email delivery, Stripe or another disclosed payment processor for license, Team Seat, and saved-profile billing, and Google Gemini/Vertex AI for Inkify Help and limited signer-reviewed suggestions where enabled. Inkify does not use third-party advertising trackers for signer forms or saved profiles.

6. Security Measures

We implement "reasonable security measures" as required by Illinois law to protect your data. This includes:

• •Encryption: Using SSL/TLS encryption for data transmitted through our forms.
• •Cloud Security: CommonShelf, SecureShelf, and RoozCast data use Firebase and Google Cloud services with encryption in transit and at rest. Product access boundaries may differ by product design, account model, and feature set.
• •Product-Specific Access Models: CommonShelf is intentionally open and shared, so it should not be used for confidential, regulated, or secret inventory records. SecureShelf is designed with authenticated accounts, role-based access, server-side authorization checks, audit logging for important actions, and private storage or access controls for supported secure-location workflows.
• •Integration Secret Handling: OAuth tokens, API keys, webhook secrets, and similar privileged credentials are stored separately from ordinary user content and redacted from standard export data where possible.
• •Access Control: Restricting access to personal data to only those employees or contractors who need it to fulfill their duties.

7. Children's Privacy (COPPA)

Our services are not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If we discover such data has been collected, we will delete it immediately.

8. Data Breach Notification

In the event of a security breach involving your personal information, we will notify you in the most expedient time possible and without unreasonable delay, as required by Illinois PIPA (815 ILCS 530/10).

9. Your Rights and Contact Information

You have the right to request access to the information we have collected about you or to request its deletion. Please contact us at:

RoozCast users can also use the in-app Export My Data feature to receive a JSON copy of supported account data, and the in-app Delete Account feature to permanently remove either an anonymous or linked RoozCast account and ordinary stored data. Deletion does not cancel an Apple App Store or Google Play subscription; users manage cancellation through the applicable store.

CommonShelf users may contact us regarding shared-location data questions, notification subscriptions, or support-driven location deletion requests. Because CommonShelf is an open shared product, information other users have already viewed, copied, exported, or recorded may remain outside our control even after data is removed from our systems.

SecureShelf may provide export, billing, and support tools to authorized owners or administrators for supported secure-location data. Members may also contact us regarding access, export, or deletion questions, but some records may be retained for audit, billing, security, fraud-prevention, continuity, or legal reasons even after membership ends or content is removed from active views.

MyCircles users can use available in-app export tools to create supported project archives, and signed-in users can request account deletion from the app. Account deletion removes cloud data controlled by us where possible, but does not remove local device data, exported files, copied collaborator data, provider billing records, or records we must retain for legal, security, fraud-prevention, or billing reasons.

Neighborhood Technology Solutions LLC
1847 W Morse Ave. Chicago, IL 60626
Email: support@naborlydone.com
Phone: (773) 942-0995