Founding marketplace terms

Approved daily and weekend launch policy

Our booking policy sets out the approved 15% landowner commission, owner transfer target, and cancellation/refund rules for paid launch. Paid checkout and real payouts remain inactive. Existing requests and holds are not paid bookings and do not constitute acceptance of a future payment agreement.

Parcel-first private owner workspaces

An eligible continuation begins with a private workspace, not a listing. You must choose the exact state-bound county and separately assert that you control the hunting rights or are authorized to represent them. That assertion does not verify identity, ownership, title, authority, parcel boundaries, or hunting rights. Saving it creates no public inventory, booking, payment, agreement, permission, or right of entry.

You may separately authorize Back40 Pass to use one private record clue to prepare a parcel before you finish the hunt details. This authorization ends at the earlier of 30 days or the continuation expiry. The clue is removed when used, cancelled, or expired; expiry also removes any unpromoted staged parcel source and geometry. If a prepared parcel transfers when a complete listing is created, it remains an unconsented, unverified private draft. You must still review it, separately consent to the exact boundary-and-evidence revision, submit it, and pass operator review. No workspace or promotion action by itself publishes a listing or map.

Private hunter invite links

A hunter may choose to share a request-specific, expiring link with a possible landowner. Anyone who receives or is forwarded that link can view its limited state, game, party-size band, and timing summary until it expires, is revoked, or the request becomes inactive. Hunters may ask hello@back40pass.com to revoke an issued link; that link cannot be restored afterward. Do not post or forward another person's invite without permission, attempt to discover invite secrets, or use an invite to harass or misrepresent either party.

A landowner response through an invite only tells Back40 Pass about a possible property fit. It does not reveal either party's private contact details to the other, create a verified match or introduction, accept terms, grant hunting access, or prove authority over a property. Back40 Pass may review, decline, close, or mediate the response before any introduction.

Originating-hunter public listing handoffs

If an active private landowner response becomes a reviewed public listing through its exact source relationship, an authenticated Back40 Pass operator may prepare a public-listing note for only the hunter whose request originated that response. The tool is available only while the exact request lineage, active statuses, eligible response stage, stored state and canonical game, and every current strict-public listing gate still match. The note uses only already-public listing facts and the public URL; it does not disclose landowner contact, exact private location, private notes, parcel or source evidence, access instructions, internal identifiers, or capabilities.

Copying the note or opening a local email draft does not itself send or deliver a message and creates no send, delivery, receipt, or open record. The note is informational, not a verified match, offer, reservation, lease, booking, payment, priority right, listing guarantee, permission to enter, or hunting access. The hunter must separately request dates, and the owner and Back40 Pass must still review availability and terms. A listing can later be paused or removed, so the current public page controls.

Current service status

Back40 Pass is collecting hunter demand, reviewing possible properties, and allowing no-payment requests for dates on any separately verified public property records. Paid bookings are not currently offered. Joining a list, submitting a property, or requesting dates does not create a reservation, lease, listing agreement, guarantee of service, or right to enter any property.

Private landowner continuation, manager, and browser-return capabilities

After the property-interest quick start or a private response to a hunter request, Back40 Pass may return a short-lived, one-use private link that can continue only that saved interest or response into the full property-draft form. Anyone holding an active link may view and use its prefilled contact and broad property basics, so do not forward, publish, probe, or attempt to discover another capability. The link becomes unavailable after expiry, successful full-draft use, or another terminal condition, and Back40 Pass does not distinguish those conditions on the public-facing page. The success screen validates an eligible returned continuation and keeps its relative path and fragment only in an in-memory ref—not React-rendered state, an href, a fallback field, analytics, application logs, query parameters, or JavaScript-accessible browser storage. The original submitter may choose Continue, which revalidates the ref-held value and navigates the same tab with only the relative path and fragment, or explicitly choose Copy for their own return. Only Copy constructs the absolute same-origin link and writes it to the system clipboard. Anyone who uses it can continue the draft and receive its manager control, including the ability to retire the draft. Save a private copy only for your own return; never forward or publish it or save it in a shared or insecure place.

