Privacy Policy - Neezy Trail Private

What Neezy Trail Private Does

Neezy Trail Private is built for the kind of work where the same people fill the same form over and over: site engineers logging daily reports, sales reps logging calls, technicians logging equipment checks, store staff logging inventory counts. It is not a one-off survey tool. Each invited person opens the app, signs in with their Google account and lands on their own home screen showing their previous submissions. They can search past entries on fields the form owner picks, open any one to read every detail, then start a new submission knowing exactly what they have already sent. Before anything is submitted, the form checks every answer against rules the form owner has set - required fields, length and value ranges, file count and size limits, allowed file types - so problems are fixed upfront. If the same answers are submitted twice by mistake, the app spots it and stops the second copy from going through. Getting started is quick: the form owner picks a ready-made template in the app, adjusts the questions to fit the work and the app creates the Google Sheet behind the form. Setting the sheet up by hand works too. Either way, the form lives inside a Google Sheet the form owner controls. Questions, drop-down choices and the rules each answer must follow are all set up in the sheet, including which fields appear on each entry in the home-screen list. Adding a question, changing a label or inviting a new person is just editing or sharing a sheet, with no app update needed when the form changes.

No Backend Server

Neezy Trail Private has no backend server operated by Neezy. The app talks directly to Google Sheets and Google Drive through Google's APIs. Form responses written by users go straight from the user's device to the owner's Google Sheet. Uploaded files go straight from the user's device to the owner's Google Drive. Neezy never sees, processes or stores your form responses or files on any server. The only data the app sends elsewhere is the diagnostic information described under Analytics and Crash Reporting.

All authentication is handled by Google Sign-In and OAuth 2.0. We do not run our own user database, session store or password system. Sign-in tokens are managed by Google and held only on the user's device.

Access Control via Google Sheet Sharing

Neezy Trail Private uses Google Sheet sharing permissions as the sole mechanism for controlling who can access a form. The form owner shares their Config Spreadsheet and Response Spreadsheet with specific Gmail addresses. Only those pre-authorized Google accounts can sign in and use the form.

We maintain no separate user list, allowlist or account database. Adding a user is sharing a Sheet with their Gmail address. Removing a user is unsharing the Sheet. Google enforces these permissions; the app does not store or duplicate them.

Data We Access

Neezy Trail Private accesses the following data on the user's device or Google account to perform its function:

• Google account email address (used for sign-in only)
• Form field definitions, dropdown options and validation rules in the owner's Config Spreadsheet (read-only)
• The user's previous submissions in the owner's Response Spreadsheet (used to detect duplicate submissions before writing a new row)
• Files the user explicitly selects to attach to a submission
• Network reachability state (used to show offline feedback)

All Sheet and Drive access is mediated by Google's OAuth 2.0 authorization. The user sees a Google consent screen on first sign-in listing the exact permissions requested.

Data We Collect

Neezy operates no server of its own and keeps no copy of your form data. The data you submit flows directly between your device and Google services owned by the form owner. The one exception is the diagnostic data described under Analytics and Crash Reporting, which goes to third-party services from Google.

The data handled by Neezy Trail Private is:

