Privacy policy

How Junturi treats your data.

What we collect, who can see what inside a trip, and how to leave with nothing left behind. Written for people, reviewed by counsel.

Version 1.0Effective 18 October 2026Operator: Jesus Javier Victoria, doing business as JUNTURI SOFTWARE PUBLISHING

01Who we are

Junturi is operated by Jesus Javier Victoria, a Philippine sole proprietor doing business under the DTI-registered business name JUNTURI SOFTWARE PUBLISHING (DTI Business Name No. 8482793) ("Operator", "we", "us" or "our"), who is the personal information controller responsible for the processing described in this policy. "Junturi" refers to our app and associated services.

Business address: 117 Orchids Street corner Dahlia Street, Alido Subdivision, Barangay Bulihan, Malolos City, Bulacan 3000, Philippines
Privacy questions and rights requests: privacy@junturi.app, or the business address above
Service and subscription questions: support@junturi.app
Designated privacy officer: Jesus Javier Victoria, at the privacy address (Section 12.2)

For the purposes of the Philippine Data Privacy Act of 2012 (Republic Act No. 10173, the "DPA") and, where they apply, the EU General Data Protection Regulation (Regulation (EU) 2016/679, "GDPR") and the UK GDPR and Data Protection Act 2018 ("UK GDPR"), the Operator is the personal information controller ("controller") of the personal data described in this policy.

02Scope and who may use Junturi

This policy covers the Junturi web app at app.junturi.app, the installable web app, the Junturi apps distributed through the Apple App Store and Google Play, and the transactional emails and push notifications we send.

You must be at least 18 years old to use Junturi. We do not knowingly collect personal data from anyone under 18. You confirm this when you create an account. If you believe a person under 18 has created an account, contact us at the privacy address above and we will delete the account and its data.

03What Junturi is, in one paragraph

Junturi is a shared trip-planning app. You create or join trips with people you invite, plan days and places on a map, record bookings and expenses in several currencies, settle who owes whom, share photos and documents with the members of a trip, and keep a private travel record. Most data you enter is visible to the other members of the trip you entered it on, by design. Section 5 explains exactly what is visible to whom.

04Personal data we collect

4.1 Data you give us

Category Examples Why we collect it
Account Email address, password (stored as a salted hash by our authentication provider), sign-in codes sent by email To create and secure your account. Sign-in is by email and password or by a one-time code emailed to you. There is no social login.
Profile Display name, initials, avatar photo, optional bio, optional payout handles (for example a PayPal.me, Wise or GCash handle) and an optional GCash QR image To identify you to the people you travel with and to let them pay you back. Your profile, including payout handles, is readable only by you, your friends and people who share a trip with you; handles are surfaced at settlement.
Trip content Trip names, destinations, dates, places you pin or mint, day plans, wishlist items, polls, tasks, messages in a trip's Talk, ratings and reviews of places, recommendations you publish This is the product. Visible to trip members; some items can be published more widely by you (see 5.3).
Money data Bookings, costs, currencies, exchange rates, expenses, splits, shares, payments, settlement balances, a private personal budget To compute who owes whom. Money data is shown only to the members of the trip it belongs to, and some of it only to the people it concerns (see 5.2).
Photos and documents Trip memories, highlight photos, place and item photos, profile posts, uploaded tickets, confirmations and receipts To keep the trip's record together. Photos and documents you upload are attributed to you and follow the audience you choose (see 5.2 and 5.4).
Friends and circles Friend requests, friend links, circles (groups of friends), invitations you send by email, people you block To let you invite people you know.
Reports The content you report, the reason (spam, harassment, inappropriate, other) and your account as reporter To review and act on abuse reports.
Support Anything you send to our support or privacy addresses To answer you.

4.2 Data collected from your device, only when you use the feature