An eligible quick-start success may also show a clearly separate, reusable public signup link that the landowner may choose to share with another landowner. That public link contains only a state, member referral code, and fixed campaign labels and opens a blank property-interest form. It contains no submitted name, contact detail, property area, relationship answer, continuation capability, or manager control. Sharing or opening it cannot continue or control the original interest, and it does not create a property interest, listing, booking, payment, hunting permission, or access for the recipient.

An eligible property-interest quick start—but not a demand-linked private response—also queues one automatic continuation email to the submitted address. Its separate capability is prepared only when the dispatcher claims that exact work, is usable for up to seven days from preparation, cannot outlive the original continuation, and shares the same one-draft consumption and source-eligibility gates. Back40 Pass server and workflow records store a one-way hash and limited installation, expiry, first-resolution, queue, attempt, and provider facts, not the raw emailed capability or generated body; resolving the link can store that same raw capability in the separately described HttpOnly browser-return cookie. Anyone holding the active emailed link can continue the draft. Opening it does not verify the email address, identity, ownership, title, authority, or hunting rights, and it is not property submission for review, publication consent, publication, a listing agreement, reservation, booking, payment, permission to enter, or hunting access. Message timing and delivery are not guaranteed.

Back40 Pass may automatically store one raw capability for the latest eligible landowner continuation or property manager in this browser. The host-only cookie has no Domain attribute, is HttpOnly, Secure, SameSite=Strict, is scoped to the exact /api/landowner-resume path, and lasts no more than 30 days; the underlying flow may expire or become unavailable sooner. A newer eligible flow overwrites the older browser return. Anyone using the same browser profile may try it, so use Forget on the property-review page when the browser is shared or you no longer want that return. Forgetting the browser return does not by itself delete the underlying interest or draft. A copied private link remains the backup for another browser or device, and anyone holding an active copied capability can use its controls.

The resume API revalidates the current database record before a same-origin 303 response returns the existing private route with the raw capability in its URL fragment. The destination page scrubs that fragment before its first private API request. An invalid, expired, used, rotated, retired, or otherwise unavailable browser return is cleared. The raw cookie is unavailable to page JavaScript and is not copied into React state, local or session storage, analytics, application logs, query strings, metadata, referrer data, or public HTML. An exact stale-link 404 requests cleanup only if the cookie still matches that capability, so it does not clear a newer flow. Validation conflicts and temporary failures do not trigger that cleanup.

Saved name, email, state, and broad area remain tied to the quick start or response. A mapped owner or authorized-representative answer and supported game category also remain tied to it. A co-owner or person who was unsure must truthfully choose owner or authorized representative before continuing; that choice remains an intake statement and does not prove authority. The full property-draft email consent is separate, required for that draft, and unchecked by default. The current full form—whether direct or continuation-linked—uses the same-session parcel-v1 path and opens private draft control through a same-origin URL-fragment capability. That handoff does not queue or verify a confirmation email. The manager keeps the scrubbed capability in a ref unless the current holder explicitly copies it for their own return. Only that click constructs the full private link and writes it to the system clipboard. Anyone holding the active manager capability can control or retire the draft. Save a private copy only for your own return; never forward or publish it or save it in a shared or insecure place. The holder has seven days from draft creation to record an owner or authorized-representative assertion. A successful assertion ends that deadline, and the same manager fragment capability then remains active until it is rotated or the draft is retired. Mode-omitted client submissions and legacy records may instead retain their email-recipient confirmation deadline and controls. Neither the assertion nor a legacy confirmation proves identity, ownership, title, authority, or hunting rights. Opening, resuming, or completing either path is not submission for operator review, publication consent, publication, a listing agreement, reservation, booking, payment, hunting permission, or right of entry.

Property reviews, parcel-v1 evidence, and fictional examples

