Go withAmanaأمانة

Privacy policy

Last updated 16 October 2026

Who we are and what this policy covers

Go with Amana is operated by Amana LLC, an Illinois limited liability company in the United States (Illinois file number 18815362). Our principal business address is 5921 W Dakin, Chicago, IL 60634, United States. This policy covers gowithamana.com, the Go with Amana application and the planning, account and reservation services we operate. Email hello@gowithamana.com, or Gowithamanasupport@gmail.com. Telephone: +1 (773) 732-8390.

Customer accounts and linked trips

Account notice version: 15 October 2026. We collect your name, email address, securely hashed password, adult eligibility declaration and the versions and timestamps of your account terms acceptance and privacy acknowledgment. We store hashed session and verification/reset tokens, rather than readable passwords. We use these records for authentication, account security, linking your enquiries and itineraries and providing requested support.

Verification links expire after 24 hours, password reset links after 30 minutes and sign-in sessions after up to seven days. Expired account tokens, sessions and abuse-prevention records are cleaned up on account-service activity. Account creation does not authorize payment or subscribe you to marketing.

Planner, reservation and support information

We collect the planner answers you submit, such as traveler numbers, departure city, dates or season, trip length, interests, pace and accommodation preferences. When you ask us to send a plan, we collect your first name and email address, and a phone number if you choose to give one. We keep these with your enquiry, itinerary versions, displayed estimate and subsequent correspondence.

For a booking, we request only details needed for the selected services: traveler names, dates, occupancy and room requirements, pickup details, relevant contact information and reservation references. Dates of birth, identity-document details, emergency contacts or dietary/accessibility requirements are requested only where needed for a particular service. Do not put passports, card details, passwords or sensitive health information into account signup or general planner free text. We explain a suitable channel if additional information is needed.

We keep booking communications, confirmations, payments and refund status, accepted conditions, change/cancellation requests and support records. If you provide another traveler's information, make sure you have authority to do so and tell them about this policy. Special requirements may reveal health or religious information; share only what you want us to use to arrange the requested service, and we obtain any additional permission required by applicable law.

Payments and technical information

Payments made through Stripe-hosted links are processed by Stripe under its privacy policy. We may receive payment confirmation, transaction references, amount, currency, billing/contact details and refund or dispute status. Our account and planner forms do not collect or store full card numbers, card security codes or bank login credentials. Your bank or payment provider may retain its own transaction records.

Our servers and hosting services process connection and security information, such as IP address, request time, requested URL and browser information, to deliver and protect the service. Account abuse prevention uses temporary keyed records. Optional audience measurement is described below. The former per-visit planner endpoint no longer stores new visit identifiers. Historical per-visit planner records expire after 90 days. The current site and app do not include a third-party advertising or analytics SDK.

Why we use information

Where data-protection law requires a legal basis, the basis depends on the purpose and jurisdiction: steps requested before a contract, performing a contract, legal obligations, legitimate interests in secure operation where available, or consent where required. We do not treat account acceptance as blanket consent to every use or an international transfer.

Recipients and service providers

We share only the booking information a selected hotel, riad, driver, guide, activity operator or restaurant needs to quote, confirm or deliver the service. Reservations may be handled by supplier email, an agent platform, a channel manager or supported API. Supplier tools may include platforms such as HotelRunner, SynXis or Bookinglayer where the selected supplier uses them. We do not send every customer's details to every prospect in our partner network.

Our service providers include Render for the configured website hosting and database deployment; Resend and configured SMTP email services, including Google/Gmail, for delivery and correspondence; Stripe for hosted payments; and WhatsApp when you choose that communication channel. Website fonts are served from Amana’s own host, rather than fetched from Google Fonts when you visit. These providers' own notices also apply to their services.

When enabled, supplier research tools use Anthropic's Claude API to research proposed destinations, properties and rates. These tools assist staff and do not confirm reservations. The research requests use trip-planning criteria and supplier information; account passwords and payment credentials are not required for this purpose. We review outputs before relying on them for a booking.

Authorized staff and advisers may access records needed for operations, accounting, dispute resolution or legal obligations. We may disclose information where required by law or needed to protect rights and security. We do not sell personal information or share it for third-party targeted advertising.

The application and your device

The Go with Amana app opens planning, account and itinerary pages from our website and uses the same server-side account records. A phone and a desktop can have separate sign-in sessions. The app stores session cookies in its embedded browser; the native navigation receives limited signed-in profile information so it can display account status. Public destination summaries are bundled for offline use; they are not a downloaded copy of your customer trip records.

If you choose to export your account data in the native app, it creates a temporary JSON file in app-private cache and opens the device's share sheet. The app attempts to delete that temporary file when sharing finishes. Copies you save or share, and copies retained by a receiving app or backup, remain under your control and that service's policies. A crash can leave a temporary cache copy until the app or operating system clears it. Use care when exporting on shared devices.

The current app does not request camera, microphone, precise location, contacts or photo-library access for its features, or register a remote push-notification token for daily discovery. In app versions with Discover, reminders are scheduled locally by the phone only after you enable them and grant the required notification permission. Reading history and streaks are stored on the device, independently of your travel account; clearing app/browser data removes them. Privacy choices in the app let you clear this history, and Discover lets you turn reminders off. It does not create a separate native password store. External links may open another app or website, which then handles your information under its own notice. Unsent form input can be lost after a reload or connection failure.

International processing

Amana operates through its United States company, our team and providers may process information in other countries, and Morocco suppliers receive the details needed for your trip. Those countries may have different protections. Where applicable law requires transfer safeguards or additional permission, we must put them in place before the relevant transfer. Accepting these terms does not waive those requirements. Contact us for information about the recipients and safeguards relevant to your booking.