Category When Notes
Precise location Only when you tap a "use my location" or "navigate" control on a map, or drop a pin at your position Used to centre the map or resolve a pin. Not collected in the background, not tracked continuously, not stored as a location history.
Camera and photo library Only when you attach a photo or scan a receipt The image you choose is uploaded; nothing else on your camera roll is read.
Push notification tokens Only if you turn push notifications on A device token (web push endpoint today; Apple and Google device tokens in the store apps) so we can deliver notifications you have asked for. Notification bodies never contain money amounts.
Local storage on your device Always Sign-in session, theme choice, an offline queue of things you created while offline, and a small set of interface preferences and caches, listed item by item in Section 14. This stays on your device.

4.3 Data generated while you use Junturi

Category Notes
Usage events We record a small set of product events (for example that a trip was created, that a share sheet was opened) in our own database to understand which features are used. No third-party analytics or advertising SDK is used.
Error reports If something breaks, an error report is sent to Sentry with a stack trace and technical context. Before it leaves your device or our server, we strip your email, username, IP address and authentication headers. We do not use session replay or screen recording.
Referral attribution If you joined from an invitation, the invitation and inviter are recorded so the invitation can be honoured.
Server logs Our hosting provider (Vercel) and database provider (Supabase) keep standard request logs, including IP address and user agent, for security and operations.

4.4 Identity documents, and what we do not collect

We do not require you to provide a government identity document to create a standard account. However, if you upload a passport, ticket, receipt, photograph or other document, we process the information it contains. This may include information about you or other people and may include sensitive personal information. Upload only information needed for the feature you are using. Where practical, remove or obscure information that is not needed, such as a full identity-document number. Check the audience before sharing a file (Section 5).

The Documents area offers a "Visa/ID" category, so it may hold identity documents such as a passport or visa page if you choose to file one there. We do not ask for them, and nothing in Junturi requires one. They are stored privately (Section 5.5), opened only through a link signed for five minutes at the moment you open the document, after a check that you are in its audience, and you can delete them at any time.

We do not collect payment card numbers or bank account numbers. Subscriptions are purchased and billed through Apple or Google under the applicable store terms (see Section 8); we never see your card. We do not use advertising identifiers, do not run ads, and do not sell or rent personal data.

4.5 Information about other people

Some features hold information about people who have not joined Junturi, because a member entered it: a contact you add as a friend by name and email before they sign up, a person you add to a trip's cost split who does not have an account (a managed participant, shown by name only), and the email address of someone you invite. We use this information only to run the feature it was entered for. A friend you add is visible only to you and is deleted when you remove it or delete your account. A person you add to a cost split is visible to the trip's members and is deleted with the trip; if you delete your account, it passes to the trip owner with the money records it carries. An invitation's email address is visible to the trip owner and the person invited, and is deleted with the trip. If you add someone this way, make sure you are entitled to share their details with us.

05Who can see what: the visibility model

This section is unusual for a privacy policy. It is here because Junturi's whole purpose is sharing with a chosen group, and the sharing rules are the most important privacy fact about the product.

5.1 Trip members

Everything you add to a trip (plans, places, messages, polls, tasks, bookings, the existence of expenses) is visible to the accepted members of that trip, unless a narrower audience applies to it: money can be scoped to the participants it concerns (5.2) and a document can be restricted to you or to selected members (5.4). Being invited does not make someone a member: an invitation grants nothing until it is accepted.

5.2 Money

Money is scoped more tightly than the rest of a trip. A booking's cost can be scoped to the whole trip or only to the participants it concerns; participants and the payer see it, others do not. Your personal Budget is private to you, including from the trip owner. Settlement history involving you stays visible to the members it concerns so that the record stays auditable.

5.3 Friends, profiles and the feed

Your profile (name, avatar, bio, highlights you have promoted, posts you have written) is visible to your friends and to people who share a trip with you. Activity feed items are visible only to the people the underlying content is visible to. Ratings you give to places are private to your trip circle; a review you choose to publish is visible more widely; a place recommendation you publish is visible to the members of the trip or outing it came from, not to the public; and publishing either is always an explicit act by you.

5.4 Photos and documents

