PageSourceSearch

https://www.cropwatch.io/_app/immutable/nodes/9.DJA-I0sp.js

js cropwatch.io collected 2026-10-04 20:20:17 UTC 16,578 bytes, 107 lines download raw bytes

1import"../chunks/DsnmJJEf.js";import"../chunks/Bqse1kGK.js";import{p as f,e as y,t as g,a as s,b as v,g as w,s as t,c as l,f as d,n as a,$ as C,r as c}from"../chunks/D3VVM66Y.js";import{h as b}from"../chunks/RRYO2zhT.js";import{s as A}from"../chunks/-0EIOjA6.js";import{i as P}from"../chunks/HMGnNntM.js";import{r as T}from"../chunks/Bgr2k0MU.js";import{B as k}from"../chunks/D4ScDI4n.js";/* empty css                */var I=d(`<meta name="description" content="CropWatch, LLC's Privacy Policy, covering how personal information is handled and used, how it is managed and protected, and how disclosure requests are handled."/> <link rel="canonical" href="https://cropwatch.io/legal/privacy-policy"/>`,1),U=d(`<!> <article class="legal-doc"><h1>Privacy Policy</h1> <p>CropWatch, LLC (the “Company”) establishes this Privacy Policy (the “Policy”) as follows
2		regarding the handling of personal information of persons who use the Company’s services
3		(“Users”). The Company promotes the protection of personal information by establishing a system
4		for protecting personal information, ensuring that all employees understand the importance of
5		protecting personal information, and requiring them to follow the Company’s personal information
6		protection practices.</p> <hr/> <h2>Article 1 (Personal Information)</h2> <p>“Personal Information” means “personal information” as defined in Japan’s Act on the Protection
7		of Personal Information (Act No. 57 of 2003; the “APPI”), namely information relating to a
8		living individual that can identify a specific individual by a name, date of birth, or other
9		description contained in that information, or information that contains an individual
10		identification code.</p> <hr/> <h2>Article 2 (Purposes of Use of Personal Information)</h2> <p>The Company acquires and uses Users’ Personal Information to the extent necessary for the
11		purposes listed below. If the Company uses Personal Information beyond the scope of these
12		purposes, it will obtain the User’s consent in advance by an appropriate method.</p> <ul class="list-legal"><li>(1) To provide the Company’s services (the “Services”)</li> <li>(2) To improve or refine the Services, or to develop new services</li> <li>(3) To provide information about new features, updates, campaigns, and similar matters
13			relating to the Services, and about other services provided by the Company, including by
14			email, flyers, and other direct mail</li> <li>(4) To contact Users as necessary regarding maintenance, important notices, and similar
15			matters</li> <li>(5) To respond to feedback, inquiries, and similar communications from Users regarding the
16			Services, including verifying the User’s identity</li> <li>(6) To report to Users on their use of the Services</li> <li>(7) To ask Users to cooperate with surveys, interviews, and similar activities relating to the
17			Services, to request their participation in events, or to report the results of those
18			activities and events</li> <li>(8) To investigate and analyze Service usage histories and similar information, and to use the
19			results to improve and develop the Services and deliver advertisements</li> <li>(9) To provide Personal Information to companies and other organizations participating in
20			events hosted by the Company, based on a User’s consent or application</li> <li>(10) To identify Users who have violated the terms of use or who attempt to use the Services
21			for fraudulent or improper purposes, and to deny their use of the Services</li></ul> <hr/> <h2>Article 3 (Use of Cookies, etc.)</h2> <p>The Company uses technologies such as cookies, information collection modules, and similar
22		technologies (collectively, “Cookies, etc.”) to obtain information about Users’ access to and
23		browsing of the Services. For details about the Cookies, etc. used by the Services, please
24		review the Cookie Policy separately established by the Company.</p> <hr/> <h2>Article 4 (Management and Protection of Personal Information)</h2> <p>Personal Information will be managed strictly and, except in the circumstances listed below,
25		will not be disclosed or provided to any third party without the User’s consent. The Company
26		also takes preventive and corrective measures against risks such as unauthorized access to,
27		loss, destruction, alteration, or leakage of Personal Information, with due regard for security.</p> <ul class="list-legal"><li>(1) When it is necessary to protect a person’s life, body, or property and it is difficult to
28			obtain the User’s consent.</li> <li>(2) When it is especially necessary to improve public health or promote the sound growth of
29			children and it is difficult to obtain the User’s consent.</li> <li>(3) When it is necessary to cooperate with a national government body, local government, or a
30			person entrusted by either of them in performing duties prescribed by laws and regulations,
31			and obtaining the User’s consent is likely to impede the performance of those duties.</li> <li>(4) When otherwise permitted by laws and regulations.</li></ul> <hr/> <h2>Article 5 (Outsourcing the Handling of Personal Information)</h2> <p>The Company may outsource all or part of the handling of Personal Information to the extent
32		necessary to achieve the purposes of use. In that case, the Company will carefully assess the
33		service provider’s qualifications, include confidentiality and other relevant provisions in the
34		agreement, and exercise necessary and appropriate supervision over the service provider.</p> <hr/> <h2>Article 6 (Disclosure of Personal Information)</h2> <p>A User may request that the Company disclose Personal Information it holds. When the C
34ompany
35		receives such a request from a User, it will disclose the information to the User without delay.
36		However, the Company may withhold all or part of the information if disclosure would result in
37		any of the following circumstances. If the Company decides not to disclose the information, it
38		will notify the User of that decision without delay.</p> <ul class="list-legal"><li>(1) There is a risk of harming the life, body, property, or other rights or interests of the
39			User or a third party</li> <li>(2) There is a risk of materially interfering with the proper conduct of the Company’s
40			business</li> <li>(3) Disclosure would otherwise violate a law or regulation</li></ul> <hr/> <h2>Article 7 (Correction, etc. of Personal Information)</h2> <ul class="list-legal"><li>1. If Personal Information held by the Company is incorrect, the User may request that the
41			Company correct, add to, or delete that Personal Information (collectively, “Correction,
42			etc.”).</li> <li>2. Upon receiving a request under the preceding paragraph, the Company will conduct the
43			necessary investigation without delay. If it determines that the request has grounds, it will
44			make the Correction, etc. without delay.</li> <li>3. When the Company decides whether to make a Correction, etc. under the preceding paragraph,
45			it will contact the User without delay.</li></ul> <hr/> <h2>Article 8 (Cessation of Use, etc. of Personal Information)</h2> <ul class="list-legal"><li>1. The User may request that the Company cease using, erase, or cease providing to third
46			parties the Personal Information it holds (collectively, “Cessation of Use, etc.”).</li> <li>2. Upon receiving a request under the preceding paragraph, the Company will conduct the
47			necessary investigation. If it determines that the request has grounds, it will carry out the
48			Cessation of Use, etc. However, if the Cessation of Use, etc. would involve substantial cost
49			or is otherwise difficult, and the Company can take an alternative measure necessary to
50			protect the User’s rights and interests, it will take that alternative measure.</li> <li>3. When the Company decides whether to carry out the Cessation of Use, etc. under the
51			preceding paragraph, it will contact the User.</li></ul> <hr/> <h2>Article 9 (Procedure for Amending the Privacy Policy)</h2> <p>The Company will review the Policy from time to time and work to improve it. Except as otherwise
52		provided by laws and regulations or this Policy, the Company may amend this Policy. The amended
53		Privacy Policy will take effect when the Company notifies Users by a method specified by the
54		Company or posts it on the Company’s website.</p> <hr/> <h2>Article 10 (Compliance with Laws, Regulations, and Standards)</h2> <p>The Company will comply with Japanese laws, regulations, and other standards applicable to the
55		Personal Information it holds.</p> <hr/> <h2>Article 11 (Handling Complaints and Consultations)</h2> <p>The Company accepts complaints and consultations from Users regarding the handling of Personal
56		Information and responds to them appropriately and promptly. The Company also responds promptly
57		and appropriately to Users’ requests concerning the disclosure, correction, addition, or
58		deletion of Personal Information, or the refusal of its use or provision, and similar matters.</p> <hr/> <h2>Article 12 (Security Control Measures)</h2> <p>The Company implements organizational, physical, personnel, and technical measures to prevent
59		unauthorized access to, loss, destruction, alteration, leakage, and similar incidents involving
60		Personal Information provided by Users. These measures include restricting access to personal
61		information files, recording access logs, and implementing security measures to prevent
62		unauthorized external access. If an incident such as the leakage of a User’s Personal
63		Information occurs, the Company will promptly report it to the relevant supervisory authority in
64		accordance with the APPI and related guidelines. Following the authority’s instructions, the
65		Company will also take necessary action, including measures to prevent similar incidents and
66		recurrence.</p> <hr/> <h2>Article 13 (Company Address and Representative)</h2> <p>The Company’s United States address and representative are as follows:<br/> Address: 88 Saint Laurent Street, Epping NH 03042 USA<br/> Representative: Kevin Cantrell<br/></p> <hr/> <h2>Article 14 (Contact)</h2> <p>For privacy inquiries handled through the Company’s contact in Japan, please contact:<br/> CropWatch, LLC<br/> 806-5 Minamikata, Saito City, Miyazaki Prefecture 881-0027, Japan<br/> TEL: 080-4284-3390<br/> Email: <a href="mailto:[email protected]">[email protected]</a></p> <hr/> <h2>Article 15 (CropWatch Android App and Home-Screen Widget)</h2> <h3>1. Scope</h3> <p>This section applies to the CropWatch Android app and home-screen widget, package name
67		io.cropwatch.widget. The app signs users into an existing CropWatch account and displays
68		information from their CropWatch devices. The native Android sign-in screen does not contain a
69		registration form. CropWatch pages opened by the app in an external browser may offer account
70		creation.</p> <h3>2. Information sent to CropWatch</h3> <p>When a user signs in, the app sends the email address and password entered by the user to
71		https://api.cropwatch.io over HTTPS. The CropWatch API returns an access token, which the app
72		uses to request the user’s device and gateway information.</p> <p>
72If the API rejects an access token, the app may send the saved email address and password again
73		to obtain a new access token and continue refreshing the widget.</p> <p>The app downloads device names, device identifiers, CropWatch location and group names, current
74		sensor readings, measurement units, last-update times, online and alert status, gateway status,
75		and fleet totals. If the user selects a location or group filter, that selection is included in
76		later API requests. The Android app downloads sensor readings but does not upload sensor
77		readings.</p> <p>CropWatch location names refer to locations assigned to monitoring equipment. The app does not
78		request or access the Android device’s GPS location.</p> <h3>3. Information stored on the Android device</h3> <p>The app stores the account email address, reusable password, and access token in encrypted app
79		storage. The encryption key is managed by Android Keystore.</p> <p>The app also stores selected filters and the latest widget display data in Android’s private app
80		storage. This data can include device names and identifiers, CropWatch location or group names,
81		current readings, status and alert information, gateway totals, device-page links, and the last
82		successful update time. The widget cache is separate from the encrypted credential store. The
83		app does not keep a local history of sensor readings.</p> <p>The saved email address and password allow the widget to refresh in the background when the
84		current access token is no longer accepted.</p> <h3>4. Local retention and deletion</h3> <p>The app does not use a time-based local deletion schedule while the user remains signed in. A
85		successful sign-out deletes the saved credentials, filters, and widget cache. Removing the final
86		CropWatch widget calls the same local deletion process. Clearing the app’s storage or
87		uninstalling the app also removes its private local data.</p> <p>The app is configured to exclude its data from Android cloud backup and device-to-device
88		transfer.</p> <p>Signing out, removing the widget, or uninstalling the app deletes local Android data only. These
89		actions do not delete the user’s CropWatch account or information stored on CropWatch servers.</p> <h3>5. Home-screen display, Autofill, and browser links</h3> <p>Device information is displayed on the Android home screen. Anyone who can view the device’s
90		home screen may be able to see the widget’s contents. The Android launcher receives the widget
91		data needed to display it.</p> <p>The sign-in fields support Android Autofill. If the user enables an Autofill or password-manager
92		service, that service handles the entered information under its own privacy terms.</p> <p>Account, privacy, gateway, and device links open CropWatch pages in the user’s external browser.
93		Device-page links contain the related CropWatch location and device identifiers. The app does
94		not place the user’s password or access token in those browser links. Browser and website
95		activity is governed by the applicable CropWatch website privacy and cookie policies.</p> <h3>6. Advertising, analytics, and other recipients</h3> <p>The Android app contains no advertising, analytics, or third-party crash-reporting SDK. The
96		native app sends authentication and fleet requests directly to CropWatch services and does not
97		send information to advertising networks.</p> <p>CropWatch uses Vercel to host the API and Supabase to authenticate accounts and store Service
98		Data. These providers process information on CropWatch’s behalf as described in Article 5 of
99		this Policy.</p> <h3 id="account-deletion" class="scroll-pad">7. Server retention and account deletion</h3> <p>CropWatch retains device and sensor Service Data for the period included in the Customer’s plan,
100		up to a maximum of two years, as described in the <a>CropWatch End-User License Agreement</a>.</p> <p>
100Email <a href="mailto:[email protected]?subject=CropWatch%20account%20deletion%20request">[email protected]</a> to request deletion of a CropWatch account and server-held personal information. Include the email
101		address associated with the account, but do not include a password or access token. CropWatch reviews
102		the request under Articles 6 through 8. If the request is approved, the account is flagged for deletion.
103		Signing out, removing the final widget, or uninstalling the Android app deletes local Android data
104		only and does not submit an account-deletion request.</p> <h3>8. Security</h3> <p>The Android app restricts its API traffic to HTTPS and rejects cleartext HTTP. Authentication
105		information is encrypted locally using a key managed by Android Keystore. Cached widget
106		information and filters are kept in Android’s private app storage. App data is excluded from
107		Android cloud backup and device-to-device transfer.</p> <p class="legal-meta">Established August 1, 2024. Last updated August 24, 2026.</p></article>`,1);function _(h,p){f(p,!1),P();var o=U();b("eve2sk",e=>{var u=I();a(2),w(()=>{C.title="Privacy Policy | CropWatch"}),s(e,u)});var i=y(o);k(i,{items:[{label:"Home",href:"/home"},{label:"Privacy Policy"}]});var n=t(i,2),r=t(l(n),144),m=t(l(r));a(),c(r),a(8),c(n),g(e=>A(m,"href",e),[()=>T("/legal/EULA")]),s(h,o),v()}export{_ as component};

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.