A property submission creates only a private pending draft. The current full form uses the same-session parcel-v1 path, where parcel evidence is mandatory before the listing can be submitted for operator review. The holder must choose a state-bound county, provide a Polygon or MultiPolygon boundary and source evidence, and provide a private parcel or APN reference for owner-drawn evidence. An official-record link is a research path only; third-party records, an APN, an owner assertion, and a drawn or imported boundary do not prove title, ownership, authority, surveyed limits, access rights, or hunting permission. Mode-omitted client submissions and legacy records may retain the earlier confirmed-email review flow.

After the owner assertion, the manager holder may separately authorize Back40 Pass for up to 30 days to use one private address, parcel or APN, official-record URL, or other record clue to prepare an unconsented private parcel draft. That authorization is not public-boundary consent, ownership or authority verification, parcel submission, listing submission, publication, booking, payment, or permission to enter. The manager holder must inspect or edit any prepared map, separately check the exact-revision publication consent, and submit the parcel evidence. The clue cannot be used for preparation after its 30-day expiry. Back40 Pass clears the raw clue and optional owner note immediately when the request is prepared or cancelled, or before returning status on the next private owner or authenticated operator check after expiry. The operator-prepared draft remains private and cannot bypass the existing owner-consent or operator-publication gates.

A local GeoJSON import stays in the tab until an explicit save or submit; Feature properties are ignored. Saving a parcel draft does not publish it or satisfy the parcel-v1 listing-review gate. Submitting the current parcel revision requires separate, unchecked-by-default consent to publish only its operator-verified boundary and county if the listing later remains eligible. Parcel-v1 consent and verification bind to the exact geometry and evidence revision. A geometry, county, APN, or source-evidence revision resets consent and verification, and an owner may revoke publication or delete the map. Any such invalidation on a published parcel-v1 record pauses the listing and removes its public listing, map, and sharing surface until current evidence is submitted and the property passes operator re-review. Neither a draft, owner assertion, parcel submission, nor map consent reserves dates, authorizes Back40 Pass to offer access, proves authority over hunting rights, or grants anyone permission to enter. Back40 Pass may request more information, approve, reject, pause, remove, or retire a property record.

Cards marked as examples are fictional product previews, not property listings or available inventory. Their scenes and prices are illustrative. They cannot be requested as properties, reserved, purchased, reviewed, ranked, or treated as evidence of local rates or availability. A “request a hunt like this” action creates only a general hunter request for similar access.

Requests for dates and 24-hour platform holds

A request to book asks a landowner to consider specified access dates. The request alone is not an offer acceptance, reservation, lease, booking, permission, or right of entry, and it does not block dates. No payment is collected through this flow. If the owner expressly authorizes the exact dates, party size, whole-party land-access subtotal, and conditional hold, Back40 Pass may issue that access-price snapshot and let the hunter start one free 24-hour platform hold while every current gate still passes. When issued, Back40 Pass stores an immutable, versioned price-offer record containing the bounded price/hold request and public-listing snapshots, access subtotal, canonical price/hold snapshot digest, owner-authorized hold-scope digest, and explicit blocked-checkout facts. It also stores one role-bound owner acknowledgement derived from that exact prior authorization and, only if the hunter acts, a separate hunter acknowledgement of the canonical price/hold snapshot digest. “Offer” is a workflow record label, not a legal offer capable of acceptance. Neither acknowledgement is an identity verification, signature, contract acceptance, final agreement, order, booking, payment, or grant of access. An active hold blocks overlapping Back40 Pass requests and holds for that listing and date range until its database-recorded expiry or earlier release. It does not control an owner's off-platform calendar, create a paid booking or final property-access agreement, or grant permission to enter or hunt.

