← Coyote and Powell

JUNROS Privacy Policy

Last updated: 2026-11-02

This Privacy Policy explains how Coyote and Powell LLC (“Company,” “we,” “us,” or “our”) handles personal information through the JUNROS mobile application, related server functions, support channels, and JUNROS pages on coyoteandpowell.com.

This English policy applies to JUNROS as offered outside Japan. It is not a reference translation of the Japanese policy.

1. Controller

The controller or organization responsible for the processing described in this Policy is:

Coyote and Powell LLC
8F-B Hirokoji Building
1-17-6 Ueno, Taito-ku
Tokyo 110-0005, Japan

Privacy contact and New Zealand privacy officer:
Coyote and Powell LLC Privacy Desk
info@coyoteandpowell.com

2. Information We Handle

We handle the following categories of information.

Category Examples How obtained
Account information Email address, password hash, account ID, consent records Provided during registration or generated by our authentication system
Guest account and registration information System-generated account and authentication identifiers; information needed to resume a guest account; the email address entered for registration; registration-process identifiers, status and timestamps Generated when guest use begins or when you register an email address
Third-party sign-in information Provider-specific account ID, email address, and name if supplied and retained Received when you choose Sign in with Apple or Google
Profile information Display name and profile image you choose. Not shown to other users Optional; provided by you when you set up or edit your profile
Travel content Journeys, dates, locations, carrier and facility names, flight or train numbers, booking references, notes and companion names Entered by you or extracted from a document you submit
Scan content Images and PDFs of supported travel reservation documents Selected or captured by you, or attached to an email you forward to JUNROS
Forwarded email Subject, sender address, body text and attachments of emails you forward to your JUNROS forwarding address, and that forwarding address When you forward an email to your forwarding address; the address is created when you first open the forwarding screen or create a new one
Ask AI content Text you enter in Ask AI and the resulting conversation (questions and answers) Optional; when you use Ask AI
Subscription information Internal user ID, product ID, entitlement and purchase status Received from Apple and RevenueCat
Usage information AI-read count, request status and subscription-period counter Generated when you use AI reading
Support information Feedback text, attachments and correspondence Provided when you contact us or submit feedback
Security and operational information IP address, request time, app or browser version, operating system, device type, security and administrative-access logs Generated during operation of JUNROS and its supporting systems
Guest security information App Attest key identifiers and public keys, verification results, request-replay protection records, DeviceCheck guest-use status, and keyed hashes used to limit registration-confirmation emails Generated or received when you start guest use, authenticate a device, use relevant features, or request registration
Meta app-measurement information An identifier generated by the SDK on the device, app-install and activation events, device and app information, and measurement-setting information Sent to Meta by versions using the SDK, including version 1.7.3; see “Meta app-install and activation measurement” below

Guest use and registration

The guest-use descriptions in this Policy apply to versions or trial environments that provide guest functionality. Publishing this description does not mean that guest functionality is available in the version you currently use.

When you start as a guest, our authentication system creates an account without requiring you to register your own email address. Guest use is not anonymous use: we handle an account ID, system-generated authentication identifiers, authentication information and records relating to acceptance of the Terms.

The descriptions in this Policy for journeys, documents, forwarded emails and subscriptions also apply when you use those features as a guest. If you later register an email address, you continue with the same account, and your existing travel content becomes associated with that address.

To send and complete the registration confirmation, resume the process and prevent misuse, we keep the email address you enter, the registration-process identifier, status and timestamps. We separately keep a keyed hash of the destination address and request information to limit abusive confirmation-email requests. Their different retention periods are described in Section 9.

To respond to delivery failures and spam complaints for authentication and confirmation emails, we receive delivery-event records from our email provider and handle a keyed hash of the recipient address, the suppression reason, occurrence and update times, and delivery-event identifiers. We check this suppression information before sending guest-registration confirmation emails to prevent repeated inappropriate sending. We also use our delivery provider’s suppression controls. Our suppression records do not contain the email message body or its confirmation link.

Consent records

For acceptance of the Terms and related documents, we handle account and consent-event identifiers, the document version and language, app version, the time reported by the device and our receipt time. If different information arrives for the same event, we record the fields that differ, the latest conflicting information, the number of conflicts and detection times to check the accuracy of our records. These records do not include journeys, images or email message bodies.

Website analytics information

