TRIPQUO — Privacy Policy for the Website, SaaS and Chrome Extension | Approval Candidate

Proposed approval version: LEGAL-GOOGLE-OAUTH-2026-11-05-RC2-EN
Status: Complete counsel-review version; not yet approved or published as an effective policy.
Operator: Yair Ohayon (יאיר אוחיון), an Israeli individual proprietor trading as TRIPQUO; registered as an authorized VAT dealer according to the owner's statement, subject to official verification.
Privacy requests: info@tripquo.io
Effective date: To be set upon authorized publication; not retroactive.

1. Scope of this Policy

This Policy covers the TRIPQUO website, the TRIPQUO software-as-a-service platform for travel agencies, and the TRIPQUO Chrome extension. These are different processing pathways: not every category described below is collected by every feature. The Policy explains what information may be processed, why, who may receive it, how to exercise applicable rights, and the limits of retention and deletion claims.

2. Operator and Data Roles

TRIPQUO is a trade name used by an Israeli sole proprietor, not a separately incorporated company. The operator may determine the purposes of account administration, billing, security and business support data, and may therefore act as a controller in relation to that data. Travel agencies may determine the purpose of processing their customers' and travelers' information, with TRIPQUO acting as a processor or service provider for relevant operations. The classification depends on the actual activity and applicable law, not just contractual labels.

3. Accounts, Authentication and Workspaces

Account and extension pairing features may process the user's name, email address, phone number, business name, user and Workspace identifiers, membership role, language preference, subscription status, connection timestamps and limited security logs. The extension connects to an authorized TRIPQUO Workspace using a pairing process; the server validates extension session tokens and checks access permissions. Connection tokens must not be shared with unauthorized persons.

4. Quotes, Customers and Travelers

Depending on user actions, the platform may process customer contact information; destinations and travel dates; hotels, rooms, meal plans and cancellation policies; passenger and room counts; flights, baggage and fare conditions; supplier and customer prices, currencies and markup; quote versions; customer selections and approvals; and related operational notes. Travel details may constitute personal data even when presented as business quote information.

5. Chrome Extension's Single Purpose and Page Content

The extension's single purpose is to help authorized travel agents identify, review and transfer hotel and flight offer details from supplier websites into TRIPQUO to build travel quotes. Depending on its final packaged permissions and behavior, it may access content displayed on supported supplier pages, including hotel and room names, prices, currencies, dates, traveler counts, cancellation conditions and flight itinerary details. Some local detection may occur before a user explicitly clicks “Add to Quote”; the exact trigger and set of accessible websites must be confirmed from the packaged extension source. The extension is not intended to monitor general browsing habits, and collection unrelated to its disclosed purpose is not authorized by this Policy.

6. Website Addresses and Browsing Context

The service may process a supplier domain, page category, structural page signature, path pattern and certain page-related diagnostic details to identify site layouts and assist extraction. The inspected server code sanitizes some URL fields by stripping queries and fragments; this does not establish that every URL or browser event is treated identically in all extension code paths. We must verify the complete extension package and server communications before stating that particular browsing metadata is never stored. General browsing histories are not collected for sale or advertising as part of the extension's disclosed purpose.

7. Selecting and Sending Offer Information

Users can review, correct and select extracted offer fields before adding an offer to a quote. Necessary information may be sent to TRIPQUO servers to validate the extension session, check Workspace permissions, locate customers and quotes, create or update a hotel or flight option, and generate content for agency customers. Server-side endpoints checked to date authorize actions in the relevant Workspace. The presence of page analysis does not automatically mean full page content is stored on every visit; the precise payload of each extension operation must be verified.

8. Teach Tripquo and Shared Structural Site Learning

When an agent teaches or corrects the extension's recognition of an offer, TRIPQUO may store extraction mappings, site domain, page categories, path patterns and structural hints for the agency's authorized use. A separate structural-learning feature may reuse and share restricted site-layout hints across agents to improve recognition at the same supplier websites. This does not authorize one agency to access another agency's quotes, traveler identities or customer records. Structural hints are not necessarily anonymous in every case, and free-text fields or derived data may sometimes contain personal information. Effective sharing controls and disclosures must reflect the deployed code and applicable legal requirements.

TRIPQUO does not permit cross-agency structural learning to share passports, payment card numbers, passwords, traveler identities or another agency's private offer details. Mapping, historic shared records and backup retention may differ from the limited traveler-document access window. Access, correction and deletion requests will be reviewed subject to applicable law and agency roles.

9. AI-Assisted Extraction

Some TRIPQUO functions may send selected page or offer content to an external AI provider to extract or repair data, where that route is enabled. AI output may contain errors. Server source confirms that the analyzeSupplierPage route can send sanitized supplier-page/offer content to the OpenAI Responses API when invoked. The exact invocation and payload from the current extension v1.0.5 (the previous legal audit inspected v1.0.4), deployed provider configuration, processor location, access to input/output, model-training settings and retention period remain subject to verification against the final extension, server settings and service contract. We do not promise that AI providers delete all copies on the same schedule as TRIPQUO unless verified separately.