A photo you upload to a trip's shared memories is visible to that trip's members. A trip cover photo you upload is different: it is stored at a public address (5.5), so anyone who has that address can load it, and the cover picker tells you so when you choose one. A document you upload defaults to the trip's members, and you can narrow it to yourself or to named members at any time from the Documents vault. Share cards and exports from Junturi only ever contain photos their creator uploaded, never another member's. A trip member may feature one of your trip photos as a highlight on their own profile only with your consent: a consent you give for that photo, a consent you give that member for that trip, or a default you set in your profile (nobody, trip members, or friends who are also trip members), which you can override photo by photo. Blocking someone withdraws every such consent from them.

5.5 How images and documents are stored and delivered (media posture)

Junturi stores files in two ways, and the difference matters:

  1. Restricted files (trip memories, item photos, documents, payout QR images) are stored privately, on Cloudflare R2 and in private Supabase buckets. Before sharing a document or image, check the audience shown in the app: some items are shared with the trip; a document can be restricted to you or to selected members (5.4). Access to a restricted item is checked against the item's selected permissions, and the file is delivered through a temporary signed link that expires after one hour, or for a document after five minutes, signed at the moment you open it. Anyone who obtains a valid link may be able to use it until it expires; do not forward a link outside the intended audience.
  2. Public-address files are stored at addresses that are not secret: anyone who has the address can load the file, the address is not listed anywhere public, and we do not index it. These hold your profile avatar, highlight photos you promote, photos on shared bucket-list items, circle photos, profile-post photos, photos on public place recommendations, and trip cover photos you upload. When you remove such a file, we delete the stored file, and a deletion that cannot be verified is retried rather than assumed.

Sharing with a private trip, named members or a private circle is different from public publication. Publishing a place recommendation is an explicit act by you. A recommendation, with your note and your star rating, is visible to you and to the members of the trip or outing it came from; it is not public, and the app tells you who will see it before you confirm.

5.6 Blocking

If you block someone, within Junturi they can no longer send you friend requests, mention you, invite you to outings or contact you through Junturi, your content is hidden from each other, and any consent you gave them to feature your photos is withdrawn (5.4). Blocking does not automatically remove either of you from a trip you already share, and it does not change money you already owe each other, because those records belong to the whole trip. Blocking cannot retrieve copies already obtained. A signed link already issued remains usable until it expires (at most one hour), and a public-address file remains loadable until it is deleted.

06Why we process your data and on what legal basis

Our legal basis depends on the information, the purpose and the applicable law (in the Philippines, Sections 12 and 13 of the DPA; where they apply, Articles 6 and 9 of the GDPR and UK GDPR).

  • Providing the service you asked for. For ordinary personal information needed to create your account and supply the features you request (accounts, trips, sharing with members, money calculations, notifications you turned on, and the subscription entitlement records we receive from Apple or Google), we rely on performance of our agreement with you where that basis applies (DPA s.12(b); GDPR Art. 6(1)(b)).
  • Legal obligations. Where we must keep records or respond to a lawful requirement, we rely on legal obligation (DPA s.12(c); GDPR Art. 6(1)(c)).
  • Security, abuse prevention and reliability. For keeping the service secure, preventing and acting on abuse (including reports you send us), keeping error reports, and keeping the product usage events described below, we rely on legitimate interests where permitted, after assessing necessity and the effect on your rights (DPA s.12(f); GDPR Art. 6(1)(f)). Our interests are the security and integrity of the service, protecting users from abuse, diagnosing faults, and understanding which features are used. You can object by contacting privacy@junturi.app; we will assess the objection under the applicable law.
  • Features you choose. For optional features you switch on or invoke (using your location on a map, attaching a photo or scanning a receipt, push notifications, AI-assisted suggestions), we ask for consent for the purposes explained when you choose the feature (DPA s.12(a); GDPR Art. 6(1)(a)). You may withdraw that consent by turning the feature off, by revoking the permission in your device settings, or by contacting privacy@junturi.app. Withdrawal does not make earlier lawful processing unlawful, and we explain any effect on the feature when you withdraw. Giving the app permission to use your camera, photos, location or notifications is separate from permission to share information with other people or to send it for AI processing: the relevant feature explains those uses, and each AI run is started by you after a notice of what it sends (7.3).
  • Sensitive personal information. For sensitive personal information, including sensitive information contained in documents or photos you upload, we rely on your consent, given when you upload the document or photo, for that feature's purpose and for the audience you select (DPA s.13(a); GDPR Art. 9(2)(a) where it applies), and we obtain that consent before the processing concerned. We do not rely on legitimate interests alone to process sensitive personal information.