On our English landing page at https://coyoteandpowell.com/en/junros/, Microsoft Clarity collects page views, clicks, taps, scrolling and other interactions, technical information such as device and browser characteristics and country, and page content and layout information used to reconstruct visits as session replays. This information is collected through the webpage and sent to Microsoft. We use the resulting records and heatmaps to understand and improve that page. We do not use Clarity inside the JUNROS mobile app.

We also use Vercel Web Analytics for general website statistics. Details of both services and their settings are in our Website Cookie Policy.

We do not receive your complete payment-card or bank-account information. Apple processes payment information.

Meta app-install and activation measurement

JUNROS versions with the Meta SDK enabled, including version 1.7.3, send app-install, activation and related measurement information to Meta. This information includes an identifier generated by the SDK on your device, installation and activation events, device and app information such as device model and language, and measurement-setting information. We use this measurement to understand app adoption and the effectiveness of advertising in bringing people to the app.

In our current configuration, the SDK’s advertising-identifier collection setting is disabled, and JUNROS does not request App Tracking Transparency (ATT) permission. Neither fact means that no information is sent to Meta or that Meta cannot associate information it receives with other information.

JUNROS does not currently provide an in-app setting to disable only this measurement. If you wish to avoid these transmissions, discontinue using the app. For Meta’s privacy settings and rights requests, see Meta’s Privacy Policy. Those settings do not necessarily stop all communications from JUNROS. For questions and requests concerning our handling of information, contact us using the details in Section 1.

3. Information Kept Only on Your Device

JUNROS may store the following locally on your device:

  • authentication tokens;
  • cached journey information and temporary images;
  • app settings;
  • locally scheduled notification content;
  • your selected passport-issuing country; and
  • a booking reference or member ID placed on the clipboard at your request.

Clipboard entries created through JUNROS are configured to expire after approximately 10 minutes where supported by the operating system.

The local information listed above is normally removed when you sign out, delete your account, or when JUNROS performs its startup cleanup. Copies you exported, pasted, shared, or backed up through another service are outside our control.

Guest credentials and pending registration

Credentials used to resume a guest account are stored in the device’s Keychain. When iCloud Keychain synchronization is enabled, those credentials may synchronize between devices using the same Apple Account. Resuming the account depends on the synchronized credentials being available and on on-device authentication, such as Face ID or the device passcode.

These credentials are separate from the documents and photos described as On-Device Content below. Synchronizing guest credentials through iCloud does not mean that all journey information or documents stay off our servers. Each category follows the storage arrangements described for it in this Policy.

Signing out alone does not remove guest credentials from iCloud. After email registration is completed, or when you delete the account, JUNROS performs cleanup for that account’s guest credentials. Device conditions or synchronization delays may delay removal. Apple’s privacy policy and applicable terms govern Apple’s Keychain and iCloud services.

When you begin registration from a guest account, JUNROS temporarily keeps information needed to continue the process, including the password you entered, in protected storage on that device. This pending-registration copy is not synchronized through iCloud. It is removed through password-setting and registration cleanup, sign-out or account deletion. An unfinished copy becomes eligible for cleanup after seven days, but cleanup requires the app to run and, where needed, connectivity and account-state checks. It may therefore remain while the app is unused or offline.

Content stored on your device and in your iCloud

Some JUNROS features store documents, photos, and other content you add on your device and in your own iCloud account (a cloud service provided by Apple Inc.) instead of on our servers (“On-Device Content”). For On-Device Content:

  • it is not sent to or stored on our servers, we do not collect it, and we cannot view it;
  • iCloud storage is provided by Apple, and Apple’s privacy policy and iCloud terms apply to it. If you do not use iCloud, On-Device Content is stored only on that device;
  • it is saved to the iCloud account used on the device where you sign in to JUNROS. If you sign in on someone else’s device, it may be saved to that person’s iCloud account;
  • when you sign out, the device’s local copy of content stored in iCloud is removed (the content stays in iCloud), and content on a device that does not use iCloud stays on that device but is not shown to anyone else who signs in;
  • it is kept until you delete it or delete your account. Account deletion, including cases where some content may remain, is described in Section 13 of the Terms of Service; and
  • because we keep no copy on our servers, we cannot restore On-Device Content that is lost from your device or iCloud.

JUNROS does not currently use remote push notifications. Its travel reminders are scheduled locally on the device.

4. Purposes

