Hunt NYC
Privacy Policy
Effective November 18, 2026
Hunt NYC is operated by Mark Zolott and Jacob Yoel (“we,” “us,” or “our”). This Privacy Policy explains how we collect, use, and share information when you use our apartment-search organizer.
Questions or privacy requests: teamhuntnyc@gmail.com
1. INFORMATION WE COLLECT
Account information. When you create an account, we collect your email address and assign an internal account identifier. If you use Google sign-in, Hunt NYC receives your name and email address through our authentication provider. You may also add or edit a display name. If you create a password, we store a password hash rather than the password itself.
Profile and preferences. Depending on which features you use, you may provide a work address, arrival-time preference, apartment preferences, and consent choices. We also store location coordinates and lookup status associated with your work address. Account records may contain a phone number, optional tour-contact email, and tour-related acknowledgment if you have provided them.
Apartment-search content. We store information you add or generate while using Hunt NYC, including:
- Hunts, budgets, move-in dates, membership, and roles.
- Saved listings, addresses, photos or photo links, prices, amenities, and listing links.
- Agent and brokerage contact information.
- Apartment and agent notes, follow-ups, and contact history.
- Votes, comments, activity, workflow stages, and commute estimates.
Support and feedback. If you submit feedback, our managed email service processes your message, account name and email, page or section information, and any attachments you include. Feedback is delivered to teamhuntnyc@gmail.com. To limit excessive submissions, the feedback feature also records a submission ID, your internal account ID, and a timestamp separately from the email. This submission log does not contain your message or attachments.
Technical and security information. We and our service providers process technical information to operate and secure the service. Hunt NYC stores session tokens, associated user IDs, and session-expiration timestamps. For password-reset abuse prevention, Hunt NYC records email addresses or IP-address information, attempt categories, and timestamps. Our hosting and other service providers may also process technical information associated with requests to their services. If you request a password reset, we also store a password-reset record with an expiration timestamp.
Optional analytics. If you accept analytics cookies, Google Analytics processes page visits and app-feature usage. This activity may be associated with a pseudonymous identifier derived from your internal account ID.
Please avoid entering sensitive information that is unnecessary for organizing your apartment search, such as Social Security numbers, bank details, or identity documents.
2. HOW WE USE INFORMATION
We use information to:
- Create accounts, authenticate users, and maintain sign-in sessions.
- Save and display apartment-search information and preferences.
- Support collaboration within shared hunts.
- Import listings and provide maps, address lookup, and commute estimates.
- Respond to feedback and support requests.
- Protect accounts, prevent abuse, and troubleshoot problems.
- Understand use of the service through optional analytics, when accepted.
- Send account, security, support, and important service-related messages. We do not currently use your account email to send promotional emails.
3. SHARED HUNTS
Members of a shared hunt can access shared apartment-search information, including listings, notes, contact history, comments, activity, and member display names. Members can modify shared information according to the app’s permissions. The member list includes roles and join dates. Hunt owners can also view members’ full email addresses and manage membership and sharing settings. If you have not provided a display name, the app may display the portion of your email address before “@” as your name.
Shared-hunt members can access other current members’ available commute results for shared listings and whether they have a work address configured. Shared results may include estimated travel time, transfer counts, walking time, subway lines, bus routes, the arrival time used for the calculation, calculation date, and calculation status. This shared-commute response does not include work-address text or destination coordinates. Although your work address and destination coordinates are not shared, the commute details visible to other members may allow them to infer your approximate work location.
Owners can allow members to share the hunt’s invitation link. A signed-in person with a valid invitation link can join without a separate approval step. Share invitation links only with people you intend to invite. Only the owner can reset the invitation link to invalidate the old link.
Leaving a hunt, being removed, or deleting your account does not necessarily remove your previous contributions or activity. Votes may remain visible to other members with your internal user ID attached. Other retained records or text may also contain information associated with you. Deleting your account may leave cached commute results stored, although commute entries associated with former members are not returned to remaining members through the shared-hunt API. See “Retention and Deletion” below.
4. SERVICE PROVIDERS AND THIRD-PARTY FEATURES
The following services process information in connection with Hunt NYC:
- Emergent provides hosting, managed database infrastructure, Google sign-in integration, and managed email delivery. Email content and any attachments are processed through its email-delivery service.
- ScraperAPI processes listing-import requests involving StreetEasy URLs.
- NYC GeoSearch receives address text, including listing addresses and a work address you provide, to look up building locations.
- Transitland receives listing-location coordinates, your saved work-location coordinates, and your selected arrival time to calculate commute estimates.
- OpenStreetMap Foundation provides the map tiles displayed in Hunt NYC. When a map loads, your browser connects to its tile service and requests tiles corresponding to the map areas you view. The service receives technical information such as your IP address, browser and device information, and request details. OpenStreetMap Foundation processes this information under its own Privacy Policy.
- Google Analytics processes optional usage analytics after you accept analytics cookies. This may include page visits, app-feature usage, and a pseudonymous identifier derived from your internal account ID.
Hunt NYC’s operators, Mark Zolott and Jacob Yoel, can access production user records through the platform’s database-management tools to operate and support the service.
5. COOKIES AND BROWSER STORAGE
Hunt NYC uses an essential sign-in cookie called hunt_session to maintain your session. It is configured with a 30-day lifetime.
We also use browser storage for analytics choices, interface preferences, walkthrough progress, and temporary invitation and welcome flows.
Google Analytics is configured to load on our production site only after you accept analytics cookies. With your consent, it collects page visits and app-feature usage and may associate that activity with a pseudonymous identifier derived from your internal account ID. Our analytics code is designed to remove query strings and URL fragments from manually reported page locations.
You can accept or reject analytics through the analytics banner and change your choice in Settings → Analytics → Analytics preferences. Rejecting analytics does not disable essential sign-in functionality. If you withdraw a previously granted choice, the app attempts to remove Google Analytics cookies and reloads the page to stop the loaded analytics tag. Withdrawing consent does not itself delete information already sent to Google Analytics.
Our hosting platform’s optional visitor-analytics cookies are disabled for Hunt NYC. The hosting platform continues to maintain server request logs, which may include IP addresses, browser information, and pages requested. Disabling hosting analytics cookies does not disable this logging.
6. RETENTION AND DELETION
We retain information to provide the service and support security and operational needs. Retention varies by record type.
You can delete your account through Settings → Delete account and confirm the deletion. The account-deletion process removes your account record, sign-in sessions, specified account-linked import and tour-processing records, and password-reset records. It also deletes hunts where you are the only remaining member, including their listings and embedded commute and vote data, comments, hunt activity, contact notes, contact history, and listing-import queue entries. It does not remove every record associated with your use of Hunt NYC.
Shared hunts remain available to their other members. If you own a shared hunt, ownership transfers to its longest-standing remaining member. Tasks assigned to you may be reassigned or become unassigned, and contact-note ownership may be reassigned. Your contributions and past activity may remain in shared hunts. Although some authorship may be displayed as “Former member,” retained identifiers, records, or text may still contain information associated with you. Votes remain visible to other members with your internal user ID attached. Under the current account-deletion implementation, cached commute results associated with your user ID may also remain stored on shared listings, but those entries are not returned to remaining members through the shared-hunt API. Leaving a hunt or being removed clears your cached commute entries for that hunt. After leaving, removal, or account deletion, you no longer have API access to that hunt’s shared information.
Password-reset records. Password-reset links expire after 30 minutes. Expiration prevents use of the link but does not necessarily delete the associated database record. The account-deletion process removes account-linked password-reset records. We have not established a fixed retention period for reset records that remain stored before account deletion.
Password-reset abuse-prevention records. We retain records containing email addresses or IP-address information, attempt categories, and timestamps to help prevent abuse. We have not established a fixed retention period for these records, and they may remain after account deletion.
Deleted listings initially remain stored and may be restored through Recently deleted. Listings deleted more than 30 days ago become eligible for permanent cleanup, which runs when the hunt’s active or deleted listings are requested rather than on a guaranteed schedule. A separate permanent-delete action can remove a deleted listing sooner. These cleanup paths remove the listing record and its associated comments, but do not themselves remove separate hunt activity, contact notes, or contact-history records.
Deleted hunts may remain recoverable before permanent cleanup. Hunts deleted more than 30 days ago become eligible for cleanup when your active or deleted hunts are requested, rather than on a guaranteed schedule. A separate permanent-delete action can remove a deleted hunt sooner. These cleanup paths remove the hunt, its listings, contact notes, and comments, but do not themselves remove separate activity, contact-history, or listing-import queue records. We do not promise permanent deletion exactly 30 days after a hunt is deleted.
Optional analytics. Our Google Analytics property is currently configured with a 2-month event-data retention period and a 14-month user-data retention period. New activity resets the user-level retention period. These settings do not control the retention of most standard reports based on aggregated data.
Feedback emails and attachments. Feedback emails and attachments are retained in our team inbox so we can review submissions, respond, and refer to past issues. We have not established a fixed retention period for these emails and attachments. Deleting your Hunt NYC account does not automatically delete feedback emails or attachments from our inbox. You can contact teamhuntnyc@gmail.com to request their deletion.
Feedback-submission logs. To limit excessive submissions, the feedback feature records a submission ID, your internal account ID, and a timestamp. These records do not contain your message or attachments. We have not established a fixed retention period for these records, and they may remain after account deletion.
For questions about retained information or to request access, correction, or deletion, contact teamhuntnyc@gmail.com. We may need to verify your identity before responding.
7. SECURITY
We use measures intended to protect information, including password hashing and controls on sign-in sessions. No online service or transmission method can be guaranteed completely secure.
8. AGE REQUIREMENT
Hunt NYC is intended for adults aged 18 and older. If you believe someone under 18 has provided personal information through the service, please contact us at teamhuntnyc@gmail.com so we can investigate and take appropriate action.
9. CHANGES TO THIS POLICY
We may update this policy as the service or our practices change. We will update the date above and provide any additional notice required by applicable law.
10. CONTACT
Mark Zolott and Jacob Yoel
teamhuntnyc@gmail.com