Product usage events. We record a small set of product events, each with your account identifier, the event kind and a few event properties (for example that a trip was created, that a member became an organiser, that a share card was shared, that a spending guide was saved, that a decision was closed, and that an invitation link was opened), to understand which features are used. We rely on our legitimate interest in that purpose, subject to your rights. We keep identifiable events for 24 months and then delete them (Section 10). You can object at privacy@junturi.app. No third-party analytics or advertising SDK is used.

We do not use your data for automated decisions that have legal or similarly significant effects on you. We do not use your data to train AI models; what our AI provider may do with data sent through our integration is stated in 7.3.

07Who we share data with (processors and other recipients)

Some providers process personal information on our behalf under our instructions. Other recipients, including the app stores for their own payment, account and compliance activities, determine their own purposes and handle information under their own privacy notices. The list below identifies each recipient's role and the information involved; other users receive your data as described in Section 5.

Provider Role What it does for us Data it receives Where
Supabase Processor Database, authentication, file storage, real-time updates All account and content data Tokyo, Japan (AWS ap-northeast-1)
Vercel Processor Hosting, serverless functions, scheduled jobs, request logs All data in transit through the app; IP address and user agent in logs Serverless functions run in Vercel's Tokyo region; Vercel Inc. is a US company and its content network and request logs are global. Vercel's Data Processing Addendum applies (Section 9).
Cloudflare (R2 object storage; DNS and email routing for junturi.app) Processor Storage of restricted images and documents; routing of inbound mail to our mailbox (Google, below) Uploaded images and documents; inbound support and privacy email in transit R2 bucket in Eastern North America, so uploaded documents, including any identity documents you file, are stored there while the database is in Tokyo; DNS and email routing are global. Cloudflare's Customer Data Processing Addendum (Section 9)
Anthropic Processor AI features (Section 7.3) Only the fields the feature sends, listed in 7.3 Stored in the United States; requests may be processed in the United States, Europe, Asia or Australia (Anthropic privacy centre, dated 2026-06-15, read 2026-09-26)
LocationIQ Processor Turning a typed place name into map coordinates The place text you search for (sent from our server, not from your device) United States
openrouteservice (HeiGIT) Processor Drawing routes between pinned stops Coordinates of the stops (sent from our server) Germany (operator HeiGIT gGmbH, Heidelberg; hosting location not published in its privacy policy, read 2026-09-26)
MapTiler Processor Map tiles Map tile requests (IP address, tile coordinates) Switzerland / EU
Unsplash Processor Cover images for trips, when you search for one Your search text, sent from our server; and, when a trip's Unsplash cover is displayed, your IP address, because your device loads the image from Unsplash's image service Not stated: Unsplash's privacy policy (updated 2022-09-12, read 2026-09-26) says information may be processed in any country where it or its service providers operate
Sentry Processor Error reporting Error reports with email, username, IP and auth headers removed before sending United States
Resend (with Gmail as fallback sender) Processor Transactional email: invitations, sign-in codes, reports to our moderation mailbox Recipient email address and the message content United States
Apple (App Store) and Google (Google Play) Independent controllers for their own payment, account, distribution and compliance activities Distribution of the store apps, subscription billing, push notification delivery (APNs, FCM) Purchase records; push tokens and notification payloads Apple and Google's own privacy notices apply
RevenueCat Processor Subscription entitlement management for the store apps Your Junturi account identifier (the store apps sign in to RevenueCat with it), the store's purchase and subscription records, and the device's IP address, because the RevenueCat library in the store apps contacts RevenueCat directly United States
Google (Gmail) Independent controller under Google's own consumer terms The mailbox that receives mail sent to support@, privacy@ and our other junturi.app addresses, and that sends our replies Your email address, your message and any attachments, and our replies United States; Google's privacy policy applies
open.er-api.com (Exchange Rate API) n/a (no personal data) Fetching public exchange rates No personal data; only the base currency code n/a