This founding workflow can durably queue a mode-omitted or legacy listing confirmation, hunter request receipt, private owner date request, and quote-ready notice. An eligible property-interest quick start can separately queue one automatic continuation message before a property draft exists. Current same-session parcel-v1 drafts do not create listing-confirmation email work. After current eligibility and any operator-authorization gate passes, Back40 Pass may use a configured provider or a controlled manual fallback. Separate legacy records can retain manual queued, prepared, marked-sent, skipped, stale, or cancelled facts; a manual marked-sent record is only an operator attestation, and automatic provider events do not create it. Back40 Pass does not guarantee message timing or delivery.

An active request may be withdrawn through its private capability link. Withdrawal, operator decline, or request expiry releases any still-active platform hold. Because this founding flow creates no paid booking and collects no payment, no cancellation fee or paid-booking cancellation policy applies. The current price breakdown shows the known whole-party land-access subtotal, no Back40 Pass charge at the request or hold stage, and total due now of $0. Platform fees are not configured, taxes are not determined, cancellation and refund terms are not configured, no payment provider is connected, and no final payable total is available because no checkout exists. Any later paid product must create a fresh agreement and acceptance record and disclose every fee, applicable tax, refund term, cancellation rule, and charge timing before acceptance.

A displayed daily price covers one local calendar day of private-land access for the whole party, subject to the stated party limit. Unless a future listing and final agreement expressly say otherwise, it does not include lodging, guiding, licenses, permits, tags, equipment, transportation, or any promise of seeing or harvesting game.

Checkout preparation records

When an eligible hunter acknowledgement starts a platform hold, Back40 Pass may create a private, versioned checkout-preparation record tied to that request and exact price snapshot. It records the USD access subtotal, $0 due now, hold times, lifecycle, and the exact blocker states: checkout is blocked; payment is not collected; the platform fee, agreement terms, cancellation policy, refund terms, and payment provider are not configured; taxes are not determined; the final payable total is unavailable; and property-access permission is not granted. It may close only with a bounded workflow reason when the request or listing no longer supports the preparation.

The checkout-preparation record is internal evidence only. It is not an agreement, order, acceptance, checkout, payment, booking, reservation, property-access grant, hunting permission, or promise that paid access will be offered. It creates no action for either party and cannot replace the fresh written terms, acceptance record, final price disclosure, valid permission, and other gates required for any future paid product.

Private owner date-request decisions

A private owner-review link lets its holder view a limited request snapshot and choose either to authorize the exact dates, party size, and snapshotted whole-party land-access subtotal for a conditional 24-hour platform hold or decline the request. Anyone with an active link can use that capability. Do not forward it, publish it, try to discover another link secret, or use a link unless you are authorized to act for the property.

The owner may add a private decision note of up to 500 characters. Do not place sensitive access instructions, exact property details, another person’s contact information, or unlawful content in that note. Continuing requires the owner to check an authorization for this request's exact dates, party size, and snapshotted whole-party access price; the owner action does not itself start a hold. A hold begins only if the access-price snapshot is issued and the hunter acts while the dates remain eligible. The owner may separately choose an unchecked contact-sharing consent for one request-specific mutual email introduction; declining does not record either authorization. Once either action is recorded, the owner link cannot be used again. The authorization permits only the snapshotted access-price terms and limited platform hold. It is not payment, a final access agreement, permission to enter, or hunting permission. A decline decision ends this request workflow without creating those outcomes.

Optional mutual email introductions

When a hunter starts the 24-hour hold and acknowledges the owner-authorized access-price snapshot, either, both, or neither optional introduction choice may be selected. If no introduction was requested at hold start and the introduction has not already queued, released, or closed, the holder of the hunter's private request capability may make one separate later request while that exact hold remains active. The later form presents contact-sharing consent and an adult attestation as separate unchecked choices; both must be affirmatively selected. That action does not restart, replace, or extend the hold, change its dates or expiration, change the booking-request status, collect payment, or create a booking or access right. Anyone holding the active private request link can use the actions it makes available, including authorizing this limited name-and-email sharing, so the link must not be forwarded, published, or stored insecurely.

