Legal
Privacy Policy
This Privacy Policy explains how DuoCloud Infotech Private Limited handles information in connection with Qevric, including the Qevric website, business workspace, member portal, public storefront pages, invoice and receipt pages, mobile apps, support communications, and related product flows.
Contents
Sections in this Privacy Policy.
1. What Qevric Is
Qevric is business software for fitness, wellness, and related businesses. Businesses use Qevric to manage subscriptions, billing, invoices, payments, member access, public storefronts, member portal flows, staff access, notifications, and connected day-to-day operations.
Business customers decide what information they enter into Qevric and how they use Qevric for their own members, leads, staff, and operations.
2. Roles And Responsibilities
For information a business customer enters about its members, leads, staff, customers, storefront content, invoices, payments, and operations, Qevric generally handles that information on behalf of the business customer.
Qevric is responsible for its own business operations, including account administration, public website analytics, Qevric subscription billing, support, security, legal compliance, and service-provider management.
- Each business customer decides what information it collects and enters into Qevric.
- Each business customer is responsible for giving required privacy notices to its members, leads, staff, and customers.
- Each business customer is responsible for obtaining required consents, permissions, legal basis, or other authority required by law.
- Each business customer is responsible for ensuring its staff and admins use Qevric lawfully.
- Each business customer is responsible for complying with laws that apply to its business, services, members, payments, refunds, taxes, and communications.
3. Information We Process
Qevric handles information needed to provide, secure, support, bill, and improve the service. This includes the categories below.
3.1 Account And Staff Information
We may handle information about business owners, admins, and staff, including names, email addresses, phone numbers, roles, email verification status, account status, login and security details, permissions, branch access, staff invitations, notification preferences, and related timestamps.
We also handle authentication and security information such as password hashes, protected token records, failed login attempts, lock state, and session-related records.
3.2 Business And Workspace Information
We may handle business profile and workspace information, including business name, public URL slug, logo or image references, business activities, currency, timezone, address, tax or business identifiers, branch details, invoice and receipt numbering settings, tax settings, billing settings, member portal settings, public enrollment settings, storefront settings, and workspace setup.
We may also handle Qevric billing information, including plan, trial, grace period, subscription status, pending plan changes, Stripe subscription references, payment-provider account identifiers, payment-provider setup/readiness, and provider onboarding status.
3.3 Member, Lead, And Member Portal Information
Business customers may use Qevric to handle information about members, leads, and member portal users. This may include names, gender, phone number, country code, email address, address, date of birth, emergency contact, notes, profile photos, home branch, tags, archive or prospect status, import records, portal account details, portal activation and password reset records, lead source, lead status, enrollment records, selected plans, selected branches, and selected batches.
Qevric does not currently provide a medical record system. Businesses must not use Qevric to store sensitive medical records, biometric data, or health-record data unless Qevric later expressly supports that use and appropriate legal terms are in place.
3.4 Operational Information
We may handle operational information, including plans, add-ons, retail items, service types, prices, batches or class groups, service-provider records, subscriptions, start and end dates, next billing dates, subscription status, cancellation records, freezes, discounts, collection mode, assigned branch, assigned batch, assigned service provider, session balances, session usage, attendance or visit records, reversal records, operational notes, dashboard summaries, and related analytics.
Subscription-at-risk indicators and similar product metrics are treated as ordinary business analytics unless future AI features are separately introduced.
3.5 Billing, Payment, Invoice, Credit, Refund, And Receipt Information
We may handle invoices, invoice line items, descriptions, quantities, prices, taxes, discounts, totals, balances, issue dates, due dates, statuses, PDFs, receipt records, public invoice or receipt links, public access tokens, checkout/payment collection attempts, payments, allocations, credits, refunds, refund allocations, amounts, currency, payment dates, receipt numbers, refund reasons, and payment-provider details.
Qevric does not store full card numbers or full bank account details directly. At launch, Qevric uses Stripe-hosted or payment-provider-hosted payment flows and stores provider references and limited details, such as customer IDs, payment method type, brand, last4, invoice status, payment status, refund status, subscription status, and related provider identifiers.
Businesses may also enter offline payment details, such as reference numbers, bank names, cheque details, UPI details, card last4, authorization codes, and notes.
3.6 Communications, Notifications, And Support Information
We may handle transactional email records, support emails, in-app notifications, notification categories, notification messages, target details, read state, email delivery status, push notification preferences, and mobile push delivery details.
Qevric uses Firebase Cloud Messaging / Google Firebase for operational mobile push notifications for business owners, admins, and staff on supported mobile apps. Push notification flows may handle device IDs, platform, environment, encrypted Firebase Cloud Messaging device tokens, protected token records, app version, build number, operating system version, device model, active/revoked state, provider message IDs, provider error details, delivery status, and limited notification details needed to send and track safe notifications.
Qevric does not currently use mobile push for member-facing push, marketing push, SMS, WhatsApp, digest delivery, Firebase Analytics, Crashlytics, Performance Monitoring, Remote Config, App Distribution, or Firebase delivery-data export to BigQuery.
3.7 Website Analytics And Cookies
Qevric uses PostHog for restrained analytics on public marketing, learn, support, contact, privacy, and terms pages.
Current analytics may include page path, page type, referrer host, campaign tracking values, selected call-to-action interactions, support-contact intent, and sanitized destination or path values.
Analytics tools may use cookies or similar browser storage depending on production configuration and browser settings. Visitors may be able to limit cookies through browser settings, though doing so may affect some website behavior.
- Automatic capture of all page interactions is disabled.
- PostHog's automatic pageview capture is disabled.
- Session replay is disabled.
- Qevric does not currently use this PostHog setup on authenticated app routes, dashboard routes, admin routes, checkout routes, public invoice or receipt token pages, member portal routes, storefront preview routes, or login/register form internals.
- Long-term first-visit campaign tracking is not implemented.
3.8 Technical, Security, And Reliability Information
We may handle technical and security information such as audit logs, duplicate-request prevention records, request hashes, response codes, request IDs, error details, operational timestamps, sync/freshness details, cache details, server refresh details, worker and billing job state, retry status, platform/admin operational records, and troubleshooting records.
4. How We Use Information
Qevric uses information to:
- Provide, operate, maintain, and secure the service.
- Create and manage business workspaces, accounts, staff access, roles, and permissions.
- Support member, lead, portal, storefront, subscription, invoice, payment, credit, refund, receipt, attendance, session usage, and operational flows.
- Handle Qevric billing, trials, plan changes, cancellation flows, and payment-provider integrations.
- Generate invoices, receipts, PDFs, notifications, transactional emails, and support responses.
- Provide public storefront, invoice, receipt, checkout, and member-portal flows requested or configured by business customers.
- Detect, prevent, investigate, and respond to security, fraud, abuse, payment, and operational issues.
- Maintain reliability, troubleshoot errors, support customers, and improve product functionality.
- Comply with legal obligations, enforce terms, resolve disputes, and protect Qevric, customers, users, members, and third parties.
- Analyze public website interest and support/contact intent through restrained public-site analytics.
6. Payment Providers
Payments may be handled by Stripe or other payment providers added later. Payment providers handle payment information under their own terms, privacy policies, compliance programs, financial-provider requirements, and legal obligations.
Qevric stores only payment-provider references and limited payment details, not full card or bank details directly.
Customers must review and comply with applicable payment-provider terms before enabling payment flows.
7. Customer Responsibilities
Business customers are responsible for:
- The information they enter, upload, import, publish, or collect through Qevric.
- Giving required privacy notices and obtaining required consents, permissions, legal basis, and authority.
- Ensuring staff users and admins use Qevric lawfully and with appropriate permissions.
- Complying with laws that apply to their business, members, services, communications, taxes, refunds, disputes, and payment obligations.
- Obtaining required parent/guardian consent and legal authority before entering or processing data about minors.
- Avoiding sensitive medical, biometric, health-record, illegal, abusive, or payment-provider-prohibited content or activity unless expressly supported by Qevric and legally permitted.
8. Retention
Qevric keeps information for as long as reasonably needed to provide the service, support customers, maintain security, run billing and operations, comply with legal obligations, resolve disputes, and enforce agreements.
Exact retention periods may vary by data type, provider requirements, legal obligations, and operational needs.
- Workspace, account, operational, billing, and support data may be retained while the customer account is active.
- After a verified workspace deletion request, Qevric will delete or de-identify workspace/member data when it is operationally feasible.
- Qevric may retain billing, tax, security, fraud-prevention, audit, legal, payment-provider, and compliance records as required or permitted by law.
- Backup, log, and security records may remain for a limited period according to operational and legal requirements.
9. Security
Qevric uses administrative, technical, and operational controls designed to protect the service and the information handled through it. Examples include password hashing, protected token records, encrypted Firebase Cloud Messaging token storage, role and permission controls, branch access controls, login protections, backend validation, public-link access controls, and operational audit records.
No service can guarantee absolute security. Customers are responsible for keeping their credentials, devices, staff accounts, and workspace access secure.
10. International Processing
Qevric is operated by an Indian company and is intended for global customers. Qevric and its service providers may process, transfer, store, or access information in India and other countries where Qevric, its service providers, payment providers, infrastructure providers, and support operations are located.
11. Your Rights And Requests
Customers can use in-app features to access and export certain workspace information. Qevric does not currently provide exports by email or support request. Workspace deletion can be requested through support by the workspace owner.
Individuals whose information is managed by a business customer should generally contact that business customer first. Qevric may assist the business customer with privacy requests when required or appropriate.
Privacy requests can be sent to support@qevric.com.
12. Minors
Qevric is not intended to contract directly with children. Business customers may store or process minor member data only when they have required parent/guardian consent and legal authority.
13. OpenAI And Internal Blog Generation
Qevric uses OpenAI for internal automated blog-writing flows only. Qevric's current policy is that OpenAI blog generation must not use customer data, member data, staff/admin user data, payment data, support data, analytics data, private operational data, or any other data from the Qevric app.
OpenAI is described separately in this policy because Qevric's current use is limited to internal Qevric marketing blog generation, not customer workspace, member, payment, support, analytics, or product automation flows.
Qevric's current OpenAI use involves human review before use and does not include customer-facing AI, customer workspace flows, member flows, risk scoring, payment decisions, or support automation.
If any AI flow later handles customer, staff, member, payment, support, analytics, operational, or sensitive data, Qevric will update or add relevant privacy, terms, provider, retention, and product notices before enabling that flow.
14. Changes To This Policy
Qevric may update this Privacy Policy as the product, providers, laws, and business practices evolve. Updated versions will be posted with a new last-updated date. Where required, Qevric will provide additional notice.
15. Contact
DuoCloud Infotech Private Limited
326, Nagarjun Colony, Jaripatka, Nagpur, Maharashtra, India - 440014
support@qevric.com
Related Legal Pages
Review Qevric terms alongside this Privacy Policy.