We may also disclose personal data where the law requires it, to establish or defend legal claims, or to protect the rights and safety of users or the public. If the business is transferred, personal data would be transferred with it, and you would be notified.

7.1 Third-party links

Junturi shows links to third-party sites for your convenience (for example Google Maps, Apple Maps, Waze, Skyscanner, Agoda, Wise, PayPal, GCash, translation and visa services). When you open a third-party link, your browser, device or the destination service may send or receive information such as your IP address, the requested page and referring information. The destination handles information under its own privacy notice. Where we deliberately include trip details in a link, they are: the booking title you typed and the check-in and check-out dates, for an Agoda search; and the airport pair and travel dates read from a flight booking's title, for a Skyscanner search; map and navigation links carry the place being opened (its map coordinates where it has a pin, otherwise its name; Naver Map links carry both). No account identifier and no affiliate parameter is included.

7.2 Recipients who are other users

Other users receive your data as described in Section 5. Invitations you send by email disclose your name and the trip name to the invitee.

7.3 AI features

Some features use a large language model provided by Anthropic: itinerary suggestions, a spending strategy for a trip, a travel guide, and scanning a receipt image into an expense.

  • When you request one of these, we send a fixed, named list of fields for that feature (destination, dates, day plans, bookings and their categories, your stated preferences, and for receipt scanning the receipt image you chose) to Anthropic, PBC (United States) to generate a response. The list is built field by field; nothing outside it is sent. The data is gathered as you, so a run can never include something you could not see yourself in the app, and money amounts hidden from you by another member's settings are never included. A notice at the start of each run identifies the information before you send it.
  • The result is shown to you, the member who asked for it. We save it into your trip only when you choose to save it; it is never written to the database automatically. A saved result then follows the sharing rules of the trip item it is saved to.
  • Under the commercial terms applicable to our API use, Anthropic may not train its models on the requests and responses we send.
  • Anthropic automatically deletes the requests and responses from its systems within 30 days of receiving or generating them. Longer periods apply by exception: where a submission is flagged under Anthropic's usage policy, requests and responses may be kept for up to 2 years and the related trust-and-safety classification scores for up to 7 years; and Anthropic may keep data where the law requires it. We keep a per-account count of the AI runs you have used, for metering, together with the time that count last changed, for as long as your account exists. We do not log your request or the result. Our server records only counters (which feature ran, the model, token counts and your run count) and never the content sent or returned. One exception: when a run fails, our server log and our error-reporting service (Sentry) record the AI provider's error message so we can diagnose it; that message does not contain your request or any generated result.

08Subscriptions and payments

Junturi Plus is an optional paid subscription purchased and billed through the Apple App Store or Google Play under the applicable store terms: the store collects your payment details, processes the charge and holds your card data. We never receive your card number. We receive, through RevenueCat, a record that your account holds an active subscription, its renewal date and the store's transaction identifier, so that we can unlock Plus features. Payment and subscription information is processed as described here. For cancellation, refunds and applicable withdrawal rights, see the Terms of Service, Section 6. Contact support@junturi.app if you need help identifying the correct purchase or exercising rights against us.

09International transfers

The Operator is based in the Philippines and may access information there to operate the service and respond to requests. Our providers process information in the countries identified in Section 7. A hosting region does not necessarily identify every country where support, logging or other processing occurs.

Where processing happens: the database, uploaded files held by Supabase and Supabase's daily backups (kept for 7 days) are in Tokyo; our serverless functions run in Vercel's Tokyo region (hnd1), while Vercel Inc. is a US company whose content network and request logs are global; restricted images and documents, including any identity documents you choose to upload, are stored in Cloudflare R2 in Eastern North America; each other provider in Section 7 processes only the data listed there, in the country stated; request logs are kept by the provider that generates them, for the periods in Section 10; and the Operator accesses the service from the Philippines. We do not treat your acceptance of this policy as consent to any transfer.