10. Local Chrome Storage and Session Information

The Chrome extension may use browser-managed local storage for its pairing status, settings, drafts or temporary page content. The backend creates extension sessions, but the exact Chrome storage API, locally stored keys, duration, encryption and sync behavior have not yet been inspected in the final extension package. An accurate key-by-key inventory and applicable removal procedures must be added before this Policy is adopted. Never share or send authentication tokens as part of routine support.

11. Diagnostics and User-Submitted Bug Reports

If a user submits an extension bug report, the server may store the reporter's name and email, Workspace, vertical, supplier hostname, a sanitized page URL in that reporting route, report description, optional screenshot URL, extension version and limited technical metrics. Users must avoid attaching passports, credit cards, confidential customer details or other excessive personal data in reports. The retention period and support access rules for reports require confirmation before publication.

12. Passports and Traveler Documents Are Separate Features

The TRIPQUO platform has separate traveler document upload and passport OCR workflows, subject to their own specific notices, per-upload authority and consent, appropriate agent confirmation and human verification of extracted fields. The dedicated extension backend endpoints examined are not passport upload endpoints; the final Chrome extension package must still be audited to verify that it does not access or transmit passport content. The platform's access to traveler documents and sensitive extraction output is configured to end within up to 72 hours. Ending access is not the same as physical erasure of every underlying file, vendor backup or AI processor copy. Legacy Base44 objects require a separate provider deletion process. A global production R2 cutover is not yet fully verified for all agencies.

13. Permitted Purposes

Information is processed to provide the requested offer capture and quote creation functionality, recognize supplier site structures, maintain authorized accounts and connections, troubleshoot and improve extraction reliability, secure the service, prevent abuse, provide support, meet applicable legal obligations, and fulfill other specifically disclosed operational needs. Extension-derived information must not be used for personalized advertising, sold to data brokers or used to assess creditworthiness.

14. Legal Bases and Collection Notices

Depending on applicable law, processing may be based on contract necessity, legal requirements, a permitted legitimate interest, or affirmative consent where required. Clear information about data categories, purposes and recipients must be presented before collection. Travel agencies are responsible for ensuring they have authority to process customer and traveler information and provide applicable notices. Installing the extension is not a blanket authorization to capture or disclose any personal information encountered online.

15. Recipients and Service Providers

Authorized agency users and operational service providers may have access on a need-to-know basis: Base44 for the application and data infrastructure; Cloudflare R2 for new private traveler documents only after the cutover is activated; relevant AI providers where the feature sends information for processing; Resend for specified email workflows; and payment or analytics providers if enabled. This list does not mean each provider receives information originating from the Chrome extension. Before final publication, an accurate data-flow and subprocessor register will identify all actual recipients, their purposes, data categories and applicable safeguards.

16. International Transfers

Some application, messaging, AI and storage vendors may process or store data outside Israel. Regional storage settings do not prove that all AI, log, backup or support processing happens in one region. Transfers must comply with applicable law, contractual safeguards and, where relevant, requirements applicable to international travel agencies or travelers.

17. Security

The inspected backend implements extension-session checks, Workspace authorization and structural sanitization for some site-learning and bug-report fields. Security of the Chrome package itself—including requested permissions, authentication token storage, network destinations, draft data, error logging and cross-agency isolation—requires additional verification. No system is entirely risk-free. This statement does not exclude our legal duties to implement appropriate safeguards. Users should report suspected unauthorized access promptly.

18. Retention Periods — Final Schedule Pending Verification

Accounts, quote records, private or shared site-learning patterns, telemetry, bug reports, session records and traveler documents have different purposes and may have different retention periods. When issued, an extension server-side session token is configured with a maximum 30-day expiry unless revoked earlier; that does not establish the deletion date for the session record or any other data. The 72-hour window concerns traveler documents in the platform and does not automatically apply to all extension data. A verified retention matrix for each record, backup and downstream vendor is a publication prerequisite.

19. Disconnection, Uninstallation and Deletion

Uninstalling the extension does not automatically delete data previously saved in the TRIPQUO account or by a processor. Disconnecting a session, clearing local drafts, removing learning rules and deleting an account are different operations whose actual behavior must be verified. Subject to identity and authority checks, requests to access, correct or delete information will be handled under applicable law, including lawful retention requirements for accounting, security records and vendor backups.

20. Marketing, Cookies and Similar Technologies

Extension-derived data is not intended for sale to advertisers or personalized advertising. Website marketing subscriptions, where offered, are separate and must provide the appropriate choice and opt-out required by applicable law. TRIPQUO's website uses Base44 platform analytics; verified event metadata includes attribution/referral information (including UTM parameters), login, page activity, session duration and AI feature traffic. Analytics supports service operation, security, usage monitoring and improvement. The exact cookies, visitor identifiers, IP handling, subprocessor access and any pre-consent processing remain subject to technical and legal verification. Base44 documents a 60-day analytics event query window, which does not establish deletion of every log, cookie or backup after 60 days. Chrome-derived data must not be repurposed for unauthorized marketing measurement.

