Confirmed Facts First
Public pages use confirmed company, product, and ownership information. Unconfirmed identifiers, contact details, metrics, and credentials are omitted.
Trust, policies, and platform review
A central public reference for OXEFY identity, ownership, data, security, and policy status.
This page helps reviewers, partners, customers, and platform teams understand what OXEFY operates today, what policy surfaces exist, and which items still require owner, legal, or operational decisions.
Corporate identity
OXEFY FITNESS SERVICES PVT. LTD. is the public legal display standard.
OXEFY is presented as one Indian private limited company and corporate brand operating distinct products, services, and founder-led initiatives.
Additional registration or tax identifiers are omitted until the owner approves public publication.
Review Company InformationCompany identity
Confirmed public company information
Only confirmed facts are shown here. Registration identifiers, tax details, phone numbers, and email addresses are omitted until approved for public use.
- Brand
- OXEFY
- Legal name
- OXEFY FITNESS SERVICES PVT. LTD.
- Expanded legal wording
- OXEFY FITNESS SERVICES PRIVATE LIMITED
- Company type
- Indian private limited company
- Country
- India
- Founder
- Bharat Shinde
Registered Office
Floor No. 6, Ruia ChambersIn front of Amanora Gold Towers
Amanora Park Town, Hadapsar
Pune - 411028, Maharashtra, India
Trust principles
The public site is built around conservative evidence.
These principles guide Services, Trust, Vocalis, Company Information, Contact, and draft policy routes.
User Control
AI, publishing, and platform workflows are described with user authorization, destination choice, review, and user responsibility visible.
Conservative Claims
The site avoids unsupported certifications, partner claims, provider decisions, customer metrics, and outcome promises.
Clear Dependencies
Draft policy routes and contact workflows identify the specific decisions needed before launch completion.
Policy and assurance directory
Public routes for trust topics and remaining dependencies.
Every topic below has a visible status. Draft policy routes are foundations, while company and product ownership routes carry confirmed facts.
Draft policy
Privacy
Foundation outline for privacy disclosures across the public website, Vocalis, platform connections, publishing configuration, operational logs, and user rights.
- Audience
- Users, platform reviewers, partners, and privacy reviewers
- Dependency
- Data practices, deletion process, analytics decision, privacy contact, subprocessor review, and legal review.
Draft policy
Terms
Foundation outline for service scope, account responsibilities, content ownership, integrations, payment topics, limitations, and contact routes.
- Audience
- Users, customers, platform reviewers, and commercial reviewers
- Dependency
- Product scope, payment/refund decisions, service terms, and legal review.
Draft policy
Cookies
Foundation outline for current website script posture and future cookie disclosure needs if analytics, forms, embeds, or preference tools are introduced.
- Audience
- Website visitors, privacy reviewers, and launch reviewers
- Dependency
- Analytics decision, cookie inventory, form tooling, embedded media choices, and consent decision.
Draft policy
Security
Foundation overview for access control, secret handling, provider authorization, dependency hygiene, logging, incident handling, reporting, and shared responsibility.
- Audience
- Security reviewers, API providers, partners, and users
- Dependency
- Security mailbox, incident workflow, deployment controls, product-specific security review, and owner approval.
Draft policy
Acceptable Use
Foundation for responsible use across AI, SaaS, publishing, automation, services, platform access, and user-submitted content.
- Audience
- Users, customers, reviewers, and service clients
- Dependency
- AI-use policy, enforcement process, reporting channel, product scope, and legal review.
Draft foundation
Data Deletion
Public deletion instructions for account, workspace, content, generated content, platform disconnection, contact enquiry deletion, logs, backups, verification, and limitations.
- Audience
- Users, platform reviewers, privacy reviewers, API providers, and business partners
- Dependency
- Self-service deletion tooling, privacy mailbox, identity verification, retention schedule, backup handling, and legal review.
Published foundation
Data Handling
High-level categories and purposes for account information, user content, generated content, platform metadata, publishing configuration, status events, and logs.
- Audience
- Users, platform reviewers, privacy reviewers, and security reviewers
- Dependency
- Detailed privacy text, retention decisions, deletion process, and subprocessor review.
Published foundation
Platform Access
Explains why Vocalis may request provider permissions and how provider access depends on terms, user authorization, account type, and platform review.
- Audience
- LinkedIn, Meta, Google, API, and partner reviewers
- Dependency
- Provider-specific app configuration, permission set confirmation, and contact channel.
Published foundation
Product Ownership
Summarizes legal operator and ownership statements for Vocalis, OXOFIT, OXOFIT mobile app, and BitByBharat.
- Audience
- Business-verification reviewers, platform reviewers, partners, and customers
- Dependency
- Optional publication of additional identifiers such as CIN or GSTIN if approved.
Pending operational decision
Support
Routes support, security, privacy, platform-review, product, service, media, partnership, and general business enquiries through Contact until mailboxes and form delivery are confirmed.
- Audience
- Users, customers, reviewers, partners, and media
- Dependency
- Domain email addresses, form recipient, spam-prevention strategy, and support workflow.
Published foundation
Company Information
Confirmed legal display name, expanded legal wording, registered office, founder name, operating areas, known public websites, and ownership statements.
- Audience
- Business-verification reviewers, platform reviewers, partners, and customers
- Dependency
- Owner decision on optional publication of registration or tax identifiers.
Vocalis trust summary
Product, platform, data, and responsible-use context are public.
OXEFY provides public review context for platform and API providers without representing external provider decisions as complete.
Data and user-control overview
Vocalis describes account/workspace information, user-provided content, generated content, brand/persona settings, connected-platform metadata, publishing configuration, delivery status, errors, and operational logs at a high level.
Users remain responsible for authorization, destination selection, content review, and platform compliance.
Review Vocalis data handlingReviewer quick reference
What reviewers can inspect today.
This checklist and matrix support review conversations while external provider decisions, final policy text, and confirmed contact channels remain separate dependencies.
- Legal operator is visible on Company Information and Vocalis.
- Product ownership statements are linked from Products, Vocalis, and Trust.
- Policy routes exist and clearly identify draft/foundation status.
- Vocalis explains user authorization, user review, platform permissions, and provider dependencies.
- Contact route exists without fake mailboxes, phone numbers, or non-working form delivery.
- Unresolved legal, privacy, security, and operational dependencies are documented.
| Reviewer | Main concern | Public route | Status | Remaining dependency |
|---|---|---|---|---|
| Business identity, requested platform access, user authorization, destination control, and responsible content publishing. | /vocalis/#approval-context | Published foundation | Provider-specific app review inputs and confirmed contact channel. | |
| Meta | Platform permissions, user control, content responsibility, data-use explanation, and policy route visibility. | /vocalis/#integrations | Published foundation | Provider-specific app configuration and privacy-policy completion. |
| OAuth purpose, requested scopes, user consent, data categories, privacy route, and security route. | /trust/#policy-directory | Published foundation | OAuth scope confirmation and final privacy/security text. | |
| Payment provider | Legal operator, product/service description, terms, refund path if payments are introduced, and contact route. | /company-information/ | Pending legal review | Payment model, refund decision, legal terms, and operational contact channel. |
| API provider | Use case, authorization model, data categories, responsible use, and user control. | /vocalis/#user-control | Published foundation | Provider-specific permission set and technical configuration. |
| Customer security reviewer | Security principles, data categories, contact route, incident path, and unresolved security dependencies. | /security/ | Draft policy | Security mailbox, incident workflow, deployment controls, and technical review. |
| Business partner | Legal identity, operating areas, ownership statements, services fit, and contact path. | /trust/#product-ownership | Published foundation | Commercial terms and confirmed contact workflow. |
Product ownership
One operator, distinct products and initiatives.
OXEFY is presented as one legal company and corporate brand with distinct products and initiatives.
- Vocalis is developed and operated by OXEFY FITNESS SERVICES PVT. LTD.
- OXOFIT and the OXOFIT mobile application are OXEFY products.
- The OXOFIT mobile application is an OXEFY product. Selected software development and app-store operations have been supported through an external development collaboration.
- BitByBharat is a founder-led publishing and knowledge platform created by Bharat Shinde.
Ownership routes
Policy status
Legal-policy routes are visible foundations.
This table records route status and dependencies without presenting incomplete legal text as complete.
| Topic | Status | Route | Dependency |
|---|---|---|---|
| Privacy | Draft policy | /privacy/ | Data practices, deletion process, analytics decision, privacy contact, subprocessor review, and legal review. |
| Terms | Draft policy | /terms/ | Product scope, payment/refund decisions, service terms, and legal review. |
| Cookies | Draft policy | /cookies/ | Analytics decision, cookie inventory, form tooling, embedded media choices, and consent decision. |
| Security | Draft policy | /security/ | Security mailbox, incident workflow, deployment controls, product-specific security review, and owner approval. |
| Acceptable Use | Draft policy | /acceptable-use/ | AI-use policy, enforcement process, reporting channel, product scope, and legal review. |
| Data Deletion | Draft foundation | /data-deletion/ | Self-service deletion tooling, privacy mailbox, identity verification, retention schedule, backup handling, and legal review. |
| Data Handling | Published foundation | /vocalis/#data-handling | Detailed privacy text, retention decisions, deletion process, and subprocessor review. |
| Platform Access | Published foundation | /vocalis/#approval-context | Provider-specific app configuration, permission set confirmation, and contact channel. |
| Product Ownership | Published foundation | /company-information/ | Optional publication of additional identifiers such as CIN or GSTIN if approved. |
| Support | Pending operational decision | /contact/ | Domain email addresses, form recipient, spam-prevention strategy, and support workflow. |
| Company Information | Published foundation | /company-information/ | Owner decision on optional publication of registration or tax identifiers. |
Compliance position
Transparent foundations without unsupported compliance claims.
OXEFY aims to operate transparently. Platform access remains subject to provider terms and review. Policies describe current practices and intended controls based on repository-confirmed behavior.
Compliance obligations may depend on product configuration, geography, data, customer context, and provider terms. Customers and partners may need their own legal review.
Deletion and privacy routes
The Data Deletion route explains current request initiation, platform disconnection guidance, backup limitations, and operational gaps without claiming a self-service deletion endpoint.
Review Data Deletion InstructionsSecurity and support route
Use Contact while dedicated mailboxes and form delivery are pending.
Security, privacy, support, platform-review, product, service, partnership, media, and business enquiries are routed through Contact until domain mailboxes and delivery workflow are confirmed.
Open ContactContact categories
- Product enquiry
- Vocalis enquiry
- Services enquiry
- Partnership enquiry
- Platform or API review
- Privacy enquiry
- Security report
- Media enquiry
- General business enquiry
Trust FAQ
Trust and policy questions.
Answers distinguish between confirmed public facts, published foundations, and remaining launch inputs.
Is the Trust Centre a final legal-policy hub?
No. It is a public foundation that links confirmed company and product information while legal-policy routes remain pending owner and legal review.
Where can reviewers verify who operates Vocalis?
The Company Information and Vocalis pages state that Vocalis is developed and operated by OXEFY FITNESS SERVICES PVT. LTD.
Where are privacy and security details?
Privacy and Security routes exist as foundation pages, while Vocalis also includes high-level data-handling and security-principle sections.
Does the website publish direct support emails?
No. Domain-based mailboxes and contact delivery are not yet confirmed, so enquiries route through the Contact page without fake contact details.
What still needs completion before launch?
Final legal policy text, domain mailboxes, form delivery, data deletion instructions, retention decisions, and some provider-specific review inputs remain open.
Review next steps
Continue with company identity or contact routing.
Company Information carries confirmed public facts. Contact explains enquiry categories without publishing unconfirmed mailboxes or a non-working form.