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
We only collect information that you voluntarily provide to us. Through our feedback form, this includes:
- • Name (First and Last)
- • Date of Birth
- • Phone Number
- • 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. We do not sell or share your personal data for marketing purposes.
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: We use Firebase Authentication to manage sign-in and collect account identifiers such as your user ID, email address, display name, and authentication provider details. 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.
- • 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, contacts, or financial information based on the app's current functionality. We do not sell RoozCast personal data.
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, export supported RoozCast data, and request account deletion from the app where those controls are available.
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 MyCircles: Concentric Circles
Use of the MyCircles: Concentric Circles App is optional. You may use MyCircles: Concentric Circles without creating an account; creating an account enables additional features such as saving and sharing projects.
- • Account information (if you create an account): We collect your name and email address. Account creation is optional and these details are only collected when you choose to provide them.
- • Profile picture (optional): You may choose to upload a profile picture to personalize your account.
- • Live sharing & retention: MyCircles: Concentric Circles allows users to live-share projects. For paying subscribers, shared projects are retained indefinitely. For non-paying users, shared snapshots are retained for up to 90 days, consistent with Section 4 (Data Retention).
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, and Billing Metadata: Used for activation, tier checks, Enterprise access, signer-profile subscriptions, payment-collection readiness, billing support, fraud prevention, and abuse prevention.
- •Configuration Metadata: Settings such as form IDs and titles, published form URLs, hidden payload configuration, selected folders or templates, branding preferences, delivery settings, workflow mode, counts, timestamps, and redacted operational status.
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 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. naborlydone-controlled hub and short-link systems are designed not to retain customer-owned submissions, signatures, signed PDFs, member sheets, private keys, signed-copy email content, or private workflow state.
Inkify Hub Processing: The Inkify Hub may retain admin/license/support metadata, form configuration metadata, safe form registry records, redacted workflow projections, operational 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, 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, currently planned at $2/month or $20/year per profile. Billing metadata is handled only as needed to operate the profile subscription.
License Usage, Subscriptions, and Future Limits
If an organization chooses to share a single designated lifetime license or administrative email among multiple users, the Licensee is solely responsible for how those credentials are distributed and utilized. Consequently, we assume no liability for internal privacy breaches, unauthorized document generation, or data exposure that may occur as a result of multiple individuals sharing a single license.
Furthermore, while we operate on an honor system for team deployments, we reserve the right to audit unusually high-volume accounts. We retain the right to introduce technical seat limits, enforce access controls, or suspend licenses exhibiting excessive usage patterns detrimental to our infrastructure in future updates to prevent system abuse.
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. We do not sell or share your personal data for marketing purposes.
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, process check-ins with Google Gemini/Vertex AI, organize transcripts into summaries and tasks, maintain categories and schedules, send reminders, and support export or account deletion requests.
- • 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 Inkify: We use Inkify admin, license, 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.
- • Account Deletion: RoozCast includes an account deletion flow that removes the authenticated user's Firestore data, stored check-in audio files, and Firebase Authentication account. This action is intended to be permanent.
- • 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.
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 for AI processing; Google Calendar and Google Tasks for optional user-authorized sync; 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.
Inkify uses third-party providers only to operate selected features: Google Workspace for form-owner processing, Cloudflare for Hub, routing, and encrypted profile storage, Zoho ZeptoMail for profile login-code delivery, Stripe or another disclosed payment processor for license and saved-profile billing, and limited AI services only for 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: RoozCast data is stored using Firebase and Google Cloud services with encryption in transit and at rest. User data access is restricted by authentication, Firebase Security Rules, and backend service permissions.
- • Integration Secret Handling: OAuth tokens and API keys for RoozCast integrations are stored in a separate private area 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 request permanent removal of their RoozCast account and stored data.
Neighborhood Technology Solutions LLC
1847 W Morse Ave. Chicago, IL 60626
Email: support@naborlydone.com
Phone: (773) 942-0995