Retention and security

We keep information for the purpose it was collected: handling an enquiry, providing an active account or booking, completing payments and refunds, resolving disputes and meeting applicable tax, accounting, fraud-prevention and legal requirements. The period depends on the record, whether the matter is active and the obligations that apply. We do not promise automatic deletion after a fixed period that is not yet implemented. Contact us to request a review or the retention information relevant to your records.

We use access controls, password hashing, expiring tokens and protected connections for account operations. No service can guarantee absolute security. Backups may retain copies until rotated, and a justified legal hold can delay deletion. We restrict retained records to the relevant purpose and explain applicable retention exceptions when handling your request.

Account deletion and personal-data requests

In the website or app, open My account, then account settings, to download account data, submit a privacy request, sign out all devices or delete your account after confirming your password. You can also request deletion of your Go with Amana account and associated data without using the app by emailing hello@gowithamana.com or Gowithamanasupport@gmail.com. Include the account email and request type; do not send a password or identity document. We may ask for proportionate verification.

The self-service account deletion removes the profile, login credentials, sessions, tokens and links between the account and trips. It does not cancel travel or automatically delete separately held enquiry, supplier, accounting or dispute records. To request those records' deletion, use the privacy-request option or email us. We assess deletion of associated data and explain any specific legal or other applicable exception and how long retention is needed. An account download contains account data and linked enquiry/trip information available to that tool; contact us for other business records.

Depending on applicable law, you may have rights of access, correction, deletion, portability, restriction, objection, appeal or withdrawal of consent. We acknowledge and respond within the deadlines that apply, explain any permitted extension or refusal, and provide an appeal route where required. We do not require a paid booking to exercise privacy rights. Privacy-request records and your verified contact information are kept separately while we handle the request and any required recordkeeping. Where available, you may also complain to the relevant regulator.

Service messages and marketing

We use your email for account security and the trip enquiry or booking you requested. Account creation and trip enquiries do not subscribe you to newsletters or unrelated marketing. A separate marketing subscription, if offered, is optional and includes an unsubscribe option. Tell us if you no longer want follow-up about an unbooked enquiry; necessary account, booking, legal and security messages may still be needed.

We use your phone number to discuss your requested trip and use WhatsApp if you ask for that channel. We do not use it for marketing. A selected supplier may receive it where necessary for pickup, check-in or delivery of your booking; we do not promise it will be shared only with drivers or guides.

Cookies

Essential account cookies support sign-in (up to seven days) and form security (one hour). Signing out clears the current sign-in cookie; account settings also allow all-device sign-out. The app's embedded browser uses these same essential cookies. We do not currently set advertising cookies. A local privacy preference records only your accepted/rejected choice, notice version and selection time, for up to 180 days, without a unique identifier. You can reopen Privacy choices to change it. Rejecting optional statistics does not disable essential account security or requested services.

Optional statistics on the website and app

Optional measurement starts only after you choose Allow statistics. Reject statistics is offered alongside it. You may change or withdraw that choice using Privacy choices on the website, or Privacy choices in the app. Browser Global Privacy Control and Do Not Track signals keep optional measurement off even if a stored choice says allow. Choices apply to that browser or app installation, rather than every device on your account.

With permission, the website and app send page/screen categories, broad actions such as reaching a planner step or pressing story completion, and short foreground-active time increments. Website acquisition sources are reduced on the device to categories such as direct, search, social, email, partner or paid. We do not send raw referrer URLs, campaign text, form values, account or trip identifiers, advertising IDs, reading-history IDs or precise location in audience events. We do not use a visitor or session identifier. Network requests necessarily pass connection information through our hosting infrastructure; this is separate from the audience counters.

Audience events are combined into daily counters without a raw-event table, using UTC dates, platform, page/action category and fixed planner-step and destination/content vocabularies. Destination counters describe content interest, not a person’s travel history. Daily totals expire after 400 days. The preference expires after 180 days without being renewed by ordinary visits. We use aggregate trends to improve the product and inform broad business planning and potential partnerships. They are not individual advertising profiles, unique-person counts, tracked customer journeys or retargeting lists. Exports for possible sharing omit technical traffic and suppress counts below five occurrences; we still review them before disclosure and do not join them to customer records.

Declining or withdrawing prevents subsequent optional events. Existing aggregate totals cannot identify your contributions for individual extraction or removal. Essential security and service operation continue: separate technical counters record daily HTTP status totals without paths or identities, and hosting providers may keep their own restricted logs under their service configuration. Backups can contain previous copies until their normal rotation; restoring a copy requires reapplying retention cleanup.

Legal grounds where applicable

Where the GDPR applies, we use information needed to take requested steps before a contract and perform agreed travel services; applicable legal obligations for required business records; and legitimate interests in proportionate service security, abuse prevention and support, subject to the required balancing and objection rights. Optional audience measurement uses your consent and is not required to book, create an account or read a story. If a particular use requires additional permission, we obtain it before that use. You may withdraw consent without affecting the lawfulness of processing before withdrawal.

Children

Accounts are for people aged 18 or older who are legally able to accept the account terms. The age screen records an adult declaration rather than a birth date or identity document; it is not identity verification. Children may travel with an authorized adult who supplies necessary booking details. We do not knowingly invite children to submit personal information directly through accounts or the planner. If you believe this happened, contact us so we can investigate and take appropriate action.

Changes and contact

We update the date on this page when the policy changes and communicate material changes through an appropriate account or contact channel. We obtain additional permission where required. Email hello@gowithamana.com, or Gowithamanasupport@gmail.com. Telephone: +1 (773) 732-8390.