We use personal information only as reasonably necessary to:

  1. register and authenticate accounts;
  2. store, display and synchronize journeys;
  3. perform AI reading requested by you;
  4. provide Ask AI: answering your questions about your trips using your itinerary;
  5. apply Free Plan and Pro usage limits;
  6. confirm and administer subscription entitlements;
  7. send authentication, account and service messages;
  8. provide support and investigate reported problems;
  9. improve JUNROS, consider new features and carry out statistical analysis, in principle in a form that does not identify you;
  10. secure JUNROS, prevent misuse and preserve audit records;
  11. comply with law and respond to valid legal process; and
  12. establish, exercise or defend legal claims.

For the Meta measurement described in Section 2, we also use app-install and activation information to understand app adoption and the effectiveness of advertising in bringing people to the app. This information is not described as anonymous merely because the SDK’s advertising-identifier collection setting is disabled.

We do not use travel documents or itineraries for advertising. Website interaction information is disclosed to Microsoft through Clarity as described in Sections 2 and 6 and our Website Cookie Policy. We use Clarity to analyze and improve our English landing page and configure its advertising-storage setting as denied. Microsoft’s independent handling of the information is described below and in its Privacy Statement. This disclosure does not limit any right to opt out or other right provided by applicable law.

JUNROS does not use AI output to make decisions that produce legal or similarly significant effects concerning you.

5. AI Reading and Explicit Permission

AI reading is optional.

When you request AI reading, the selected image or PDF and a processing instruction are sent through Vercel-operated server infrastructure to Anthropic in the United States. The purpose is to extract and structure the travel information requested by you.

If you forward an email to your JUNROS forwarding address, JUNROS reads it automatically the next time you open the app. The email’s attachments (or its text, if it has no attachments) are sent to Anthropic in the same way, without a separate selection for each email. This happens only after you have given the permission described below.

Before the first transmission, JUNROS will show an AI-specific disclosure and request your explicit permission. This disclosure may appear on the same screen as the request to accept the Terms of Service. Accepting the Terms alone does not replace permission for AI transmission. The disclosure will identify:

  • the information sent;
  • Anthropic as the AI recipient;
  • the United States as a processing location;
  • the purpose of the transmission;
  • the currently verified provider-retention period; and
  • how to avoid the transmission.

We do not authorize Anthropic to use submitted content to train general-purpose models.

Anthropic may retain API inputs and outputs for a limited period under the Company’s account settings and Anthropic’s applicable terms for security, abuse prevention and legal compliance. We do not authorize the use of submitted content to train general-purpose AI models. Current retention information may be requested through the privacy contact below.

Do not submit medical records, health records, national identification numbers, tax identifiers, bank-account information, payment-card details, or documents unrelated to travel. Do not forward copies of passports, insurance cards, payment cards or similar documents. If you set up automatic forwarding, limit it to booking emails.

6. Service Providers and Other Recipients

We use the following providers to operate JUNROS.

Provider Function and information involved Provider or principal processing location
Supabase Inc. Authentication, database and file storage; account, profile, journey, scan, forwarded-email, usage and feedback information Primary application data stored in AWS Tokyo region; provider administration may involve the United States
Vercel Inc. Server functions through which scan content passes on its way to Anthropic and through which forwarded emails pass before storage; server and security logs United States
Anthropic, PBC AI extraction from scan content, and generating Ask AI answers (your question, the recent conversation in that thread, and your itinerary data) United States
RevenueCat, Inc. Subscription-entitlement management using an internal user ID and purchase status United States
Cloudflare, Inc. Receiving emails you forward to your JUNROS forwarding address and passing them to our server functions; we do not store emails on Cloudflare in our processing United States
Apple Inc. App distribution, in-app purchase, optional Sign in with Apple, maps, place search and weather forecasts where provided (see “Maps and weather” below), App Attest and DeviceCheck for guest security checks, and iCloud Keychain synchronization of guest credentials Countries where Apple operates, including the United States
Google LLC Optional Google sign-in and user-initiated external searches, and operational backups of the JUNROS database and stored files United States and other countries where Google operates
Plus Five Five, Inc. (Resend) Delivery of authentication and confirmation emails, including recipient addresses, message content containing confirmation links, and delivery records United States

Resend’s message content and delivery records are separate from the confirmation-email abuse-prevention history we keep. Deleting that history from our systems does not necessarily delete Resend’s records at the same time. Resend retains information under the applicable service terms, settings and legal requirements. For the Free plan we currently use, Resend states that email and delivery-log data is normally retained for 30 days. Backups and records required by law are subject to separate arrangements. Resend manages its suppression list separately from ordinary delivery-log retention.

We require service providers to process information only for authorized purposes and to apply appropriate protections through contractual or other legally recognized measures.

Operational backups are used only for disaster recovery and are not used for ordinary operation.