We remain responsible for the obligations that apply to us when a provider processes information on our behalf. For processing subject to Philippine law, we use contractual and other appropriate measures to provide the required comparable protection.

Per-recipient transfer map (figures read on the dates shown):

Recipient Contracting entity Data sent Where Safeguard Their retention
Supabase Supabase Pte. Ltd. (Singapore) (Terms of Service, read 2026-09-29) All account and trip data; files held in Supabase storage Tokyo (database, storage and daily backups) Supabase's Data Processing Addendum (version 1, 1 August 2026), incorporated into its Terms of Service (read 2026-09-29) Backups 7 days (Section 10); customer data deleted 30 days after account termination (DPA 11.2)
Anthropic Anthropic, PBC (United States) Only the fields listed in 7.3 Stored in the US; processed in the US, Europe, Asia or Australia Anthropic's Data Processing Addendum, incorporated into its Commercial Terms without separate signature 30 days, with the exceptions in 7.3
Vercel Vercel Inc. (Delaware, United States) All data in transit; IP address and user agent in request logs Functions in Tokyo; logs and content network global Vercel's Data Processing Addendum, which applies to Pro plans on entering its agreement (effective 2026-03-31, read 2026-09-26) Request logs 30 days (Section 10)
Cloudflare Cloudflare, Inc. (San Francisco, United States) Uploaded images and documents; inbound support email in transit R2 in Eastern North America; DNS and email routing global Cloudflare's Customer Data Processing Addendum, which forms part of its customer agreement (version 6.4, effective 2026-04-03, read 2026-09-26) Until you or we delete the file (Section 11)
Sentry Functional Software, Inc. d/b/a Sentry (United States) Error reports, with email, username, IP address and auth headers removed; a failed AI run's provider error message (7.3) United States (storage region) Sentry's Data Processing Addendum, version 5.1.0, accepted 2026-09-26; Sentry's use of identifying error data for product improvement is switched off 30 days (Section 10)
Google (Gmail) Google LLC (United States), under its consumer terms Support and privacy correspondence United States None: a personal Gmail account carries no data-processing terms, so Google handles this mail as its own controller under its privacy policy Kept by us up to 24 months (Section 10)
Resend Plus Five Five, Inc. (San Francisco, United States) Recipient email address and message content United States Resend's Data Processing Addendum, binding on entering its terms (read 2026-09-26) No per-message period published; account data deleted within 90 days of account termination (DPA)

The other recipients in Section 7 are listed there with the data they receive and their location.

10How long we keep data

We keep personal information for the periods below, unless a shorter period is required or a specific lawful reason requires limited information to be kept longer. When a period ends, we delete the information or make it no longer reasonably identifiable. A legal hold applies only to the information needed for the particular obligation, investigation or claim: access is restricted, the need is reviewed, and the information is deleted when that reason ends.

What we keep, and for how long

Data Retention
Account and profile While your account remains active. If you delete your account, Section 11 applies. We do not delete accounts for inactivity: your account remains until you delete it (Section 11) or a deletion is required by law.
Trip content While the relevant trip remains available, subject to your deletion choices and the shared-record rules in Section 11. Trips you own are deleted when you delete your account.
Money records on shared trips after you leave or delete your account Kept so that the other members' settlement stays correct, with your displayed name and direct account link removed where possible (Section 11).
Abuse reports Up to 24 months after resolution where needed to prevent repeat abuse or deal with related claims; information no longer needed is deleted earlier.
Support and privacy correspondence Up to 24 months after the last message, except where a documented legal hold applies.
Identifiable product-usage events 24 months, then deleted.
Subscription entitlement data While needed to provide access and handle related billing, refunds and disputes, then for 24 months after the subscription ends. Tax and accounting records needed under Philippine law are retained for the applicable statutory period, generally five years calculated from the relevant filing deadline, or the actual filing date if later, under the applicable tax-record rule. A longer period applies only where a specific lawful requirement or documented legal hold requires it.

