Arventiq Privacy Policy

What Arventiq does

Arventiq is an AI-powered calendar assistant. You connect Google Calendar through OAuth and use the web dashboard, Telegram, or both to view your schedule, create and change events, set reminders, and run other scheduling actions the product supports.

Google User Data Access

When you sign in with Google and grant permission, Arventiq accesses Google user data only through the Google APIs your authorization covers (including the Google Calendar API). Our collection and use of that data complies with the Google API Services User Data Policy and the Google APIs Terms of Service, including the Limited Use requirements where they apply.

1. Data accessed

• Google Calendar data. Arventiq reads and writes calendar events and related metadata through the Calendar API. That includes event titles, descriptions, start and end times or all-day dates, time zones, recurrence rules, attendees, locations, reminders, organizer information, event identifiers, and calendar identifiers needed to perform the actions you request.
• Basic profile information. Arventiq receives the name and email address associated with your Google account from Google sign-in. Arventiq uses this to identify your account, display your identity in the product, link the correct Google Calendar access, and operate multi-account features where you connect more than one Google identity.

Arventiq requests only the minimum Google OAuth scopes required for the calendar features shown in the product: sign-in profile/email access, read-only calendar list and event visibility, and event write access. Arventiq does not request Gmail, Google Drive, Google Contacts, or other unrelated Google product access as part of the calendar connection flow.

2. Data usage

Arventiq uses Google user data exclusively to provide core product functionality:

• Show your calendars and events in the dashboard and assistant replies.
• Create, update, move, delete, or query events when you ask Arventiq to do so.
• Detect scheduling conflicts and carry out confirmations or overrides you approve.
• Send reminders and scheduling-related assistant messages tied to events you manage through Arventiq.
• Interpret natural-language requests (through Arventiq's AI processing) into concrete Calendar API actions you authorize.
• Maintain accurate links between your Arventiq account and the Google accounts you connect.

Google user data is not used for advertising, is not sold, and is not used to build unrelated products or unrelated user profiles. Arventiq does not use Google user data to train generalized artificial intelligence or machine learning models.

3. Data storage and security

• Encryption in transit. Browser and client traffic to Arventiq uses HTTPS (TLS). Connections between Arventiq's components follow encrypted transport suitable for production operation.
• Protection at rest and credential handling. Refresh tokens, secrets, and other high-risk values are stored using secure storage practices appropriate to their sensitivity. Where Arventiq persists calendar-related content or assistant conversation data needed to operate features, that storage is protected through industry-standard access controls and infrastructure security.
• Access control. Access to production systems and Google-derived user data is limited to authorized personnel and automated processes that require it. Access follows least-privilege principles. OAuth 2.0 is used so you explicitly approve Google access and can revoke it from your Google account settings at any time.

4. Data sharing

• Arventiq does not sell Google user data or personal data derived from Google APIs.
• Arventiq does not use Google user data for advertising, marketing personalization based on Calendar contents, or brokerage to data brokers.
• Arventiq shares Google-derived information only with subprocessors that process data on Arventiq's instructions and only as necessary to deliver the service—for example cloud hosting, databases, messaging (such as Telegram when you use it), and AI interpretation of your scheduling requests—or when disclosure is required by applicable law, regulation, legal process, or to protect the security and integrity of the service and its users.

Those subprocessors receive data solely to operate Arventiq's features, not for independent reuse of your Google Calendar contents beyond what Arventiq requires. See "Third-party processors" for categories.

Human access to your data

No human at Arventiq reads your Google Calendar contents by default. Human access occurs only when you explicitly request support that cannot be completed without reviewing relevant data, when Arventiq investigates security incidents or suspected abuse, or when Arventiq must comply with legal obligations.

Cookies

Arventiq uses essential cookies required for secure sign-in and session continuity in the dashboard. Those cookies stay active because the service cannot operate correctly without them.

Optional analytics cookies run only after you accept them in the cookie banner. If you reject optional cookies, Arventiq keeps only essential cookies active.

Your cookie choice is stored for up to 12 months so the banner does not reappear on every visit. You can clear browser cookies or storage to reset this choice.

Third-party processors

Arventiq uses the categories below. Processors receive data only as needed to run the service and only for core Arventiq functionality.

• Google — Calendar API and OAuth sign-in for calendar access and account connection.
• Telegram — messaging and bot features for users who use Telegram.
• Hosting and cloud infrastructure — servers, networking, and related services (specific vendors may change).
• Authentication — secure login, tokens, and session services tied to your account.
• AI processing — interpretation of scheduling requests to produce assistant responses and Calendar actions you request.

Storage and retention

Arventiq stores application data needed to run the service: linked-account metadata, OAuth refresh tokens for connected Google accounts, Telegram link state, preferences such as default calendar and time zone, and message history needed for assistant continuity and support.

Data is retained only as long as necessary to provide the service, comply with legal obligations, resolve disputes, or maintain security.

After you delete your Arventiq account or disconnect Google Calendar, Arventiq deletes or de-identifies associated data within a reasonable timeframe, except where law, security, or abuse prevention requires limited retention. Backup copies may persist briefly until they age out; Arventiq does not use those copies for active processing after deletion or disconnect.

Your choices

You can:

• Disconnect Google Calendar anytime in the product or from your Google account settings.
• Request deletion of your account or associated data (see "User deletion request").
• Email support@arventiq.io for privacy questions.

User deletion request

Disconnecting Google Calendar stops Arventiq from accessing that calendar. To delete broader account data, email support@arventiq.io from an address you control, include the Google email linked to Arventiq, and describe what you want removed. Arventiq verifies ownership when needed and deletes or de-identifies eligible data unless retention is required for security, abuse prevention, legal compliance, or backups.

Contact

For privacy questions, support, or deletion requests, contact support@arventiq.io.

Policy updates

Arventiq may update this Privacy Policy. If material changes affect how Google user data is used, Arventiq will notify users through the application or by email.