Maps and weather

Where JUNROS provides features that show maps or weather forecasts for your journeys, your device sends the following directly to Apple’s services. This information does not pass through our servers.

Information sent Apple service Purpose
The area of the map being displayed (around the airports, accommodation, stations and other places in your journeys) Apple Maps (MapKit) To display map images
Text describing the places in your plans (accommodation address or name, station names, places for meals or sightseeing, and airport names where no airport code is available; for accommodation, sightseeing or meal plans with no place entered, the plan’s title) Apple’s map search To place markers on the map and to determine where to check the weather
Coordinates of the place to check, rounded to about 10 km Apple Weather (WeatherKit) To display weather forecasts
  • We do not send your name, confirmation numbers or journey titles. However, because the plan’s title is sent for a plan with no place entered, any personal name you included in that title may be sent.
  • JUNROS does not use your device’s location and does not request location permission.
  • Coordinates looked up this way are stored only on your device, separately for each user and excluded from device backups, and are deleted when you sign out or delete your account. Weather forecasts are held temporarily in memory and are not saved.
  • Apple’s privacy policy applies to Apple’s handling of this information.

Microsoft Clarity on our English landing page

Microsoft receives the website interaction information described in Section 2 through Clarity. Under the Clarity Terms of Use, we and Microsoft act as independent controllers of the personal data each handles. Microsoft is not acting solely as a processor or service provider on our behalf for that processing.

Microsoft handles the information under its Privacy Statement and the Clarity Terms of Use, which provide for Microsoft’s own purposes, including product and service improvement and advertising-related uses. We keep Clarity’s analytics-storage and advertising-storage settings denied. Microsoft documents that the latter setting prevents Clarity from sharing data with Microsoft Ads; it should not be read as eliminating every independent use permitted by Microsoft’s terms.

Microsoft may process the information in the United States and other countries where it operates. Its Privacy Statement describes its processing locations, protections and privacy choices. Clarity’s website collection is separate from the JUNROS app’s AI reading, travel documents and account functions.

Meta app measurement

The recipients of the app-measurement information described in Section 2 are Meta Platforms, Inc. and related entities identified in Meta’s applicable terms and privacy policy. Meta handles information in the United States and other processing locations.

Meta’s handling is governed by the applicable Meta Business Tools Terms, Meta Privacy Policy and related terms. These provide for uses that may include associating event information with information Meta holds, measurement and advertising personalization. Particular uses depend on applicable settings and conditions. Disabling the SDK’s advertising-identifier collection setting is not, by itself, a basis for saying that all such uses are excluded.

Meta retains and deletes information under its applicable terms, settings and legal requirements. Discontinuing use of JUNROS or deleting your account does not necessarily delete information already received by Meta at the same time. Your choices and our contact route are described in Section 2.

7. User-Initiated External Searches

If you tap an external flight-status, weather, map, carrier, or facility link, JUNROS may construct a URL containing a flight number or place name.

Your device then sends that URL directly to the selected external service, such as Google. We do not separately store the fact that the destination service received the query.

For trips to Japan, this includes searching for police boxes (koban) near the places in your plans; the search URL contains the place name or address. JUNROS does not send your device’s location.

The external service’s privacy policy applies after you open it.

8. Legal Bases for United Kingdom Users

For users in the United Kingdom, we rely on the following legal bases where applicable:

Processing Legal basis
Account creation, journey storage, requested AI reading and subscription administration Performance of a contract or steps requested before entering a contract
AI transmission and device permissions where consent is legally required Consent
Security, fraud prevention, support, audit logs and service administration Our legitimate interests in operating and protecting JUNROS, balanced against users’ rights
Tax, accounting, regulatory and lawful disclosure requirements Legal obligation
Legal claims and protection of persons or systems Legitimate interests or another basis permitted by law

You may withdraw consent at any time. Withdrawal does not affect processing that was lawful before withdrawal. If AI transmission permission is withdrawn, AI reading will no longer be available unless permission is given again.

Information about our legitimate-interest assessment is available on request.

9. Retention

