Version 5.1
| Field | Detail |
|---|---|
| Prepared | September 22, 2026. Conformed to Terms of Service v5.2 on September 29, 2026. |
| Effective date | September 29, 2026 |
| Supersedes | Version 4.0, dated May 14, 2026. Conformed to Terms of Service v5.2, effective September 29, 2026. |
| Status | Published. Reviewed by Georgia-licensed counsel. |
| Document owner | BaseNest LLC — support@basenest.io |
SCOPE OF CHANGE: This version restores the canonical Version 4 section structure, resolves internal contradictions introduced in the August 2026 working file, and adds provisions for Named Co-Travelers and for Linked Spouse Accounts created under Terms of Service §3.5. It is conformed to Terms of Service v5.2, which establishes two booking products — Standard Stay of one to twenty-nine nights and Extended Stay of thirty to eighty-seven nights, billed in installments. Sections 2.4, 4, 6.1, 7.1, 7.4, 8, and 11.10 reflect the data generated by the Extended Stay product, by the Continuation Confirmation mechanism in Terms of Service §5.12, and by the duration-based tax determinations in Terms of Service §7.2. Alabama is included as an active market.
SUMMARY: This Privacy Policy explains how BaseNest LLC collects, uses, shares, and protects your personal information when you use our Platform. By using the Platform, you agree to this Privacy Policy. If you do not agree, please discontinue use of the Platform.
BaseNest LLC is not affiliated with, endorsed by, or acting on behalf of the United States Department of Defense or any federal agency.
BaseNest LLC ("BaseNest," "we," "our," or "us") operates a verified rental marketplace serving U.S. service members, Veterans, DoD civilians, and government contractors. The Platform offers two booking products under Terms of Service §5: a Standard Stay of one (1) to twenty-nine (29) consecutive nights, and an Extended Stay of thirty (30) to eighty-seven (87) consecutive nights billed in installments. This Privacy Policy applies to all users of the Platform and to both products — both Guests (users who book lodging) and Hosts (users who list lodging). Where a data practice applies to only one booking product, this Policy says so.
This Policy also applies to Named Co-Travelers: spouses and adult dependents who stay at a Property under a booking made by a verified account holder but who do not hold a BaseNest account of their own. It applies as well to Linked Spouse Account holders: spouses who hold a limited, derivative login credential created under §3.5 of the Terms of Service, described in §2.3A below. Named Co-Travelers are described in §2.3, and their rights are described in §10 and §12.5.
Where data practices differ between Guests, Hosts, Named Co-Travelers, and Linked Spouse Account holders, this Policy identifies the difference.
Collected from all account holders at registration:
| Data | Purpose |
|---|---|
| Full name | Account identification and communications |
| Email address | Account management, notifications, and marketing (with consent) |
| Phone number | Account security and support communications |
| Pay grade | E-1 through O-10, Warrant Officer, GS schedule, or equivalent — extracted from verification document |
| Branch of service or agency | Extracted from verification document |
| Duty station / installation | Used to match Guests with relevant listings |
| Verification status | Approved, denied, or pending |
| User role | Guest, Host, or both |
BaseNest's verification process differs between Guests and Hosts.
Guests verify eligibility by submitting one of the following:
Guest verification is conducted by BaseNest staff. It is a human review process, not automated. No biometric data is collected from Guests.
Document handling:
Data extracted and retained from the verification document:
| Data extracted | Notes |
|---|---|
| Name | Confirmed against account registration name |
| Pay grade | E-1 through O-10, Warrant Officer, GS schedule, or equivalent |
| Branch of service or agency | Army, Navy, Marine Corps, Air Force, Space Force, Coast Guard, DoD civilian, contractor |
| Verification status | Approved or denied |
SSN ADVISORY: LES documents frequently contain a full or partial Social Security Number. BaseNest does not collect, store, record, or use SSN data. Guests are strongly encouraged to redact their SSN before uploading. Any SSN visible on a submitted document will not be recorded, and the document will be deleted upon completion of verification.
Hosts verify identity through Stripe Identity, which uses automated government document capture and biometric face-matching. For Hosts, Stripe Identity processes and manages all verification data within Stripe's own infrastructure. BaseNest does not independently store Host identity verification documents or biometric data.
A spouse or adult dependent may stay at a Property as a Named Co-Traveler on a booking made by a verified account holder (the "Sponsor"). BaseNest does not issue accounts to adult dependents and does not issue an independent Guest account to any spouse. A spouse may, separately, hold a Linked Spouse Account under §3.5 of the Terms of Service — a derivative credential with browsing and proposal rights only. That credential is described in §2.3A and is distinct from Named Co-Traveler status. A verified Sponsor account must exist before a Named Co-Traveler can be added to a booking. A Named Co-Traveler, acting in that capacity, cannot book independently, holds no account, and cannot log in to the Platform. A spouse who separately holds a Linked Spouse Account has the limited access described in §2.3A; that access never includes booking or payment authority.
Eligibility for a Named Co-Traveler is established by either:
Named Co-Traveler eligibility is reviewed by BaseNest staff — the same human review process applied to Guests. No automated decision-making and no biometric processing is applied to Named Co-Travelers.
Data collected about a Named Co-Traveler:
| Data | Notes |
|---|---|
| Full name | Provided by the Sponsor; recorded on the booking record |
| Relationship to Sponsor | Spouse or adult dependent |
| Basis of eligibility | Sponsor's orders listing dependents, or Sponsor attestation |
| Sponsor attestation record | Identity of the attesting Sponsor, date of attestation, and booking reference |
What BaseNest does not collect about a Named Co-Traveler: contact information, identity documents, payment information, biometric data, or military verification documents submitted by the co-traveler. BaseNest does not collect the names or ages of dependent children.
Where a Sponsor submits orders to establish Named Co-Traveler eligibility, that document is handled under the rules in §2.2 — stored temporarily during review and permanently deleted upon completion.
Because a Named Co-Traveler's name is recorded on the booking record, it is retained for the same period as the booking record under §8. A Named Co-Traveler has privacy rights under applicable state law even though they do not hold a BaseNest account. See §10 for those rights and §12.5 for how to exercise them.
A Linked Spouse Account is a secondary login credential created under §3.5 of the Terms of Service and permanently associated with a single Sponsor account. Unlike a Named Co-Traveler, a Linked Spouse Account holder can log in, search listings, view pricing, save listings and searches, and assemble a Proposed Booking for the Sponsor to review. A Linked Spouse Account holder cannot confirm a booking, authorize or change payment, cancel or modify a booking, submit verification documents or military orders, exercise SCRA rights, request a refund, initiate a dispute, or change the Sponsor account settings.
Data collected about a Linked Spouse Account holder: name, email address and login credential, the Sponsor attestation record establishing the link, OFAC screening result, Proposed Bookings assembled, saved listings and searches, and device and usage data generated by that account under §2.6.
What BaseNest does not collect from a Linked Spouse Account holder: identity documents, military verification documents, biometric data, payment instruments, or documentation of the marital relationship.
Information visible across the link. As directed by the Sponsor under §3.5(g) of the Terms of Service, a Linked Spouse Account can see the saved listings, saved searches, Proposed Bookings, booking history, and stay details associated with the Sponsor account. A Linked Spouse Account cannot see the Sponsor's eligibility verification documentation, military orders, or full payment method details. Creating a Linked Spouse Account is therefore an instruction from the Sponsor to disclose that information to a second person, and the Sponsor should not create one unless they intend that result.
A Linked Spouse Account is suspended or terminated at the same time as the Sponsor account from which it derives and cannot survive it. Either the Sponsor or the Linked Spouse may end the link, and BaseNest may suspend or terminate a Linked Spouse Account independently.
No SCRA rights arise from the link. Under Terms of Service §4.3, the existence of a Linked Spouse Account does not by itself make a spouse a named party to an occupancy and does not create, expand, or evidence coverage under the Servicemembers Civil Relief Act. BaseNest therefore collects no military orders, eligibility documentation, or service record from a Linked Spouse Account holder, and holds no data capable of establishing such coverage.
NOTICE TO SPONSORS:By adding a Named Co-Traveler to a booking, you confirm that you have the authority to share that individual's information with BaseNest and that you have made them aware of this Privacy Policy. BaseNest relies on that confirmation and does not contact Named Co-Travelers directly.
| Data | Notes |
|---|---|
| Booking confirmation number | Unique identifier for each reservation |
| Property details | Name, address, nightly rate, booking dates, term length in nights, and booking product (Standard Stay or Extended Stay) |
| Guest and Host names | Associated with each transaction |
| Named Co-Traveler names | Recorded on the booking record where a co-traveler is added |
| Total amounts charged | Including base rate, taxes, and fees |
| Cancellation tier or notice treatment applied | Standard Stay Tier 0 through Tier 3 under Terms of Service §5.3, or Extended Stay cancellation and Notice Period treatment under §5.11. Recorded as part of the transaction record. |
| Cancellation fees assessed | Late-cancellation fee, early-departure fee, or the waiver of the prorated daily charge and refund of the Service Fee applied on a verified military orders release under Terms of Service §5.4 |
| Payment method type | Card type; full card numbers are not stored by BaseNest |
| Military orders (if submitted) | Submitted for SCRA or orders-based cancellation requests; deleted after processing |
| Receipts | Itemized receipts generated for each completed stay, and for each Installment Period of an Extended Stay |
| Installment schedule and installment payment records | Extended Stay only. Installment Periods, Installment Dates, amounts charged, Service Fee charged per installment, and retry or failure records under Terms of Service §5.10. |
| Continuation Confirmation records | Extended Stay only. The identity of the confirming party, the date and time of confirmation, and the booking and Installment Period to which it relates, as required by Terms of Service §5.12(c). Records of non-confirmation are retained on the same basis. |
| Early-termination notice and Notice Period calculation | Extended Stay only. The date written notice was submitted, the resulting Notice Period, and the final chargeable night under Terms of Service §5.11(c). |
| Installment pause requests | Recorded where a Guest gives notice of pending or received orders and requests a pause under Terms of Service §5.4, together with the verification outcome. |
| Duration declaration retained for tax purposes | The Guest's confirmation of the booked term at checkout, which constitutes the declaration of intended duration where a jurisdiction requires one under Terms of Service §7.2(b). |
| Tax collected, credited, or adjusted | Tax applied to each Installment Period, together with any credit, refund, or retroactive adjustment made under Terms of Service §7.2(c) and §7.2(d). |
Platform messages between Hosts and Guests; support tickets; cancellation dispute mediation records; and review and rating content submitted after a stay.
When you receive communications from BaseNest via Customer.io: email open and click events; unsubscribe and opt-out actions; and subscription topic preferences.
BaseNest does not collect, request, or store any of the following:
| Purpose | How your data is used |
|---|---|
| Account management | Create and maintain your account; authenticate identity; manage verification status |
| Eligibility verification | Confirm qualifying military or government status; conduct OFAC/SDN screening |
| Guest document review | BaseNest staff reviews submitted orders or LES to confirm eligibility; document deleted after review |
| Co-traveler eligibility review | BaseNest staff reviews Sponsor orders or Sponsor attestation to confirm a Named Co-Traveler is eligible |
| Host automated verification | Stripe Identity processes Host identity documents and biometric data per §5 |
| Booking & transactions | Process reservations, payments, refunds, and cancellations; apply cancellation tiers and military orders releases; generate itemized receipts |
| Communications | Transactional emails; promotional content with consent; cancellation and refund status notifications |
| Platform improvement | Analyze usage; improve features; detect and prevent fraud and abuse |
| Legal & compliance | Comply with applicable law; respond to legal process; enforce Terms; maintain required records |
| Dispute resolution | Review Platform communications, booking records, and cancellation records for Host–Guest disputes |
| Tax collection | Calculate, collect, and remit applicable lodging taxes as a marketplace facilitator |
BaseNest shares your information with the following service providers only to the extent necessary to operate the Platform. BaseNest does not sell your personal data to any third party.
| Provider | Role & Data Shared |
|---|---|
| Stripe Identity — Host verification only | Automated identity verification for Hosts only. Processes Host government ID documents and biometric face-match data. Stripe manages and stores Host verification data. Not used for Guest or Named Co-Traveler verification. |
| Stripe Payments — All users | Payment processing for all transactions. Receives payment method data. BaseNest does not store full card numbers. |
| Customer.io — All account holders | Email marketing and transactional notifications. Receives: name, email, pay grade, branch of service, duty station, verification status, and booking event data. Named Co-Traveler data is not sent to Customer.io. |
| Neon — All users | PostgreSQL database hosting (U.S.-based). Stores user accounts, profiles, booking records, cancellation records, and verification status. |
| Heroku — All users | Backend server and API hosting (U.S.-based). Processes Platform requests. |
| Vercel — All users | Web application hosting (U.S.-based). Receives standard web traffic data including IP addresses. |
| AWS S3 — Temporary and media storage | U.S.-based AWS regions. Verification and orders documents stored temporarily during staff review, then deleted. Property photos, receipts, and booking documentation stored per §8. |
| Hostaway — Participating Hosts | Channel management and property-management system integration. Receives listing, availability, booking, and stay data for properties the Host has connected. Does not receive verification documents, military orders, or payment instruments. |
| Google (Google Analytics 4 and Google Tag Manager) — All visitors | Website analytics and tag management on www.basenest.io. Receives IP address, device and browser data, page and event data, and identifiers set by analytics cookies. Not deployed on identity-verification or document-upload surfaces. |
| Meta Platforms — Website visitors | Conversion measurement and advertising audience tags on www.basenest.io. Receives page and event data and advertising identifiers. Set only with consent and subject to §7.2 and §7.4. Not deployed on identity-verification or document-upload surfaces. |
| TikTok — Website visitors | Conversion measurement and advertising audience tags on www.basenest.io. Receives page and event data and advertising identifiers. Set only with consent and subject to §7.2 and §7.4. Not deployed on identity-verification or document-upload surfaces. |
We may also share information with law enforcement pursuant to valid legal process; successors in the event of a merger or acquisition (with advance notice); and professional advisors under confidentiality obligations.
BaseNest's use of automated processing and biometric data is limited to Host identity verification only. Guest and Named Co-Traveler verification is conducted entirely by human staff review. Linked Spouse Accounts are established by Sponsor attestation and are subject to OFAC screening only.
Guest eligibility is determined by BaseNest staff reviewing submitted orders or LES documents. Named Co-Traveler eligibility is determined by BaseNest staff reviewing the Sponsor's orders or the Sponsor's attestation. Both are human decision-making processes. Linked Spouse Account eligibility is not determined by BaseNest at all: under §3.5(c) of the Terms of Service the marital relationship is established solely by the Sponsor's attestation, and BaseNest reviews no marriage certificate, DEERS record, or dependent identification card and makes no determination that any marital relationship exists. BaseNest does screen every Linked Spouse Account against the OFAC lists described in §2.2; that screening is never waived, delegated, or satisfied by a Sponsor attestation.
No automated algorithms, machine learning, or biometric processing are used for Guest or Named Co-Traveler verification. Guests, Named Co-Travelers, and Linked Spouse Account holders have no automated decision to appeal because no automated decision is made as to any of them.
Host identity is verified through Stripe Identity, which uses machine learning to: (a) verify that a submitted government ID document is authentic and unaltered; and (b) compare a live selfie to the photo on the submitted ID document (biometric face-matching). This processing involves biometric data as defined under applicable state law.
By completing Host identity verification, Hosts provide affirmative consent to the biometric processing described in §5.2. Stripe Identity processes and retains Host biometric data per Stripe's policies. BaseNest does not receive or store Host biometric data.
Florida Hosts have the right to opt out of biometric data collection during Stripe Identity verification. Texas Hosts may opt out of biometric processing under Texas law. Contact support@basenest.io to request manual verification. Opting out does not affect Guest or Named Co-Traveler verification, neither of which involves biometrics.
If Stripe Identity results in denial of Host Platform access, Hosts may request human review by contacting support@basenest.io within thirty (30) days of a denial notice. BaseNest will respond within five (5) business days.
These messages are required to operate the Platform:
Welcome series, platform tips, promotional offers, and re-engagement messages. To opt out, click the Unsubscribe link in any promotional email. Opting out does not affect transactional messages.
If BaseNest sends marketing SMS messages, we will obtain your prior express written consent as required by the TCPA, 47 U.S.C. §227. Revoke consent at any time by replying STOP. Message and data rates may apply.
All promotional emails include BaseNest's physical mailing address, clear identification as a BaseNest communication, and a working unsubscribe mechanism. Unsubscribe requests are honored within ten (10) business days.
Named Co-Travelers are not enrolled in any BaseNest marketing communication. BaseNest does not collect co-traveler contact information and does not market to them.
| Category | Description |
|---|---|
| Strictly Necessary | Required for Platform function. Cannot be disabled. Includes authentication tokens, CSRF protection, and load balancing. |
| Functional | Remember preferences such as language and saved searches. Can be disabled; disabling may affect Platform functionality. |
| Analytics | Measure usage patterns to improve performance. Data is aggregated and anonymized where possible. |
| Advertising & Measurement | Set only with your consent. BaseNest deploys conversion-measurement and advertising audience tags supplied by Google, Meta Platforms, and TikTok on www.basenest.io. Those platforms are identified in §4. These tags are not deployed on identity-verification or document-upload surfaces, and no verification status, document content, or military eligibility data is transmitted to them. They are subject to your consent, to the Global Privacy Control opt-out in §7.2, and to the opt-out in §7.4. |
BaseNest honors GPC signals as a valid opt-out of data sale and sharing under applicable state privacy laws including CCPA/CPRA. If your browser sends a GPC signal, we process it as an opt-out of non-essential data sharing and provide confirmation.
You can manage cookie preferences through your browser settings. Disabling strictly necessary cookies will prevent login and Platform use.
BaseNest does not sell personal data for money. Because BaseNest deploys advertising and conversion-measurement tags supplied by third-party platforms as described in §7.1, some disclosures of device and usage data to those platforms may constitute "sharing" for cross-context behavioral advertising under the California Consumer Privacy Act, and "targeted advertising" under the comprehensive privacy statutes of other states.
You may opt out of that sharing by any of the following routes, each of which BaseNest treats as a valid opt-out: declining the Advertising & Measurement category in the Platform cookie banner; transmitting a Global Privacy Control signal, which BaseNest honors under §7.2; or emailing privacy@basenest.io with the subject line "Do Not Sell or Share." BaseNest does not require an account to exercise this right and does not condition access to the Platform on your choice.
BaseNest does not sell or share the personal data of any individual it knows to be under sixteen (16) years of age. Verification documents, military orders, eligibility data, and Named Co-Traveler data are never sold, shared, or disclosed to any advertising or measurement platform.
| Data Type | Retention Period |
|---|---|
| Guest verification documents (PCS / TDY orders, LES) | Deleted permanently from AWS S3 upon completion of staff review. Not retained after verification is complete. |
| Host verification data | Processed and retained by Stripe Identity per Stripe's policies. Not stored by BaseNest. |
| Extracted verification fields (name, pay grade, branch, status) | Life of account, plus 3 years following account closure |
| Booking & transaction records (receipts, amounts, dates, properties, cancellation tier, fees assessed) | Minimum 7 years from transaction date, per federal recordkeeping requirements applicable to government travel documentation |
| Named Co-Traveler name and relationship | Retained as part of the booking record — minimum 7 years from transaction date |
| Sponsor attestation records | Retained as part of the booking record — minimum 7 years from transaction date |
| Military orders submitted for SCRA / cancellation processing | Deleted from AWS S3 upon completion of processing. Confirmation record (orders received, date, cancellation tier applied, outcome) retained 7 years as part of the transaction record. |
| Cancellation dispute mediation records | 3 years from resolution date |
| Account profile data | Life of account, plus 3 years following account closure or last Platform activity |
| Platform messages (Host–Guest communications) | Life of account, plus 2 years; longer if subject to active dispute or legal hold |
| OFAC screening logs | Minimum 5 years per Bank Secrecy Act requirements |
| Marketing preferences & consent records | Life of account, plus 3 years |
| Device & usage / analytics data | 24 months from collection, unless retained in aggregated or anonymized form |
| Support tickets & dispute records | 3 years from resolution date |
| Linked Spouse Account records (name, email, credential, link status) | Life of the Linked Spouse Account, plus 3 years following closure or termination of the Sponsor account from which it derives |
| Sponsor attestation establishing a Linked Spouse Account link | Life of account, plus 3 years — retained as the basis on which derivative access was granted |
| Proposed Bookings submitted from a Linked Spouse Account | 24 months from submission where never confirmed; where confirmed, retained as part of the booking record |
| Extended Stay installment schedules and installment payment records | Minimum 7 years from transaction date, as part of the booking and transaction record |
| Extended Stay early-termination notices and Notice Period calculations | Minimum 7 years from transaction date, as part of the booking and transaction record |
| Duration declarations retained for lodging tax exemption purposes | Minimum 7 years from transaction date, per applicable state tax recordkeeping requirements |
| Alabama annual accommodations report submissions (property addresses) | Minimum 7 years from submission, per Ala. Code § 40-26-1.1(g) |
| Continuation Confirmation records (confirming party, date and time, Installment Period) | Minimum 7 years from transaction date, as part of the booking and transaction record |
| Installment pause requests and orders-verification outcomes | Minimum 7 years from transaction date, as part of the booking and transaction record. The underlying orders document is deleted on completion of processing. |
| Tax collected, credited, or retroactively adjusted, per Installment Period | Minimum 7 years from transaction date, per applicable state tax recordkeeping requirements |
| Advertising and measurement consent and opt-out records (including GPC and §7.4 requests) | Life of account, plus 3 years; where no account exists, 3 years from the date the choice was recorded |
In the event of a security incident involving your personal data, BaseNest will contain and investigate the incident, notify affected users and applicable regulatory authorities within the timeframes required by applicable law, and provide details of the incident and remediation steps. To report a suspected security vulnerability, contact support@basenest.io.
Regardless of your state of residence, BaseNest honors the following rights. These rights are available to Guests, Hosts, and Named Co-Travelers alike.
| Right | Description |
|---|---|
| Right to Know / Access | Request a copy of the personal data we hold about you |
| Right to Correct | Request correction of inaccurate or incomplete data |
| Right to Delete | Request deletion, subject to legal retention obligations (see §12.4) |
| Right to Portability | Request a machine-readable copy of your personal data |
| Right to Opt Out of Data Sale | BaseNest does not sell personal data. GPC signals honored. |
| Right to Limit Use of Sensitive Personal Information | Direct BaseNest to limit use of sensitive personal information — including pay grade, branch of service, and duty station — to what is necessary to provide the Platform. Submit under §12. |
| Right to Opt Out of Automated Decisions | Applies to Hosts only (Stripe Identity). Guests and Named Co-Travelers are verified by human review; there is no automated decision to appeal. |
| Right to Non-Discrimination | Exercising any privacy right will not result in denial of service or different pricing |
To exercise these rights, submit a request as described in §12.
Right to confirm data processing, access personal data, correct inaccuracies, and obtain a portable copy
Access, correction, deletion, and portability rights consistent with §10
BaseNest is organised in Georgia and operates in Georgia, Missouri, and Arkansas, none of which had a comprehensive consumer privacy statute in force as at the effective date of this Policy. Residents of those states, and of any other state without such a statute, may exercise the access, correction, deletion, and portability rights described in §10, and the advertising opt-out in §7.4, on the same terms BaseNest extends to residents of every state. BaseNest does not condition the availability of those rights on the existence of a statute requiring them.
Where a state enacts a comprehensive privacy statute after the effective date of this Policy, BaseNest will apply that statute's requirements from its effective date and will update this §11 at the next revision.
HOW TO SUBMIT: Email privacy@basenest.io with the subject line "Privacy Request." Include your full name, the email address on your account, and a description of the right or rights you wish to exercise. Requests sent to support@basenest.io will be routed to the same queue.
Before processing a request, BaseNest will verify your identity. We may request confirmation of the email address on your account and one additional verification factor.
| Timeline | Period |
|---|---|
| Standard response | 45 days from receipt of a verified request |
| Extension (if needed) | Additional 45 days with written notice before the initial deadline |
| Florida FDBR | 45 days; one 15-day extension permitted with notice |
| Denial notice | Reason provided within 45 days if the request cannot be fulfilled |
If your request is denied, appeal to privacy@basenest.io with the subject line "Privacy Appeal" within thirty (30) days of the denial. BaseNest responds within sixty (60) days. If the appeal is denied, you may contact your state Attorney General's office where applicable law provides this right.
A Named Co-Traveler, or any other individual whose personal information appears in BaseNest records without holding an account, may exercise the rights in §10.
Because such an individual has no account email to verify against, BaseNest will verify identity using the booking reference number, the name as recorded on the booking, and one additional verification factor. BaseNest may contact the Sponsoring account holder to confirm the request before acting on it.
Submit these requests to privacy@basenest.io with the subject line "Privacy Request — Non-Account Holder." The response timelines in §12.2 apply. The deletion limitations in §12.4 apply equally, which means a Named Co-Traveler's name recorded on a booking record cannot be deleted before the 7-year retention period expires.
BaseNest screens all account holders against the OFAC SDN List and other restricted-party lists at account creation and on subsequent transactions. Screening records (the fact of screening and the outcome) are retained for a minimum of 5 years per Bank Secrecy Act requirements. OFAC screening results are not shared with other users. Accounts flagged may be denied, suspended, or terminated without advance disclosure of the specific flag.
The Platform is intended solely for users eighteen (18) years of age or older. BaseNest does not knowingly collect personal information from persons under 18. A Named Co-Traveler must also be 18 or older; BaseNest does not collect the names or ages of dependent children traveling with a Sponsor.
If we become aware that a minor's data has been collected, we will delete it promptly. Contact support@basenest.io with the subject line "Minor Data Concern" if you believe a minor's data has been submitted.
Note on COPPA:the Children's Online Privacy Protection Act applies to children under 13. Because the Platform is restricted to adults, COPPA is not the operative framework here. This section states BaseNest's age restriction and minor-data handling directly rather than relying on a COPPA citation.
All BaseNest infrastructure is hosted in the United States. No personal data is intentionally transferred outside the United States.
| Service | Location |
|---|---|
| Neon (database) | U.S.-based PostgreSQL hosting |
| Heroku (backend server) | U.S.-based |
| Vercel (web hosting) | U.S.-based CDN and compute |
| AWS S3 (file storage) | U.S.-based AWS regions |
| Stripe / Stripe Identity | U.S.-based; see Stripe's privacy policy for data center details |
| Customer.io | U.S.-based email infrastructure |
OCONUS service members who access the Platform while stationed abroad should be aware that data submitted to the Platform will be processed and stored in U.S.-based infrastructure.
BaseNest is a private entity and does not represent the DoD, VA, or any federal agency. Verification of military status does not imply a security clearance check or DoD affiliation. BaseNest cannot guarantee DTS voucher approval or reimbursement of any lodging expense. Receipts are provided in a format intended to support voucher submission but do not guarantee approval.
Entitlements and reimbursement rates vary by orders, location, rank, and dependents. Verify entitlements and reimbursement eligibility with your finance or travel office.
BaseNest may update this Privacy Policy at any time. When material changes are made, we will post the updated Policy with a new effective date and send email notification to registered users at least thirty (30) days before changes take effect where required by applicable law. Continued use of the Platform after the effective date constitutes acceptance.
| Field | Detail |
|---|---|
| Entity | BaseNest LLC |
| Mailing address | 113 S. Perry Street, Suite 206, Lawrenceville, GA 30046 |
| Privacy requests | privacy@basenest.io (subject: Privacy Request) |
| General support | support@basenest.io |
| Legal notices | legal@basenest.io |
| Phone | 904-206-7553 |
| Website | www.basenest.io |
BaseNest LLC | www.basenest.io | support@basenest.io | 904-206-7553
Veteran-Owned & Minority-Owned Business