1. Introduction to Jepely

Welcome to Jepely (“Platform”, “we”, “our”, or “us”). Jepely is a cloud-based Software-as-a-Service (SaaS) automation architecture. We provide specialized business tools designed to automate customer relationship management, manage conversational interactions, and deploy artificial intelligence configurations across multi-channel communication pipelines.

Our automation core encompasses:

2. Information We Collect

To provide stable automation services, collect metrics, and maintain continuous API connection handshakes, we gather specific account and operational data:

A. Account Configuration Assets

• Account credentials including your Name, Business Title, and Email address.
• Secure OAuth tokens authorized to map third-party accounts.
• User-generated workflow variables, training knowledge documents, and response logic rules.
• System operational transaction logs.

B. Meta Platform Data Processing

When users securely authenticate their Meta accounts to activate platform tasks, Jepely processes necessary platform streams through secure official Graph API structures. This data processing strictly covers:

• Facebook Page IDs, App permissions, and unique instance credentials.
• Incoming real-time messaging payloads via secure application endpoints.
• Public comment data strings published on connected profiles.
• WhatsApp Business Account configurations and interaction transaction logs.
• Secure OAuth Access Tokens and system Webhook event structural arrays.

C. Google API Data Processing & Workspace Integration

When users connect their Google Accounts to utilize our Google Sheets CRM, BI Dashboard Builder, and Google Drive integrations, Jepely processes data strictly via official Google OAuth 2.0 protocols. This processing encompasses:

• OAuth Tokens: Encrypted store of Google OAuth Access Tokens and Refresh Tokens required to maintain persistent background service connections.
• Google Spreadsheet Matrices: Reading cell values, structural layouts, worksheet tabs, headers, and metadata strictly to render dashboard components, execute user-defined CRM tasks, or construct AI-driven business intelligence reports.
• Google Drive File Operations: Duplicating, organizing, or managing access permissions for spreadsheets strictly designated by the user within the CRM environment.
• Uploaded Dataset Archives: Temporary file storage and extracted JSON representations of user-uploaded datasets processed strictly for AI analysis and visualization.

Jepely handles this data strictly as a processor on behalf of the user to fulfill the automation task. We do not scan, retain, or read private conversations beyond the functional technical requirements.

3. Google User Data Policy & Limited Use Compliance

Jepely's use and transfer to any other app of information received from Google APIs will adhere to the Google API Service User Data Policy, including the Limited Use requirements. Specifically:

• We only request access to the Google API scopes necessary to execute user-requested actions (such as managing designated Google Sheets or Drive files).
• We do not transfer or share your Google user data with third parties unless necessary to provide or improve our core CRM features, comply with applicable laws, or as part of a merger/acquisition with explicit notice.
• We strictly do not use Google user data for serving advertisements, personalized marketing, or retargeting.
• Human agents are prohibited from reading your Google Sheets data unless you explicitly provide consent for technical support, it is required for security investigations, or it is required to comply with applicable laws.
• Data obtained through Google Workspace APIs is never utilized to train generalized AI or Machine Learning models without explicit prior authorization.

4. Purpose of Processing Data

We process data to maintain service continuity and run your operations:

• Executing accurate real-time triggers to run automated responses.
• Syncing communications across multiple messaging channels to a single client dashboard.
• Reading and updating Google Spreadsheet records in real-time based on automated CRM dispatchers.
• Extracting dataset metrics to build standalone HTML Business Intelligence dashboards.
• Monitoring engine response health and executing bug fixes.
• Ensuring platform integrity and preventing system abuse or security violations.

5. Data Sharing & Zero Commercialization Policy

Jepely enforces an absolute non-commercialization data policy. **We never sell, distribute, trade, or monetize user data, message content, or spreadsheet records.** Data transmission only occurs to bridge system events to the authorized messaging or Google Workspace channels, or when mandated by strict legal court processing structures.

6. Security Architecture

We protect user data through rigorous security engineering:

• Enforced 256-bit SSL/HTTPS transmission encryption on all connections.
• Salted cryptographic hashing routines for system parameters, Google OAuth credentials, and access tokens.
• Isolated multi-tenant database designs to guarantee data compartmentalization.
• Continuous security firewalls and proactive cloud network logs monitoring.

7. Data Retention, Revocation, and Account Liquidation

Your configurations, OAuth refresh tokens, and cached dataset matrices are actively maintained as long as your service subscription remains active. Users maintain total authority over their data:

• Token Revocation: You can disconnect Jepely’s access to your Google Account at any time via your Google Security Settings or directly inside the Jepely CRM panel.
• Account Liquidation: Upon triggering an explicit Account Deletion inside the management panel, Jepely completely purges all authorized database tokens, custom rules, uploaded dataset archives, and generated dashboard files within 30 days.

8. User Obligations & Terms Compliance

By operating Jepely, users agree to the following terms:

• To use chatbot and workspace automation responsibly and avoid any broadcast behavior that constitutes spamming.
• To strictly comply with Meta’s Platform Terms, WhatsApp Business Policy, Google API Terms of Service, and individual channel guidelines.
• To refrain from using the platform for any deceptive, illegal, or abusive operations.

9. Third-Party API Limitation of Liability

Our automation functionalities depend heavily on the availability of third-party Application Programming Interfaces (APIs). Jepely holds no responsibility for temporary platform disruptions, delayed webhooks, or features rendered inoperable due to systemic updates, API suspensions, or programmatic revisions introduced by external networks (e.g., Meta, Google Workspace, Facebook, Instagram, WhatsApp, Telegram).

10. Contact & Support Center

For support, API configuration queries, or detailed privacy audits, reach our SaaS support deck:

Jepely Support Center
Email: [email protected]
Website: https://jepely.com
Developed & Engineered by JP Kreasi