Information Retention
Account information Until account deletion, unless a limited record must be retained for law, security or claims
Profile information (display name and profile image) Until you remove or replace it, or delete your account
Journeys, steps and extracted travel information Until you delete them or delete your account
Original scans associated with a dated journey Until 60 days after the journey end date, then removed by the scheduled deletion process
Original scans without a journey date Until 90 days after registration, then removed by the scheduled deletion process
Forwarded emails (subject, sender, body text and attachments) Deleted 30 days after receipt. Attachments are deleted earlier, once they have been read successfully. Deleting an email from the inbox does not shorten this period. Travel items created from an email, and the original documents saved with them, follow the rows above
Forwarding address Until account deletion; replaced immediately when you create a new address
Device cache and local reminder data Until logout, account deletion, replacement by newer data, or routine cleanup
On-Device Content (your device and your iCloud) Until you delete it or delete your account. Not kept on our servers (see Section 3)
Clipboard information Approximately 10 minutes where supported
Usage-meter records Until account deletion, subject to limited fraud, billing or legal records
Feedback and attachments Until account deletion or earlier deletion when no longer needed
Administrative and security logs For as long as reasonably necessary to investigate access, security incidents, misuse and legal claims, then deleted or de-identified
Authentication-email delivery records According to the period reasonably necessary for delivery, security and legal compliance
Operational backups For the period reasonably necessary for disaster recovery, subject to applicable legal and security requirements
Apple and RevenueCat transaction records According to their legal, accounting, fraud-prevention and platform obligations
Guest registration-process record, including the entered email address, original system-generated authentication identifier, status and timestamps Until account deletion; an unfinished process may be replaced when you start a new registration attempt
Confirmation-email abuse-prevention history, including a keyed destination-address hash, request time and account association In the operational database, records become eligible for deletion after 24 hours and are removed during a subsequent request or the daily cleanup. This normally means approximately two days from recording, but operational failures may delay cleanup. Account deletion removes the account association, not the history itself. Backups follow their separate retention arrangements
Account-linked guest authentication and verification-key information Until account deletion
Hashes of keys already used to create guest accounts, with their use timestamps Retained after account deletion to prevent reuse of those keys. This record does not contain an account ID and currently has no automatic expiration
Sending-suppression records: keyed recipient-address hash, reason, and occurrence and update times While we operate email sending, until we verify that the cause has been resolved or that the recipient wishes to resume receiving messages. Account deletion or the passage of a fixed period does not by itself remove suppression. We review the continuing need for retention at least annually
Delivery-event receipt, notification and deduplication records Records become eligible for deletion 30 days after they are recorded and are normally deleted by the daily cleanup within approximately 31 days of recording. Cleanup may be delayed by operational failures. Sending-suppression records, provider records and backups follow their separate retention arrangements.
Consent and record-consistency information In the operational database, until account deletion. Backups follow their separate retention arrangements.
App-measurement information received by Meta Under Meta’s applicable terms, settings and legal requirements. Discontinuing use of JUNROS or deleting an account does not necessarily delete Meta’s records at the same time; see Section 6

We do not automatically delete a guest account solely because it is a guest account and has been inactive. The retention and deletion rules for journeys, scans, attachments, forwarded emails and other categories continue to apply.

The short-lived confirmation-email abuse-prevention history is separate from the registration-process record, which contains the email address you entered. Not all registration records contain only hashes, and not all copies are deleted within approximately two days. Operational backups and providers’ records follow their separately described retention arrangements.

The guest-use status recorded through Apple’s DeviceCheck is separate from account-linked key information and the hashes of used keys. JUNROS does not reset that status when you delete your JUNROS account. Retention of information managed by Apple depends on Apple’s systems and applicable terms.

Ask AI conversations are stored on our servers and are deleted after 30 days, or earlier when you delete your account.

Website analytics

Clarity data is subject to Microsoft’s published retention periods. Standard session-playback data is retained for 30 days; heatmap and click data and certain retained recordings may remain for up to nine months. For the current categories and periods, see Clarity Data Retention and the Clarity FAQ. This is not a guarantee that all data Microsoft receives is deleted after 30 days. Microsoft’s independent processing is described in its Privacy Statement.

10. Account Deletion

You may initiate deletion of a guest or registered account through JUNROS’s account settings.

Deletion removes account-linked information from active Company systems, including journeys, steps and stored scans, subject to completion of the deletion process.

Some information may remain after account deletion:

  • in rolling backups until expiration;
  • in security or audit records;
  • in records necessary for legal, accounting, fraud-prevention or dispute purposes; and
  • in systems independently maintained by Apple, RevenueCat or another provider under its own legal obligations.

The confirmation-email abuse-prevention history and used-key hashes follow the specific retention arrangements in Section 9. Used-key hashes do not currently expire automatically.

On-Device Content stored on your device and in your iCloud is handled as described in Section 3.

Deleting a JUNROS account does not cancel an Apple subscription.

