Privacy Policy - Neezy Forms

What Neezy Forms Does

Neezy Forms replaces Google Forms with a native Android app for pre-authorised users. The entire form - fields, types, validations, display rules - is driven by a Google Sheet, so the owner can add, remove or change fields without ever updating the app. Signed-in users see the same form configured in the Dropdown Spreadsheet, submit responses that write directly into the Response Spreadsheet and upload files straight to Google Drive. Access control is managed entirely through Google Sheet sharing permissions - adding or removing a user is just sharing or unsharing a Sheet. There is no backend server. Google OAuth and Sheet sharing are the sole security layer. Every submission is confirmed by the API before success is shown to the user. Duplicate submissions are blocked before they reach the Sheet.

No Backend Server

Neezy Forms 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 any of this data on any server.

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 Forms uses Google Sheet sharing permissions as the sole mechanism for controlling who can access a form. The form owner shares their Dropdown 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 Forms 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 Dropdown 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 does not collect or store any user data on any server we operate. All data the user submits flows directly between the user's device and Google services owned by the form owner.

The data handled by Neezy Forms is:

• Google account email (used only for sign-in - not stored by Neezy)
• Form field values entered by the user (written directly to the owner's Google Sheet)
• Uploaded files (written directly to the owner's Google Drive)
• Installed app version (sent only as a field in the submission row)

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 Forms only requests the drive.file OAuth scope, which restricts access strictly to files the app itself creates. Neezy Forms 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. No other version-tracking telemetry is sent anywhere.

Third-Party Services

Google Sheets API and Google Drive API (first-party Google services accessed via OAuth 2.0). No other third-party services, analytics or tracking.

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 Forms 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.readonly - Read the app configuration, form field definitions and dropdown options from the owner's Dropdown Spreadsheet.
• spreadsheets - Read the user's previous submissions and append new submissions to the owner's Response Spreadsheet.
• drive.file - Upload user-selected files to the Drive Upload Folder. This scope only grants access to files the app itself creates - no other Drive files.

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 Tracking

Neezy Forms contains no analytics SDK, no crash reporter and no tracking of any kind. We do not record user behavior, screen views or button taps. No usage telemetry is sent to Neezy or any third party.

Children's Privacy

Neezy Forms 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 Forms'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 Retention

Neezy does not retain any user data. All submitted data and files are stored directly in the owner's Google Sheets and Google Drive account. No copy is kept by Neezy.

Regulatory Compliance

Neezy Forms is designed with data minimization as a core principle. Neezy operates no server and stores no user data, which 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 Forms after changes are posted constitutes acceptance of the updated policy.