• The answers you fill into the form (sent straight to the form owner's Google Sheet)
• Any files you attach (sent straight to the form owner's Google Drive)
• The version of the app you are using. It is included with the crash and usage information described below, and is also written into your submission when the form owner has added an App Version field, so they can tell which app version an entry came from.
• Crash reports and a small set of in-app usage information, collected only to find and fix problems in the app. These reports never include your form answers, file contents, file names, name or email. Each event carries an internal identifier so events from the same user can be grouped over time; this identifier is not your name, email or any contact information.
• Your Google sign-in email is visible to the form owner. The form owner's response sheet stores each user's submissions under a per-user tab named after your email address, and the email may also appear as a column in your submission row if the form owner has chosen to record it. The form owner can also review every person's submissions inside the app, read-only.

Each item above is stored either by Google (on behalf of the form owner's Google account) or transmitted as a single field within a submission row that the form owner owns. Neezy keeps no copy.

File Uploads to Google Drive

When the user attaches a file (image or PDF) to a submission, the file is uploaded directly to a shared Drive folder under the form owner's Google Drive. The upload uses Google's Drive API; the file does not pass through any Neezy server.

After upload, an Apps Script set up by the form owner moves the file from the shared Drive folder to a private folder owned by the form owner. Neezy Trail Private only requests the drive.file OAuth scope, which restricts access strictly to files the app itself creates. Neezy Trail Private cannot read, modify or delete any other file in the user's or owner's Drive.

Force Update Mechanism

The form owner may set a minimum required app version in their configuration Sheet. When the app starts, it reads this minimum version and compares it to the installed version. If the installed version is older, the user sees a blocking update screen and cannot proceed until they update the app from Google Play.

The installed version number is also written as a field in each submission row so the owner can correlate submissions with app versions. The version is likewise included with the diagnostic data described under Analytics and Crash Reporting; it is not sent anywhere else.

Third-Party Services

Your form answers go to the form owner's Google Sheets. Files you attach go to the form owner's Google Drive. Crash reports and basic in-app usage information go to third-party services from Google so we can diagnose problems in the app. We do not sell your data, and we do not share it with any third party other than the Google services described here.

Neezy Trail Private's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Both Google services are accessed under the user's own Google account through OAuth 2.0. Their use is governed by Google's privacy policy and the form owner's own data practices for the Sheets and Drive folders they own.

OAuth Scopes

Neezy Trail Private requests the following Google OAuth scopes when the user signs in. Each scope is requested only because the listed function would otherwise be impossible.

• spreadsheets - Read the form definition (questions, drop-down options, validation rules) from the form owner's Config Spreadsheet on every form open and read your previous submissions from your own tab in the Response Spreadsheet. Append each new submission as one row to your own tab; the app never changes or deletes existing rows and never edits the header. When you create a form in the app, this permission also creates the Config and Response Spreadsheets in your own Google Drive and writes the questions you chose into them. If you own the form, the app can also list the tabs of your Response Spreadsheet and open another person's tab read-only so you can review their submissions in the app.
• drive.file - Upload files you attach to a submission into the form owner's Drive folder. When you create a form in the app, this permission also creates that form's folders in your own Google Drive. The drive.file scope only grants access to files and folders this app itself creates; the app cannot read or modify any other file in your Drive.
• drive.metadata.readonly - Read a small amount of file information, never file contents. The app checks whether you have edit access to the form owner's Response Spreadsheet and file folder so the new-submission button can be hidden when you only have view access. It also reads each saved form's name and whether you own it to label the forms in your list. It reads only the information Google Drive returns about a file (the access flags, the name and the ownership); it does not read the contents of those files or any other file in your Drive.

The user can revoke any of these scopes at any time from their Google Account permissions page ( myaccount.google.com/permissions ). After revocation the app will no longer be able to read the form configuration or submit responses.

Analytics and Crash Reporting

Neezy Trail Private collects crash reports and a small set of in-app usage information, gathered only to find and fix problems in the app. This diagnostic data is sent to third-party services from Google. It never includes your form answers, file contents, file names, name or email.

Each diagnostic event carries an internal identifier so events from the same user can be grouped over time to diagnose a problem. This identifier is not your name, email or any contact information. The app version you are running is included with this diagnostic data so we can tell which version an issue came from.

Neezy operates no server of its own, so this diagnostic data is the only information the app sends anywhere other than your form submissions, which go straight to the form owner's Google account.

Children's Privacy

Neezy Trail Private is not directed at children under the age of 13. Access requires a Google account that the form owner has explicitly shared a Sheet with, so use by children would only occur with the owner's deliberate authorization. We do not knowingly handle personal information from children under 13. If you believe a child under 13 has used the app without appropriate authorization, contact us at support@neezy.in and we will assist with deletion of any associated submission rows from the relevant owner.

Data Deletion

All submission data and uploaded files reside in the form owner's Google Sheets and Google Drive. To delete this data, the form owner can remove rows from the Response Spreadsheet and delete files from their Drive folder. Neezy holds no copy and therefore has no data to delete on a user's behalf.

To revoke Neezy Trail Private's access to your Google account, visit myaccount.google.com/permissions . To remove the app from your device, uninstall it from Google Play.

For other privacy-related requests, contact us at support@neezy.in.

Data Protection

We run no server of our own and keep no copy of your data. Your form answers and any files you attach travel over encrypted connections straight to the form owner's Google account, and the app pins Google's certificates to protect those connections. Crash and usage information travels the same way to third-party services from Google. The access the app uses to reach your sheets and files is held only in memory for the length of your session and is not stored by the app.

Data Retention

Form data: your answers and any files you attach are not retained by us at all. They are saved directly into the form owner's Google account and stay there until the form owner removes them. Diagnostic data: crash reports and usage information sent to third-party services from Google are retained per those services' standard retention windows. We do not maintain any other database of your data. You can have your form answers and files removed at any time by asking the form owner, who controls the Google Sheet and Drive folder they live in. To request deletion of the diagnostic information linked to your use of the app, contact us using the contact details listed on this site.

Regulatory Compliance

Neezy Trail Private is designed with data minimization as a core principle. Neezy operates no server and keeps no copy of your form data, collecting only the diagnostic information described under Analytics and Crash Reporting. This limits our compliance surface to the app itself and its OAuth integration with Google. We comply with the Digital Personal Data Protection Act, 2023 (India) and applicable data protection regulations.

For data subject requests (access, correction, deletion), the data controller for any given form is the form owner who set up the Google Sheets and Google Drive folder. Contact the form owner for data held in their Google account. For requests specific to the app or its OAuth integration, contact us at support@neezy.in.

Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page. Significant changes will be reflected in the app. Continued use of Neezy Trail Private after changes are posted constitutes acceptance of the updated policy.