An introduction is eligible only while that request's exact hold remains active, the owner separately authorized contact sharing, the hunter separately authorized contact sharing, the hunter separately attested that they are at least 18 and authorized to discuss the request, and Back40 Pass confirms that every current request, listing, availability, delivery, and review gate still passes. Each authorization is limited to sharing the owner’s and hunter’s names and email addresses with one another in one request-specific mutual email. The draft may include broad approved request facts needed to identify the request. It must not include phone numbers, an exact address or location, parcel or APN information, source evidence, entry or access instructions, private notes or message text, capability links, internal identifiers, or referral and campaign data. This authorization is not consent to unrelated marketing. Authorized operators already process submitted contact data in the separate private listing, request, and delivery workflows; introduction release authorizes assembly of one combined mutual To/Cc draft.

Back40 Pass may atomically recheck the current gates and irreversibly authorize and assemble that draft in its private operator workflow. Awaiting, queued, released, skipped, stale, and cancelled workflow states move only forward; a closed or released introduction cannot be restarted through the hunter action. Only after release may a configured provider receive the separately consented names and email addresses as one To recipient and one Cc recipient with the current allowlisted content, or an operator may use a controlled manual fallback. Release does not prove dispatch, provider acceptance, recipient-server delivery, receipt, opening, reading, answer, identity, suitability, a match, paid booking, final access agreement, payment, property authority, permission to enter, or hunting access. Outcomes can differ for the To and Cc recipients. A later withdrawal, expiry, or listing change cannot recall an already released draft. Either party remains free not to reply, and any later arrangement requires separate written terms and valid permission from the person who controls the hunting rights.

Public maps and reviewed parcel boundaries

At a broad zoom, public price markers show an approximate area from a separately reviewed and consented parcel publication. At zoom 12 or closer, the public map may show that reviewed parcel boundary and county. It never publishes the parcel or APN reference or private source evidence. Owner-supplied or reviewed geometry is not a survey, title record, ownership proof, parcel-provider verification, entry point, access route, direction, invitation, guarantee of game or legal hunting access, or permission to enter. The map can omit live hunts that have no eligible reviewed parcel publication. Do not use any marker or boundary to approach or enter private property.

No access by signup

You may enter private land only with valid permission from a person authorized to grant it. A website signup, email, referral code, map, or expression of interest is not permission. Future access, if offered, will require a property-specific process and acceptance.

Hunting responsibility

Hunters are responsible for current licenses, permits, tags, seasons, county rules, methods, safety, and all applicable laws. Landowners remain responsible for their own legal and tax obligations. Information on this site is general planning information, not legal, tax, insurance, or wildlife-management advice.

Accurate information

You agree to provide information you reasonably believe is accurate and not to impersonate others, misrepresent property authority, submit unlawful content, probe the service, or interfere with its operation.

Public hunter-request board

If you separately ask us to review a public hunter request, you confirm that you are at least 18 and that the broad public area and hunt details are accurate to the best of your knowledge. Do not enter an address, exact ZIP, parcel identifier, phone number, email address, landowner name, or another person’s information in the public-area field. Back40 Pass may approve, decline, hide, or remove a request and does not promise publication or a response.

A public request is an expression of interest—not a property listing, offer, booking, lease, verified match, guarantee that a hunter is ready to transact, or permission to enter land. A landowner’s possible-fit submission is not a direct introduction or acceptance. Any future property-specific access requires separate review and valid approval from the person who controls the hunting rights.

Hunter Demand Watch

A Hunter Demand Watch is an optional, private request for watch-only email about new active public hunter-request briefs matching one state and either any reviewed game category or one exact category. A watch remains pending until the email recipient confirms it through the private link. Creating or confirming a watch does not create a land listing, property offer, booking, lease, match, obligation to respond, or permission to hunt.