Where applicable law gives you a right to request deletion from a processor, contact us and we will make the request or provide the appropriate route.

11. International Processing

JUNROS is operated by a Japanese company. Primary application data is stored in Japan, while specified providers process information in the United States and in the other countries identified in Section 6.

For transfers subject to Japan’s Act on the Protection of Personal Information, we use consent or a legally recognized recipient framework and take the measures required by Article 28 and the applicable Personal Information Protection Commission rules.

For transfers subject to the UK GDPR, we use an applicable adequacy regulation, the UK International Data Transfer Agreement, the UK Addendum to approved standard contractual clauses, or another lawful mechanism, as appropriate.

For Canada, Australia and New Zealand, we use contractual or other measures intended to maintain protections applicable to overseas processing.

Copies or descriptions of applicable transfer safeguards may be requested through the contact in Section 1, subject to lawful redactions.

12. Security

We use administrative, technical and organizational safeguards appropriate to the nature of the information and the risks involved.

These include access restrictions, encrypted communications, authentication controls, service-provider review, backup controls and recording of sensitive administrative access.

For Ask AI, booking, phone and membership numbers in your itinerary are replaced with placeholders before sending, and email addresses, card numbers and passport numbers in itinerary notes are removed. Text you type yourself is sent as typed.

No Internet transmission or storage system can be guaranteed to be completely secure.

13. Your Rights

Depending on where you live and the law that applies, you may have rights to:

  • obtain information about our processing;
  • request access to your personal information;
  • request correction of inaccurate information;
  • request deletion;
  • restrict or object to certain processing;
  • withdraw consent;
  • receive eligible information in a portable form; and
  • complain to a privacy regulator.

Send requests to info@coyoteandpowell.com. We may request information reasonably necessary to verify identity and authority.

We will respond within the period required by applicable law. We will not discriminate against you for exercising a legally protected privacy right.

United Kingdom

UK users may complain to the Information Commissioner’s Office: https://ico.org.uk/make-a-complaint/

Canada

Canadian users may challenge our compliance through the Privacy Desk. Depending on applicable law, complaints may also be submitted to the Office of the Privacy Commissioner of Canada or the relevant provincial authority.

Québec users must be provided with the applicable French policy and French contract documents before the Service is offered to them.

Australia

Where the Australian Privacy Act applies, you may request access or correction and submit a privacy complaint to us. If the complaint is not resolved, you may contact the Office of the Australian Information Commissioner.

New Zealand

New Zealand users may request access or correction and may complain to the Office of the Privacy Commissioner of New Zealand.

California

Our use of Microsoft Clarity involves disclosure of website interaction information to Microsoft. JUNROS versions with the Meta SDK enabled, including version 1.7.3, also disclose app-measurement information to Meta. These disclosures and the recipients’ handling are described in Sections 2 and 6 and, for Clarity, our Website Cookie Policy. Clarity’s denied advertising-storage setting and the Meta SDK’s disabled advertising-identifier collection setting do not, by themselves, determine whether a disclosure is sale or sharing under applicable law.

Where California law applies and gives you a right to opt out of sale or sharing or other privacy rights, you may exercise those rights through the contact in Section 1. We do not require identity verification for an opt-out request where applicable law prohibits it. Information about Microsoft’s Clarity telemetry opt-out and its response to Do Not Track and Global Privacy Control is provided in our Website Cookie Policy. Nothing in this Policy limits rights or requirements under applicable law.

14. Children

JUNROS is intended for persons aged 13 or older.

We do not knowingly collect personal information from a child under 13. If we learn that an under-13 child created an account or submitted personal information, we will suspend the account and delete the information unless law requires another action.

A parent or guardian may contact us if they believe a child’s information has been submitted.

15. Medical and Health Information

JUNROS is not designed to collect or infer medical or health information and must not be used to upload medical records, prescriptions, diagnoses, test results, health-insurance documents or information concerning attempts to obtain health services.

If we determine that unsupported health information has been submitted, we may reject or delete it.

16. Changes to This Policy

We may update this Policy to reflect changes in law, providers, security requirements or JUNROS’s actual processing.

We will update the date above and provide notice appropriate to the significance of the change. Where law requires consent to a new purpose, recipient or category of processing, we will obtain it before the new processing begins.

17. Contact

Coyote and Powell LLC Privacy Desk
info@coyoteandpowell.com

Postal address:

8F-B Hirokoji Building
1-17-6 Ueno, Taito-ku
Tokyo 110-0005, Japan

← Back to home

© Coyote and Powell LLC — All rights reserved.