What our providers keep (their standard periods; we keep no separate copy)

Data Retention
Error reports (Sentry) 30 days.
Request logs (Vercel) 30 days.
Request logs (Supabase) 7 days.
Database backups (Supabase) Daily backups kept 7 days; uploaded files are not included in database backups and are deleted from storage directly (Section 11).
AI requests and responses (Anthropic) 30 days, with the exceptions in 7.3.

11Deleting your account

You can request account deletion from Settings at any time, without contacting us. Before you confirm, the app explains the effects, including deletion of trips you own for all members and the effect on any unsettled balances; it shows those balances but does not stop you.

  • Deletion removes your account and the affected content from ordinary access immediately: the deletion runs when you confirm, with no waiting period. Your profile, friend and circle connections, posts and highlights are removed. Your uploaded photos and documents are deleted from the affected storage systems, not only unlinked.
  • Trips you own are deleted entirely, including every member's content on them.
  • On trips owned by another member: your photos and documents are deleted; bookings you managed on behalf of others roll up to the trip owner; and your money entries (costs, shares, payments and settlement records) remain so that the other members' records stay correct, with your displayed name and direct account link removed where possible. Other members may still identify you from the context. We keep only what those records need for that purpose, for as long as that trip exists.
  • Limited residual copies may remain in restricted backups until their scheduled expiry, for no more than 7 days. If a backup is restored, we apply outstanding deletion instructions before returning the affected information to ordinary use.
  • Deleting your account or uninstalling the app does not by itself cancel a subscription billed through an app store. Use the subscription controls described in the Terms, Section 6.4, to stop renewal. This does not affect any right to withdraw, terminate or receive a refund under applicable law.
  • We cannot recall copies another person lawfully or unlawfully obtained before deletion. You can contact us about ongoing misuse at privacy@junturi.app.

12Your rights

12.1 Everyone

You can access, correct or delete much of your information in the app. For other requests, or to exercise the rights below, contact privacy@junturi.app. We acknowledge your request within three working days and provide the requested action or a reasoned decision within 15 working days, or sooner where applicable law requires. Working days mean Monday to Friday, excluding public holidays in the Philippines. We may request information reasonably necessary to verify your identity or clarify your request; this does not extend a deadline unless applicable law permits it. If we cannot grant a request, we explain the reason and the review or complaint options available to you.

If you believe we have mishandled your personal information or a request, contact privacy@junturi.app and tell us what happened and the outcome you seek. We investigate promptly and explain our response. This does not restrict your right to complain to a competent data-protection authority under its procedures.

12.2 Philippines (Data Privacy Act)

You have the rights to be informed, to object, to access, to rectification, to erasure or blocking, to damages, and to data portability. Jesus Javier Victoria is our designated privacy officer; contact privacy@junturi.app for questions about this policy or to exercise your privacy rights. You may also raise a complaint with the Philippine National Privacy Commission through the procedures described at privacy.gov.ph; our contact process does not remove your rights under those procedures.

12.3 EU and UK

