Effective date: October 22, 2026
Rucks helps you organize your travel history, remember places and preferences, discover ideas, and share selected information. This Privacy Policy explains what information we handle, why we handle it, who can receive it, and the choices available to you. It covers the Rucks websites, apps, and related services, including Rucks connections to other services and assistants.
We do not sell your personal information or use your private travel memory for targeted advertising. We do not use your private content to train general-purpose AI models, and we do not permit our AI service providers to do so. Connecting an account, granting a device permission, accepting a friendship, and sharing particular information are separate choices. Our use of Google data is also subject to the specific restrictions in section 8.
OTB Capital, LLC, a California limited liability company doing business as Rucks AI, operates Rucks and is responsible for the personal information described in this policy. References to “Rucks,” “we,” “us,” and “our” mean that company. Our address is 1117 State Street, Santa Barbara, California 93101, United States. Contact privacy@rucks.ai with privacy questions or requests, including if you do not have a Rucks account.
This policy covers processing by Rucks. A travel supplier, social network, app store, or independent assistant you choose to use may also process information under its own policy. Authorizing a Rucks connection does not give that service unrestricted access to your Rucks account.
Account and communications. We collect information you provide when creating or managing an account, such as your name, email address, profile information, sign-in identifiers, settings, and communications with us. We record notices and permissions presented to you, your choices, and the information needed to document them: the time and the version of the document or wording you saw and, when you accept our Terms and this policy, your IP address and your app’s or browser’s user-agent string. If you purchase a paid feature, we receive subscription, transaction, and entitlement information; payment details are handled by the checkout provider or app store identified at purchase.
Your travel memory and content. We collect the information you type, speak, upload, save, or otherwise submit: travel dates, destinations, itineraries, booking details, loyalty or membership information, places, Favorites, wishlists, plans, notes, reactions, photographs you choose to upload, questions, answers, corrections, and conversations. We also create derived information, such as summaries, searchable representations, possible travel patterns, and preferences, to provide your Rucks experience. A searchable representation can still be personal information; converting text into a vector does not make it anonymous.
Optional email and calendar connections. When you authorize a supported connection, we receive access tokens and the information needed for that connection. Our current email and calendar connections are read-only: they do not authorize Rucks to send, modify, or delete your emails or calendar entries. We use travel-related searches and filters to identify relevant records. Matching email information can include sender details, subject, message body, date, and identifiers; calendar information can include event title, dates, location, description, and identifiers. Current email import does not download attachments, and current calendar import does not store attendee lists. Travel details or names appearing within a message body or event description may nevertheless be processed.
Filters can make mistakes. A matched record can contain information unrelated to travel, including information about another person. For emails that match our travel filter, we store the subject, text body, sender and recipient addresses, and date alongside the details we extract, so we can reconcile, explain, correct, or reprocess your travel history. We keep them until you disconnect that account or delete your Rucks account. Because an AI model extracts the travel details, email and calendar import runs only while you allow AI processing (section 7). You can review your memory, correct mistakes, and disconnect a source. Section 9 explains the difference between stopping future access and deleting information already imported.
Your private people roster. You can record people you travel with or visit, including their names, their relationship to you, short notes, name variants you confirm, and spellings you said are not them. Removing an entry takes it off your roster; it is erased when you delete your account, or sooner if you ask privacy@rucks.ai. Travel records can also contain companion names. We use this information to organize your own history, for example to distinguish a family trip from other travel. Adding a roster entry does not create an account for that person, send them an invitation, make them a connected Friend, or grant them access to your information. A suggested name match may be presented for your confirmation; a private roster entry is not verification of a person's identity.
Friends and recommendations. When you use sharing features, we process the information needed to connect accounts and deliver your chosen content, such as invitations, relationship status, sender and recipient identifiers, names used for attribution, shared places or lists, recommendations, notes, and acceptance or other delivery events. A friend can be a source of information about you. Keeping a friend's list or recommendation can store the friend's name and their recommendation separately from your own note or opinion. It does not, by itself, mean you personally Like or Love the place.
Travel Profile and sensitive information. Optional Travel Profile fields can include dietary requirements, allergies, blood type, medical notes, health insurance information, travel insurance information, and other preferences you enter. Some of this information is legally sensitive. These fields are for information you choose to supply; they are not intended to be populated by inferring medical facts from connected accounts. You can leave them blank and use the other parts of Rucks. Rucks keeps the health details among them (dietary requirements, allergies, blood type, medical notes, and health insurance) only after you give a separate permission in the app, which we record with the version of its wording, and puts them on a share link only after you confirm those details for that link. Rucks never sends these details to an AI provider and never uses them to build your memory. Declining blocks nothing else. Our Consumer Health Data Privacy Notice provides additional details and rights for health information. Please do not put another person's medical information in your roster or ordinary notes.
Location. With device permission, we receive your foreground location, which may include precise latitude and longitude, to answer requests such as “near me” or show nearby places. We may also receive a city, country, and local time with the request. We do not use this permission for continuous background location tracking. Foreground location is used as request context, rather than added automatically to your travel history. Separately, locations you save or import with trips, places, or photos can become part of your stored memory. You can deny location permission and enter a destination yourself. Maps in the app are provided by Mapbox, which receives requests for the map area being shown and technical information such as your IP address and device details. The app asks the Mapbox software not to send its optional usage data, and keeps Mapbox’s attribution, which carries Mapbox’s own setting for that data. Search and location services may receive the query, relevant location, and technical information needed to respond.
Photo import and uploaded photos. If you authorize travel-history reconstruction from your photo library, the app reads photo date and location metadata and sends sampled coordinates and dates to Rucks. We store those points and use them to identify places and periods of travel. The import reduces duplicate points; it does not necessarily round each transmitted coordinate to a city or broad area. This metadata import does not upload the image files, filenames, or device asset identifiers. Separately, when you choose a photo as the cover for a saved place, the selected image is uploaded and stored. It is not displayed to other users or through shared lists. Revoking photo-library permission stops future device access but does not itself remove information already imported.
Voice. With microphone permission, Rucks can process your speech to answer you. In the cloud voice feature, audio is sent to OpenAI for speech processing and responses, and relevant Rucks context and tool results are supplied to the voice session. Where a device-based speech feature is offered, processing also depends on the device's speech service and settings. Transcripts, answers, and information you ask Rucks to remember can be stored in your account. Rucks does not maintain a library of raw recordings from the current cloud voice feature. The provider may have separate operational retention, as explained in section 7. Voice is not used by Rucks to identify you through a voiceprint.
Language and diagnostic information. We receive your chosen response language, app locale, and device language preferences. We keep a record of how an answer's language was selected, including language codes, detection confidence, the rule used, whether a mismatch occurred, whether the answer was regenerated, and associated account, conversation, feature, and app-version identifiers. This language-decision record does not contain the words you said or typed, or an audio recording. It is still linked to your account. Your separate conversation history can contain the actual words. We use these records to provide the requested language and diagnose errors, not to create an ethnic or nationality profile.
Technical and usage information. We process IP addresses, device and browser information, app versions, sign-in and security events, errors, performance information, and interactions needed to operate and improve Rucks. First-party product records can include which feature was used and whether an action succeeded. We use cookies or similar storage for functions such as authentication, security, and remembering settings. We do not operate an advertising-tracking program or use your Rucks memory to build advertising audiences. External sites you open have their own tracking practices.
Notifications and email. If you enable push notifications, we process a device push token and send notification information through delivery providers, such as Expo and Apple. A notification may include a name, a place or list title, the sender’s note (up to 280 characters), and the record identifiers needed to open the relevant content. It never includes your Travel Profile. Your device may display this on its lock screen. You can adjust notifications and preview settings. We also send account, security, service, and legally required messages. Promotional messages require the choices applicable to your location and include a way to unsubscribe. Joining a launch waitlist is not permission for unrelated marketing.
We use information to create and secure accounts; import and organize authorized travel information; answer questions; personalize suggestions; distinguish your own opinions from other people's recommendations; manage plans and sharing; deliver notifications; provide support; investigate errors and abuse; maintain the service; and meet legal obligations. Product improvement means improving how Rucks works, not a license to repurpose private content for general AI training or advertising.
Where a legal basis is required, we use the following bases according to the particular activity. Processing needed to provide the core service you request is based on performing our contract with you. Optional connections, permissions, and uses requiring consent are based on your choice and, where legally required, your consent. We rely on legitimate interests for proportionate security, abuse prevention, service diagnostics, support, and handling limited information about other people within a traveler's private records, subject to their rights and reasonable expectations. We use information where necessary to comply with law or establish, exercise, or defend legal claims. Health and other special-category data require an additional legal condition, such as your explicit consent; ordinary acceptance of this policy does not provide that consent.
Providing account information is necessary to operate your account. Optional information is not required to use unrelated features, although a feature cannot work without the information it needs. You may withdraw consent for future processing without affecting processing that was lawful before withdrawal. We do not silently substitute another basis to continue a consent-dependent optional use after you withdraw it.
Rucks combines information you supply, authorized imports, your explicit choices, and selected recommendations to make your memory useful. It may infer preferences or group trips by purpose. Those inferences can be wrong. A booking is not proof that you traveled; saving a place is not proof that you visited or endorsed it; and a friend's recommendation is not your own statement.
You can use the available review, correction, and removal controls, or contact us, to challenge inaccurate information. Changes may require related summaries or search indexes to be updated. We use personalization to assist with travel, not to make decisions about credit, employment, insurance eligibility, or other decisions with legal or similarly significant effects. We do not infer medical diagnoses, religion, ethnicity, or sexual orientation for recommendation profiling. If you mention one of these in a question, Rucks uses it to answer that question; it does not save it to your memory on its own or put it in anything you share. Rucks’s memory is instructed not to learn such beliefs, a belief in these categories that Rucks would save on its own is refused, and any such belief, including one you write yourself, is left out of what you share. These controls rely on word lists and model instructions: they reduce what is kept and shared but cannot guarantee to catch every mention. Sensitive information you deliberately provide remains subject to its specific purpose and permissions.
Sharing is scoped. Your private memory is not made public merely because you join Rucks or accept a friendship. Other people can see information you choose to share through the particular feature, together with attribution and technical details needed to provide that share. Check the recipient, content, and permission shown before sharing. A list, plan, or profile field can have different sharing rules; sharing one does not grant access to your entire account.
Your profile and your Lists. Anyone signed in to Rucks who opens your profile sees your name. People on Rucks can find you by your name in Find people unless you turn off Find me by name in Settings. Finding you shows them your name, your profile photo while it is set to Everyone on Rucks, and where you are based while that is set to Everyone on Rucks. Search results never show your email address, your Lists, places or plans, or who you are connected with. Someone you blocked never finds you, and the people you are connected with can find you either way. If you turned this off before, it stays off. Your people are the friends you connected with on Rucks, your approved followers, and the people you follow. Your profile photo is seen by the audience you choose: Everyone on Rucks (people signed in to Rucks, not anyone without an account), My people, or Only me. A first photo is set to Everyone on Rucks unless you chose otherwise first; a photo you added before October 15, 2026 keeps its audience, which is Only me unless you chose another; and a new photo keeps the audience of the one it replaces. Your Lists are for your approved followers, including the friends you connected with before following existed, and for anyone you send a List to or approve, unless you make a List Secret, which keeps it to you and the people you choose. A List you kept to yourself before stays that way. Followers see a List’s places and the tips you chose to share on it, never your private notes or the places you keep Secret. Following works one way: someone who follows you sees your Lists, and you see theirs only if you follow them and they approve. If you ask to follow someone and they approve, they can follow you back without asking you again: your request counts as your approval. This includes a request you sent before this version of the policy, once you accept it; to take a request back, withdraw it or unfollow. Pending requests, and follows that ended or were blocked, open nothing. Nobody who is not signed in sees your Lists, and a forwarded link to a List opens nothing until you approve the person who asks. Where you are based, if you add it, is shown to anyone signed in to Rucks who opens your profile, unless you keep it to your people or hide it. A Based in you added when it could only be shown to your people stays that way until you choose. It is never a precise location.
Links and connected recipients. Some shares use a link rather than requiring the viewer to sign in as a named recipient. Anyone who obtains such a link may be able to view its contents while it is valid. A recipient label does not itself prove who opened the link. Sharing can also use a connection between accounts. Access records, where available, describe system access events; they do not prove that a particular human read or understood the information.
Recommendations and kept lists. When someone keeps content you shared, their account can retain a copy and source attribution. Following a list can instead provide continuing access to its current shared content. Renaming or organizing a kept list does not turn the original author's words into the recipient's words. A recipient's own notes and opinions are separate. Removing a friendship or revoking a live link stops the access controlled by that permission; it does not automatically erase every copy the recipient previously kept or every independent record they created. You can reset a list’s link: the old link then stops working for everyone who has it, including people who follow the list through it and friends you sent it to, and your list stays. Leaving a friendship ends the places, lists, plans, and invitations the two of you sent each other directly. A list’s or plan’s own link is not ended for everyone when one friendship ends, because other people may hold it; reset or stop that link to end it. Ending access stops future viewing; it cannot take back what someone already saw or copied.
Secret places. Marking a place Secret withholds your contribution about that place from Rucks sharing surfaces governed by that setting, including your live shared lists and recommendation attribution. It also prevents new copies through those surfaces while the setting applies. It does not delete someone else's independent place record or retract information already seen, copied, downloaded, screenshotted, or exported. Secret does not mean that Rucks and its service providers cannot process the place to provide your private experience. Turning Secret off can make the place visible again through permissions that remain active; a revoked link is not automatically reinstated.
Family access. A family relationship in your private roster does not authorize access. Any account-linked family sharing requires the relevant grant. Sharing can be directional and limited by data category. A grant to see trips is not automatically a grant to see your private notes, reactions, Secret places, or health fields.
Assistants and other integrations. If you authorize an external assistant or application to access Rucks, we disclose information within the permissions you approve. These can include selected travel facts or preferences and, where separately allowed, loyalty membership information. The current assistant connection does not expose Travel Profile medical fields. Review the requesting application's identity and permissions: its name or logo is not a Rucks endorsement. Revocation prevents further authorized access through Rucks but cannot remove information already retained by the independent application. Its own terms and privacy policy apply to that copy.
Sensitive and third-party information. A recommendation note can mention someone other than its author. Share only information you have a lawful basis to disclose. Health information and other sensitive fields require their specific sharing choice; a general Friends connection is not that choice. Contact us if content about you is inaccurate, unlawfully shared, or should be restricted or removed. We assess those requests under applicable law, including obligations concerning copies held by others.
We provide relevant information to service providers that help with hosting, storage, backups, security, authentication, email and notification delivery, support, maps, search, AI processing, and, if applicable, payments. They receive information appropriate to their function and must handle it under the applicable contractual and legal restrictions. They do not receive a general right to exploit your private memory for their own advertising or model training. For example, maps in the app are drawn by Mapbox (section 2), and the web chat on rucks.ai can send your question to Tavily, a web search service (section 7). For a flight you choose to follow, its number and dates are sent to FlightAware to get its status. Place searches, and for “near me” an approximate location, are sent from our servers to Google Places, which handles them under Google’s own terms as an independent recipient, not as our service provider; it never receives your name, your account or your IP address. Section 7 explains AI processing in more detail.
An external travel, ticketing, or booking site you choose to open receives the information involved in that interaction under its own practices. We do not give travel suppliers your entire memory merely because they appear in results. A request to transmit selected information to a supplier is a separate action. If a link involves a referral commission or other material commercial relationship, we disclose that relationship where relevant; this does not authorize the transfer of your private memory for advertising.
We may disclose limited information when reasonably necessary to comply with a lawful obligation, respond to valid legal process, protect rights or safety, investigate fraud or security incidents, or establish or defend a legal claim, subject to applicable law. We may also disclose information in a corporate transaction under appropriate safeguards and notice. Google-derived information remains subject to section 8, including explicit prior consent where required for a merger, acquisition, or asset sale. Health information remains subject to its additional restrictions. A corporate transaction does not cancel the commitments applicable to information already collected.
Rucks uses AI to extract travel details, summarize memory, retrieve relevant information, interpret requests, and generate answers. Rucks does this only with your AI permission (below), except two city lookups described below: what's on in a city and a city page's history. Every AI request, voice included, goes directly to OpenAI, with no other company in between and no fallback to another provider. Tavily runs web searches: the web chat on rucks.ai can send it your question, and to find what's on in a city Rucks sends it two searches made of the city, its country and the dates (events that week, and any national election that month), without your name, your account or your words. The current list of AI providers is always at rucks.ai/ai-providers. The content can include a question, selected travel records, relevant notes and recommendations, conversation context, or portions of an authorized email or calendar record. Cloud voice also involves audio processing. We limit the information sent to what is relevant to the feature; it is not necessary for every AI request to include your entire account. The health details saved in your Travel Profile and the files saved in Documents in the app (such as passports, identity cards, driver's licenses, visas, and health and insurance records) are never sent to an AI provider. When Rucks imports your email, it reads each message's own text and never opens an attachment, and only a message that looks like a booking or a loyalty membership is sent to an AI provider to be read. Information you type, paste or share into a request yourself, such as a question or a list, is sent as that feature describes.
We do not use private user content, connected-account content, or information derived from that content to train or improve general-purpose AI models, and we do not authorize providers to do so. Making your own memory more useful through summaries, retrieval, or personalization is different from training a model for general use by others. Google-specific restrictions also apply even if data has been derived, aggregated, or anonymized.
No training does not mean zero retention. Providers may retain content or related records for limited operational, abuse-prevention, security, or legal purposes under the applicable service arrangements. Retention differs by provider, endpoint, and account configuration. For example, standard OpenAI API abuse-monitoring retention is generally up to 30 days, with potentially longer retention for specified safety or legal reasons; approved account controls and some endpoints have different rules. We do not represent that every Rucks AI request is covered by zero-data-retention processing. Contact privacy@rucks.ai for information about the providers and arrangements relevant to your request.
Access by our personnel or providers must be limited to authorized purposes and appropriate safeguards. The stricter conditions in section 8 apply to human access to Google data. Your AI permission. Rucks sends your information to the AI providers listed at rucks.ai/ai-providers only with your AI permission. If you create your account with the acknowledgment beside the signup button (“By signing up, you agree to our Terms of Use and Privacy Policy”), creating your account is that permission: you allow Rucks to send your requests, and the travel information each one needs, to those providers, for the purposes and under the conditions in this section. If Rucks asked you instead in the app, on a screen that names the providers (an account created earlier, or with an earlier version of the app), the choice you made there stands. Accepting this version of the policy later, for an account you already have, does not give AI permission, and does not turn AI back on if you declined it or turned it off. Rucks records your permission, and how and when you gave it, with the version of this policy or of the screen's wording. Rucks changes AI models often: a new model, or a new provider added to that list, does not ask again, because a provider is added only before it receives anything and only if it does not train on what it receives. A new purpose, or a provider that does not meet that condition, always asks again. Without the permission, Ask, voice, email and calendar import, pasting lists, and new memory updates send nothing to them and stay off, and everything else keeps working. Two features still look up a city without it, what's on this week (Home and city pages) and a city page's history: for those, Rucks sends Tavily the city (where your phone is, your home city, or a city you open), its country and the week you look at, and sends OpenAI the same and the language you read Rucks in, with public web text about that city, never your name, your account, anything you wrote or your memory. You can turn it off at any time in the app (Profile → AI permission). Turning it off stops new requests within seconds and ends a voice conversation in progress; it cannot take back what was already sent.
Rucks follows the Google API Services User Data Policy, including its Limited Use requirements, and the applicable Google Workspace user data and developer policy. These protections apply to information obtained through Google APIs and covered information derived from it. This section controls if another part of this policy appears to permit a broader use.
We use this information only to provide or improve appropriate Rucks features that are visible and prominent to you, such as the authorized travel-history and memory features. We do not sell it, disclose it to data brokers or information resellers, use it for advertising or retargeting, use it for credit or lending decisions, or use it to create, train, or improve AI models beyond the specific user's permitted personalized functionality.
Transfers are limited to those permitted by Google's policies: providing or improving the authorized user-facing functionality with your consent; necessary security purposes; compliance with law; or a merger, acquisition, or sale of assets after obtaining your explicit prior consent. General acceptance of our Terms or this policy is not that transaction-specific consent.
Humans may read covered data only with your documented permission to view specified information, where necessary for security or compliance with law, or for permitted internal operations involving data that has been appropriately aggregated and anonymized. Our personnel, contractors, agents, and successors must follow these restrictions. We do not treat an unrelated product-improvement purpose as permission to inspect your emails.
You can disconnect Google from Rucks and revoke access through your Google Account permissions. You can also request deletion of imported information. Revoking access at Google stops future API access but does not, by itself, erase copies already held by Rucks; section 9 describes deletion.
Account content. Rucks is designed to hold a continuing travel memory. We generally retain saved trips, places, notes, roster entries, recommendations, conversations, and related searchable representations while your account is active, until you remove them, or until they are no longer needed for their stated purpose. Source records are retained only as needed to support the authorized import, reconciliation, correction, and memory features. Removal from a screen can precede final deletion from underlying systems. You can request erasure through the contact in section 15 if the available control does not meet your needs.
Diagnostics and operational records. Account-linked language decisions and product records can remain until account deletion; they are not anonymous merely because their text fields omit conversation content. Security, support, and legal records are retained according to the purpose, risk, legal requirements, and the time needed to resolve the issue. Where a longer retention period is necessary, we restrict the retained information to that purpose. We do not retain information indefinitely merely because it might someday be useful.
Disconnecting a source. Disconnecting an account stops future syncing and removes or disables the stored access credentials. The disconnect flow describes the treatment of imported information; information you separately saved or supplied can remain in your memory. Revoking permission only at the source provider does not automatically send Rucks a deletion request. You can ask us to delete source-derived information as well as revoke access.
Account deletion. When you ask to delete your account (in the app, Profile → Account → Delete my account), it is deleted 30 days later, and purging then begins automatically. You can keep using your account and cancel the deletion in the meantime. For deletion without the 30 days, write to privacy@rucks.ai. We verify the request appropriately and process it within applicable legal deadlines. You do not have to accept a recovery period where the law requires earlier erasure.
Purging removes account information from active systems and initiates associated cleanup, including search indexes and external connection credentials. Those operations do not all complete in a single atomic transaction. Limited information may remain where law permits or requires it, including to document a rights request, meet recordkeeping duties, address fraud, or resolve a dispute. Retained information is not reused to reconstruct your ordinary account for unrelated purposes.
Backups and recipients. Backup copies can remain until they expire or are securely removed under our backup process. We restrict their use and must reapply relevant deletion instructions if a backup is restored. Provider-held records follow the applicable service arrangements and legal duties. Copies someone independently kept after an authorized share may also remain, subject to their and our obligations under applicable law; we cannot retract what they already saw. Where law requires notice to recipients or deletion of particular copies, we take the required steps. Health-data deletion has additional requirements explained in the Consumer Health Data Privacy Notice.
You can use available account controls to review and correct information, manage connections, change language and notification settings, manage sharing, download a copy of your data, and request deletion. The download (Profile → Account → Download my data) contains every kind of personal information Rucks keeps about you: your account and Profile, your conversations with Rucks, your memory and your Portrait, your travel timeline and trips, your Plans, places and lists, what you shared and were sent, the emails Rucks imported and the connections they came through, your consent records and privacy choices, and the records of your account and your use of the app. Its manifest lists each part, and what Rucks keeps but leaves out, with why: sign-in secrets and keys, other people's private information, internal processing records, and suggestions Rucks makes again from your memory. Device settings control permissions such as location, microphone, and photos. Some saved or imported information must be removed separately after a device permission is revoked. Essential account or security communications can continue even if you opt out of promotional messages.
Depending on the law applicable to you, rights can include confirmation of processing, access and a copy, correction, deletion, portability, restriction, objection to particular processing, withdrawal of consent, information about recipients, and an appeal of a refusal. You may also have rights relating to sensitive information, targeted advertising, sale or sharing, and significant automated decisions. Our current practices do not involve sale of personal information, sharing for cross-context behavioral advertising, or targeted advertising. We do not treat use of Rucks as a waiver of those rights.
Send a request to privacy@rucks.ai. Identify the right you want to exercise and enough information for us to locate the relevant records; do not send a password, full identity document, or medical detail unless it is necessary and we have explained a secure way to provide it. We verify requests proportionately, may ask an authorized agent to demonstrate authority, and protect information about other people when responding. You do not have to create an account to contact us about information concerning you. We respond within the applicable statutory period, explain any permitted extension, and give reasons and appeal information if we cannot fully comply. We do not discriminate against you for exercising privacy rights.
For people in the European Economic Area, United Kingdom, or Switzerland, applicable rights include objecting to processing based on legitimate interests and complaining to your local data protection authority. An objection is broader than correcting one memory item: tell us which processing you want stopped. For people in Brazil, applicable rights include confirmation, access, correction, portability, information about shared use, and anonymization, blocking, or deletion of unnecessary, excessive, or unlawfully processed data, along with consent-related and other LGPD rights. You may contact the ANPD. United States state-law rights apply where their statutory conditions are met; this policy does not imply that every state statute applies to every account. Other countries may provide additional rights. Mandatory rights are preserved.
Browser “Do Not Track” signals do not alter our current practices because we do not conduct cross-site behavioral advertising. We do not use such a signal as permission to track you. Where an applicable law requires recognition of an opt-out preference signal, including Global Privacy Control, we honor it for the processing covered by that law. There is currently no sale or targeted-advertising activity for such a signal to turn off.
We use administrative, technical, and organizational measures appropriate to the information and risks, including access restrictions, separation of account data, protected network connections, and encryption controls. These measures do not mean that all data is end-to-end encrypted: authorized Rucks systems and processors must be able to process information to provide the service. No system is completely secure, and we do not guarantee that loss or unauthorized access can never occur. We handle incidents and provide notifications where required by law.
Please protect your sign-in account, review the content and destination of shares, and tell us promptly about suspected misuse. A confidentiality setting cannot prevent a recipient from misusing information already legitimately received. This does not reduce our own security or legal responsibilities.
Rucks is based in the United States. We and our service providers can process information in the United States and other countries where relevant systems and personnel operate. Their laws may differ from those in your country. An international trip does not itself authorize us to disclose your private information to businesses in the destination.
Where a transfer requires legal safeguards, we use the mechanism applicable to that transfer, such as an adequacy decision or approved contractual safeguards, together with supplementary protections where needed. For transfers subject to European, UK, Swiss, or Brazilian requirements, the applicable local rules govern; one country's contract form is not automatically sufficient for another. Contact privacy@rucks.ai for information about the destinations and safeguards relevant to your information, or an available copy subject to necessary redactions. Consent to this policy is not a blanket waiver of international-transfer protections.
Rucks accounts are for adults aged 18 or older, or the age of majority where higher. We do not provide accounts directed to children or invite children to sign up. An adult's lawful travel records may nevertheless contain a child's name or relationship, for example in a family roster or booking. That does not create a child account or give the child access to Rucks.
Provide only the information about companions or other people that is appropriate for the travel feature, and obtain permission where required. Rucks remains responsible for its own processing; a user's permission or assurance does not eliminate another person's statutory rights. If you believe a child has created an account, or that we hold information about you or your child that should be corrected, restricted, or deleted, contact privacy@rucks.ai. We assess the request and take the steps required by law.
We update the effective date when this policy changes. For material changes, we provide appropriate notice, such as an in-app notice or email, before the change applies where required. We obtain a separate choice or consent when a new use requires it. Posting an updated policy does not retroactively authorize an incompatible use of information or override the restrictions on Google data. Prior versions remain available on request.
Privacy questions, rights requests, appeals, and concerns about information concerning a non-user can be sent to privacy@rucks.ai. For an appeal, include “Privacy appeal” in the subject and identify the earlier request. You may also write to OTB Capital, LLC, doing business as Rucks AI, Attention Privacy, 1117 State Street, Santa Barbara, California 93101, United States. General legal notices can be sent to legal@rucks.ai. You may contact a competent privacy regulator without first asking us for permission.