Privacy Policy

• Product: InProQu (https://app.inproqu.com)
• Effective date: July 2026

Controller (SaaS account data): Joseph Biros (“InProQu,” “we”).
Contact: [email protected] · Postal: Amaris Homes Molino 4 · [email protected]

This Policy explains how we process personal data when you use InProQu. It should be read with our Terms of Service, Cookie Policy, and (for business customers) Data Processing Addendum.

Important role split

1. Data we process

1.1 Account and workspace data (controller)

• Identity: name, email address, password hash (if password login), OAuth identifiers

• Security: MFA secrets (encrypted), backup codes, login lockout state, and session revocation metadata

• Workspace membership, roles, invites

• Billing identifiers and plan status (via our payment partner, e.g. Polar)

• Support communications you send us

• Platform admin flags (if applicable)

1.2 Customer Content (typically processor)

As directed by you:

• Company profiles (names, logos, addresses, phones, emails)
• Client records (names; contact email/phone/notes may be encrypted at rest)
• Proposal/document content, variables, attachments metadata
• Electronic signatures, acceptance records, and related evidence
• Knowledge-base documents you upload (e.g. PDF, CSV, DOCX)
• Integration tokens and configuration you connect
• AI chat/prompts you run inside the product (if AI is enabled)

1.3 Automatically collected

• IP address (often stored as a one-way hash with a server salt for view/engagement/audit events — not retained as raw IP in those logs)
• User agent, referrer (for document views / audit)
• Approximate device/browser data needed for sessions
• Email open/click events for messages you send through the product (tracking tokens)
• Diagnostic logs required to operate and secure the Service

1.4 Data we do not sell

We do not sell personal data. We do not use Customer Content to train public AI models. If you enable a third-party AI integration with your own API key or OAuth, that provider’s processing is under your configuration and their terms.

2. Sources

• Directly from you or your workspace users
• Identity providers (Google, Microsoft) when you use social/SSO login
• Your connected integrations
• Recipients who open share links or tracking pixels you enable
• Payment/billing providers for subscription events

3. Purposes and legal bases (where GDPR/UK GDPR apply)

Where consent is required (e.g. certain cookies or marketing), we will request it.

4. Sharing

We share personal data only as needed with:

• Infrastructure and platform vendors listed in Subprocessors (hosting, database, CDN/security, transactional email, SaaS billing)
• Your integrations when you connect them (email, storage, CRM, AI, analytics on your share pages, payment processors for your invoices)
• Professional advisors under confidentiality
• Authorities when required by law
• Successors in a merger or asset transfer (with notice where required)

We do not use your Customer Content for third-party advertising.

Workspace-level GA4 / Meta Pixel tags on public proposal pages, if you enable them, are your tags; you are responsible for notices/consent to your viewers.

5. Google API services and Limited Use

When you connect Google integrations (for example Gmail, Google Drive, Google Sheets, Google Calendar, Google Contacts) or sign in with Google, InProQu accesses Google user data only as needed to provide or improve those user-facing features that you enable.

Limited Use. InProQu’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

5.1 Data we access (Google)

Depending on which Google connection you enable, we may access:

• Sign-in: basic profile identifiers and email address
• Gmail (gmail.send): ability to send email you initiate (message content you compose in InProQu)
• Google Contacts (contacts.readonly): contact names and email addresses (and related contact fields returned by the API) for import into your workspace
• Google Calendar (calendar.events): calendar event details you create or update through InProQu
• Google Drive / Sheets (drive.file): only files created by InProQu or that you open with InProQu (for example an export spreadsheet or a saved proposal PDF), including file metadata and content needed to create or update those files

We do not request access to your entire Drive or all of your spreadsheets. We do not use aggregated/anonymized Google user data for advertising or unrelated analytics products.

5.2 How we use Google data

We use Google user data solely to provide or improve the user-facing feature you enabled—for example sending a proposal email, importing contacts as clients, creating a follow-up calendar event, exporting clients/proposals to a spreadsheet, or saving a PDF to Drive. We do not use Google user data for lending, credit decisions, or targeted advertising.

5.3 Sharing and transfer

• We do not sell Google user data.
• We do not transfer Google user data to data brokers or advertisers.
• We may process Google user data on our hosting infrastructure and subprocessors listed in Subprocessors solely to operate the Service.
• We do not transfer Google Workspace API user data to third-party AI/ML services for them to train their models. If you separately connect an AI provider (BYOK) and choose to include workspace content in a prompt, that content is sent under your AI provider configuration; we do not use raw or derived Google Workspace API user data to train generalized AI/ML models.

5.4 Protection

OAuth tokens and related integration secrets are stored encrypted at rest. Access is limited by workspace authentication and authorization. Transport uses HTTPS/TLS. See also section 8 and our Security and AI data use page.

5.5 Retention and deletion

• OAuth tokens: retained while the Google integration remains connected so the feature can operate; deleted or invalidated when you disconnect the integration in InProQu or revoke access in your Google Account.
• Imported contacts / related workspace records: retained as Customer Content in your workspace until you delete them or close the workspace/account, subject to backup cycles and legal holds.
• Files in Google Drive/Sheets/Calendar/Gmail: remain in your Google account under Google’s retention controls; disconnecting InProQu stops further API access but does not automatically delete files or emails already created in Google.

You can disconnect Google integrations at any time in Integrations. Revoking access in your Google Account also stops further API access.

6. International transfers

We may process data in countries where we or our subprocessors operate. Where required, we use appropriate transfer mechanisms (e.g. SCCs) as described in the DPA and subprocessor terms.

7. Retention

• Account data: for the life of the account and a reasonable period after deletion for backups, disputes, and legal retention

• Customer Content: until you delete it or close the workspace/account, subject to backup cycles and legal holds

• Security/audit logs: typically retained for a limited operational period

• Share and email tracking events: retained while useful for the document/workspace or until purged

8. Security measures (summary)

• TLS in transit for the web app
• Encryption at rest for secrets and selected sensitive tenant fields
• Access controls, workspace isolation, session controls (idle/absolute timeouts; credential version revocation)
• Password hashing; optional MFA; rate limiting and lockout
• Upload type checks; HTML sanitization

Details may evolve; see also product security documentation. No measure is perfect — report issues to [email protected] or [email protected].

9. Your rights

Depending on your location, you may have rights to access, correct, delete, port, restrict, or object to certain processing, and to withdraw consent.

• Account users: If you sign in with email and password (or personal Google/Microsoft, without company SSO), Settings → Account includes self-service deletion. We email a confirmation link; the account is not deleted until you open that page and confirm. Company SSO accounts are managed by a workspace admin (Settings → Team). Owners of a paid Business workspace close it through Billing (or support), not Account deletion. You may also email [email protected]. We aim to complete requests within 30 days. Workspaces where you are the only member are deleted with the account. Team workspaces remain for other members. Billing, tax, and signature evidence may be retained where the law requires it, and backups lag for a limited cycle.
• Your clients / document viewers: contact you (the workspace customer) first; we will assist you as processor under the DPA.

You may lodge a complaint with a supervisory authority where applicable.

10. Children

The Service is for business use and is not directed to children under 16 (or higher age required locally). We do not knowingly collect children’s data.

11. Automated decisions

We do not make solely automated decisions that produce legal or similarly significant effects about you without human involvement as part of core account eligibility, other than routine fraud/security blocks.

12. Cookies

See the Cookie Policy.

13. Changes

We will post updates to this Policy and revise the effective date. Material changes may be notified by email or in-product notice.

14. Contact

[email protected] · Joseph Biros · Amaris Homes Molino 4