Privacy & Google Sign-In

Google sign-in information

When you choose to sign in with Google, Reqelio requests only the openid, profile, and email permissions. Google provides an account identifier, email address, email verification status, and basic profile information such as your display name.

Reqelio stores your Google account identifier, email address, and display name in its application database to create or identify your Reqelio account and sign you in. The Google identifier lets Reqelio recognize the same account on a later visit. Linking Google to an existing password account requires an explicit linking action from the signed-in account.

Reqelio does not receive your Google password and does not store Google OAuth access or refresh tokens in its database or session cookie. Google sign-in does not grant access to Gmail messages, Google Drive files, contacts, or calendars. Sign-in information is not used for advertising or automatically sent to Gemini.

Accounts, workspaces, and client requests

Reqelio stores the account and workspace information you provide, including names, email addresses, memberships, and invitation records. If you create a password account, the password is stored as a password hash. Templates, project details, client contact information, answers, approvals, and activity records are stored to provide the client intake workflow.

Uploaded files are kept in private object storage and accessed through temporary signed links. Authorized workspace members can access their workspace’s projects. A client’s private request link grants access to that request, including to someone the link is forwarded to. Share client links only with their intended recipients.

Hosting, database, and storage services process information to operate Reqelio. The application uses HTTPS for data in transit. More information about access and storage is available on our security page.

Optional WhatsApp project notifications

Reqelio stores the client phone number and consent record, including when, how, and by whom consent was recorded, to manage the WhatsApp notification channel.

When WhatsApp is enabled for a project and the client's consent is recorded, Reqelio sends the recipient phone number and approved message-template parameters to Telnyx for delivery through Meta's WhatsApp platform. Telnyx and Meta process these details to deliver the message. These parameters include the client name, project name, completion percentage for reminders, and private project link. The link grants access to the project.

Reqelio records provider message identifiers and delivery status updates to show whether a notification was accepted, delivered, or failed. WhatsApp delivery receipts use a hash of the recipient phone number. Reqelio's current integration does not store incoming WhatsApp chat content or send automatic replies.

Clients can pause project notifications using the notification preferences accessible from their private project link. Workspace users can change notification channels and schedules in notification settings.

AI assistance is a separate choice

Signing in with Google does not start an AI request or send your Google sign-in profile to Gemini. When you explicitly ask for an AI template draft or send an AI interview message, the relevant prompt, template or project questions, existing answers, and conversation content are sent to Google Gemini to generate suggestions.

Interview messages and proposed answers are stored for review. Project answers are saved only after the client confirms the selected suggestions. An AI template draft becomes a saved template only when you choose to save it. The current text AI workflow does not include uploaded file contents in its provider requests.

You can use manual questions and answers without AI. Do not include passwords, recovery codes, payment card numbers, API keys, or other account credentials in project content or AI messages.

Payments through Paddle

When you choose to purchase a paid subscription or AI add-on, Paddle handles checkout and payment details as merchant of record. Reqelio sends the account email, display name, and a billing reference to Paddle to associate the purchase with your account and workspace.

Reqelio stores Paddle customer, transaction, and subscription identifiers, the selected plan, billing status and period, and payment-event records to manage access, AI add-ons, and billing support. Reqelio does not receive or store your full payment card number or card security code.

Paddle explains its own handling of purchase, payment, fraud-prevention, and tax information in its privacy notice. Paddle Privacy Notice

Cookies and operational information

The platform uses a necessary session cookie to keep you signed in. Service infrastructure may process request metadata, including IP addresses, to deliver and protect the service.

The public marketing website uses Google Analytics only after you allow analytics. Until then, its Google tag is not loaded and no analytics requests are sent to Google. Your accepted or rejected choice is stored in a cookie on the marketing website for 180 days.

If you allow analytics, Google processes visits to our public pages, cookie identifiers, and technical information such as browser, device, and approximate location. Analytics cookies last up to 180 days. Page addresses contain only approved public paths: query strings and fragments are not sent. Referrals contain only the external website origin, without a path, query, or fragment; referrals from Reqelio and its platform are excluded. We do not send names, email addresses, account IDs, form answers, project data, or template content. Sign-in, payment, platform, and private client pages are not measured. Advertising features and enhanced measurement are disabled.

You can reject analytics without affecting the service, or change your choice using Analytics preferences in the footer. Withdrawing consent stops analytics, clears its marketing-site cookies, and reloads the page. It does not erase data already received by Google.

Google Privacy Policy

Stored information and removal requests

Account and workspace records remain in the application database. Completing or archiving a project does not delete its content. Database backups are maintained for operational recovery. Signing out or removing Reqelio’s permission in your Google account does not itself delete information already stored in Reqelio.

For questions or a request to remove your account data, contact: emre@ekara.dev. Include the Reqelio account email and the workspace concerned. There is currently no self-service account-deletion control.