You have the rights of access, rectification, erasure, restriction, data portability and objection, and the right to withdraw consent at any time where consent is the basis. Withdrawing consent does not affect processing before withdrawal. You may complain to your local supervisory authority (in the UK, the Information Commissioner's Office, ico.org.uk). Where we rely on legitimate interests, you may object and we will stop unless we can show compelling grounds.

12.4 Data portability and manual exports

You can export supported trip information as calendar files (.ics) and share cards from the app today. These tools do not include every item of account information. Contact privacy@junturi.app to request access to, or an export of, other information covered by your applicable rights; we currently handle those requests manually. Where the right to data portability applies, we provide the covered information in a structured, commonly used, machine-readable format and transmit it to another controller where required and technically feasible. We protect the rights and information of other people when responding.

12.5 Other places

The law where you live may give you rights in addition to those described above. We honour requests made under those laws in the same way, through privacy@junturi.app and within the times in Section 12.1 or any shorter time that law requires.

13Security

We use technical and organisational safeguards designed to protect personal information. These include encryption in transit (TLS) and at rest by our storage providers; access rules enforced in the database itself (row-level security) as well as in the app; delivery of restricted files only through short-lived signed links after a permission check; server-side secrets held only in our hosting provider's environment; and stripping of identifying fields from error reports before they leave the app. No system can guarantee complete security.

Access to restricted content is checked against the relevant account and content permissions. Some file delivery uses temporary signed links, as explained in 5.5. Those links have limits and should not be shared outside the intended audience.

We assess and record personal-data security incidents and act to contain and address them. Where a breach requires notification, we notify the competent authority and affected individuals within the applicable legal periods.

Under the Philippine notification rules, where the required conditions are met, we notify the National Privacy Commission and affected individuals within 72 hours of knowledge of, or reasonable belief in, the breach. Those conditions concern sensitive personal information or information that may enable identity fraud, reasonable belief that an unauthorised person acquired it, and a likely real risk of serious harm to affected individuals. Any permitted delay or exemption is assessed under the applicable rules.

Where the GDPR or UK GDPR applies to our processing, we will notify the competent supervisory authority or authorities of a personal data breach without undue delay and, where feasible, no later than 72 hours after becoming aware of it, unless the breach is unlikely to result in a risk to individuals' rights and freedoms. If notification occurs after 72 hours, we will explain the reasons for the delay. Where necessary, we will provide information in stages without undue further delay.

If the breach is likely to result in a high risk to individuals' rights and freedoms, we will also inform affected individuals without undue delay, unless an exception permitted by applicable law applies. Our communication will explain, in clear language, what happened, the likely consequences, the measures taken or proposed to address the breach, and how to contact us for further information.

14Cookies and similar technologies

Junturi uses no advertising or tracking cookies and no third-party analytics. No other party collects information about your activity over time and across other websites or apps when you use Junturi. We use cookies or similar device storage for sign-in, settings you choose and supported offline functions. The list below identifies each item, its purpose, who can access it and how long it remains. Each is used because it is necessary for a service you request, because another lawful exception applies (a display preference you set), or because you have given consent. Where consent is required, optional storage is not activated before you agree, and you can change your choice. Clearing local storage can sign you out or remove information that has not yet synchronised.

Device-storage list

Item Purpose Data or identifier Who can access it How long it remains Basis
Sign-in session Keeps you signed in Your session token The app on your device only Until you sign out or the session expires Necessary for the service you requested (authentication)
Theme choice Shows the app in the look you picked The mode name The app only Until you change it or clear storage Your stated display preference (appearance exception)
Offline queue Holds things you created while offline until they can be saved The items you created The app only Until they are saved to your account Necessary for a feature you used
Pending invitation, friend-link and referral tokens Remembers the link you opened until you sign in, so the invitation can be honoured The token in the link The app only Until you sign in Necessary to complete the action you started
Interface preferences and hints Which onboarding hints you dismissed, your preferred map app, haptics, map view and last expense category Your choices The app only Until you change them or clear storage Your stated preferences; nothing is inferred from them
App and map caches (service worker) Copies of the app's own files, recent data and map tiles so the app loads fast and works offline App files, recent responses, map tiles The app only App files are replaced when the app updates; recent data is kept for up to 7 days and map tiles for up to 30 days Necessary for the installable app and its offline use

None of these is read by anyone but the app, none is shared with a third party, and none is used to build a profile of you. The website at junturi.app sets no cookies, uses no device storage and runs no scripts.

15Children

Junturi is for adults. See Section 2.

16Changes to this policy

We identify changes to this policy with a new date and version. We give notice of material changes in the app or by email, normally at least 14 days before they take effect, unless an earlier change is required by law or urgent circumstances. Where a new use requires consent, notice or continued use alone does not replace that consent.

17Contact

Privacy requests and the designated privacy officer (Jesus Javier Victoria): privacy@junturi.app
General support: support@junturi.app
Postal address: as in Section 1