Targeted cookies update — release candidate, not yet live: The inspected production HTML includes Base44 Analytics and Visitor Tracking. The Base44 referral script may set base44_referrer_id and base44_referrer_origin for up to 30 days for attribution; a complete cookie/identifier inventory for every provider is not yet verified. In the new, unpublished code candidate, known Analytics and Visitor Tracking paths are configured in consent mode before their scripts execute, with a separate choice to accept, reject or customize non-essential measurement. The choice is retained in this browser/device for up to 180 days unless purposes change, it expires, or browser storage is cleared. It can be changed through Privacy and cookie settings. Withholding or withdrawing consent blocks future measurement in the identified client-side paths and attempts to clear those two referral cookies. This choice is separate from acceptance of Terms, email marketing consent, and authentication permissions. This candidate does not prove all other vendor-level telemetry, server processing or provider copies are stopped or deleted. Owner-authorized publication and live network verification are required before presenting the implementation as active and verified.

21. Minors and Sensitive Information

Do not submit a child's identity document, personal information or other sensitive data without a lawful reason and appropriate authorization. The extension is not intended to build collections of traveler identity records or to profile minors. These restrictions must be reflected in actual product behavior and permissions.

22. Privacy Rights

Subject to applicable law, individuals may request access, correction, deletion or information about processing. When the agency controls its traveler's data, we may coordinate with it to respond. We may verify the requester's identity and authority and take steps to avoid exposing other users' or agencies' information. Requests: info@tripquo.io.

23. Security Incidents

In the event of a suspected passport exposure, credential compromise, cross-Workspace access or personal data incident, TRIPQUO will take appropriate steps to contain, investigate and document the event and provide notifications where required by law. Do not assume one universal breach-notification deadline for all jurisdictions and incident types.

24. Website Rights and Lawful Capture

Agents are responsible for accessing and using supplier information only where they have a lawful right to do so and must respect valid site terms, copyright and applicable restrictions. The extension must not be used for unauthorized access or circumvention of CAPTCHA, login or other legal technical safeguards. Supplier content remains subject to its owner's rights; extraction is not a guarantee of accuracy or permission to republish it.

25. Updates and Contact

Material changes to data collection, data sharing or use will be prominently disclosed and renewed consent obtained where required. A new policy will not retroactively validate earlier unauthorized collection. Before final publication, the verified operator identity, support and privacy contacts, effective date and legally required information will be provided. Privacy: info@tripquo.io; Support: info@tripquo.io.

26. Chrome Web Store Limited Use Statement

Information obtained through Google Chrome APIs or the TRIPQUO Chrome extension will be used solely for the extension's disclosed single purpose and related necessary operations, subject to the Chrome Web Store User Data Policy, including its Limited Use requirements. Such information will not be sold, transferred to advertising platforms for personalized ads, or otherwise used for prohibited unrelated purposes. This statement must be confirmed through a complete technical and vendor audit before it is certified.

Addendum — Google Sign-In and Account Information

Signing in with Google

TRIPQUO offers a Google sign-in option on its website and application. When a user chooses this option, Google authenticates the user, and TRIPQUO's authentication flow, currently provided through Base44 infrastructure, may receive the basic identity attributes needed to associate or create an authorized account. Depending on the approved OAuth scopes and actual implementation, these attributes may include the user's email address, display name, Google account identifier and profile image. Basic Google sign-in does not require access to Gmail message contents, Google Drive files, contacts or calendar events.

Processing purposes and separate roles

We use account identity information to authenticate users, create or link accounts, manage sessions and access permissions, associate users with their agency Workspace, prevent abuse, respond to support requests and comply with applicable law. Google is the identity provider; Base44 supplies the currently integrated authentication/application infrastructure; TRIPQUO provides the travel-agent SaaS service operated by Yair Ohayon (יאיר אוחיון), an Israeli individual proprietor trading as TRIPQUO according to the owner's statement. The registration status and any legally required business disclosures remain subject to verification before the policy takes effect. Signing in with Google is not, by itself, consent to marketing, using Gmail/Drive contents or sending Google profile information to an AI model for training.

Credentials, storage and retention

TRIPQUO does not ask users to disclose their Google password to us. The authentication system may handle OAuth authorization codes, tokens and application sessions according to its actual configuration. The exact storage, expiration, access and deletion of provider credentials, identity records and security logs must be verified before a final security or retention claim is made. Account and authentication data are not subject to the separate up-to-72-hour traveler-document access policy. Removing Google access or deleting a Google account does not necessarily erase TRIPQUO account and legally retained records. Applicable access, correction and deletion requests will be reviewed under relevant law and the agency's role.

Choice, rights and contact

Users can use another available sign-in method, where supported, and may review or revoke connected-app permissions through their Google account settings. Google sign-in is not authorization to retrieve Gmail messages or Drive documents. General service/privacy contact: info@tripquo.io (owner-provided; recent incoming mail addressed to this connected inbox was confirmed from message metadata without opening messages; the privacy-request response workflow still needs operational confirmation). Any legally required business registration disclosures and cross-border processor arrangements must be verified before the policy takes effect.