Confirmations and alerts are reviewed and may use a configured provider or a controlled manual fallback. Back40 Pass does not guarantee message delivery or timing, that a qualifying public brief will appear, that either side is suitable or ready to transact, or that a match, introduction, agreement, or access will result. An unsubscribe action closes this watch and its unclaimed work only; it does not globally suppress unrelated requested email to the same address. A provider-claimed message is already in flight and may complete after unsubscribe. Do not enter another person’s email without their permission, forward a private management link, or attempt to discover or misuse a link secret.

Hunt Availability Watch

A Hunt Availability Watch is an optional, private request for watch-only email about real reviewed hunts that are published or republished into live inventory after the watch was created. A current watch has one required U.S. state and either any listed game category or one exact category; it can also require any future dates or one exact date range of up to 14 days, an optional party size, optional whole-party daily price bounds, an optional access type, and an optional legal method. Every saved criterion must match. A watch remains pending until the email recipient confirms it through the private link, and an exact-date watch automatically stops matching after its end date. Legacy state-and-game-only watches remain usable under their earlier criteria version and are not silently broadened or converted. Example hunt cards are fictional and never qualify for watch counts or alerts.

A public search-to-watch handoff may encode the unassociated search criteria in the URL and prefilled form, so do not share that URL if you do not want another person to see those filter values. It does not include the hunter's email, a saved watch identifier, or a private capability. After submission, the email-to-saved-criteria association remains private and is not published to landowners or on hunt pages. Confirmation, management, and unsubscribe pages require a private fragment capability, remove the fragment and query before resolving, do not place the raw capability or private email-to-criteria association in browser storage or analytics, and show saved criteria only after same-origin authorization. Eligible confirmation and alert work may use a configured provider or a controlled manual fallback. Acceptance, queueing, preparation, provider acceptance, or manual attestation does not guarantee sending, delivery, receipt, opening, reading, timing, qualifying inventory, continued availability, a response, reservation, booking, payment, agreement, or permission to hunt. An unsubscribe action closes this watch's unclaimed work only and does not suppress unrelated requested email to the same address. A provider-claimed message may complete after unsubscribe. Do not enter another person’s email without permission, forward a private management link, or attempt to discover or misuse a link secret.

Email queue and provider status

Back40 Pass durably queues mode-omitted or legacy listing confirmations, hunter request receipts, private owner date requests, quote-ready notices, watch confirmations and alerts, and separately authorized mutual introductions independently of provider configuration. Current same-session property drafts do not create listing-confirmation email work or an email-verification fact. Dispatch must win an exact claim before sharing a recipient address and current message content with the provider; a mutual introduction also requires exact prior operator release before its To/Cc addresses and allowlisted content can be disclosed. If no automatic attempt is active, an authorized operator may prepare a controlled manual fallback only after closing competing unclaimed work. A watch confirmation's link-prepared time records that its private capability and link were prepared through either path; only its separate marked-sent time is a manual operator attestation. A claimed attempt is irreversible and may finish after its source closes.

Queued or retry-waiting work is not sent. Provider acceptance means only that the provider accepted the API request; it is not recipient-server delivery. A delivered event means a recipient mail server accepted the message, not inbox placement, recipient receipt, open, read, reply, match, booking, payment, agreement, permission to enter, or hunting access. Outcomes can differ for To and Cc, and Back40 Pass does not treat opening or reading as an observable workflow outcome. Retry attempts stop within the original 24-hour idempotency window; if no reliable terminal result exists then, the provider outcome is reported as unknown. Verified hard bounces, complaints, and provider suppressions may block other provider messages to the same address, but a source-specific watch unsubscribe does not.

Planning estimates

Earnings examples and calculators are illustrative only. They do not guarantee rates, demand, availability, bookings, income, fees, taxes, expenses, or the final marketplace model.

Official information controls

Season summaries can become outdated. Official agency rules and current law control. Linked third-party sites are governed by their own terms and policies.

Changes and contact

We may update these founding marketplace terms as the service develops. Material marketplace terms will be presented before any paid transaction. Questions can be sent to hello@back40pass.com.