Privacy Policy

1. Information We Collect

Rulip collects and manages information to provide a persistent, long-term memory server for your AI applications. This includes:

Account Credentials: Basic account information (such as your email address) provided via Firebase Authentication.
AI Memories: The content, transcripts, context, summaries, and parameters you instruct your AI tools (ChatGPT, Claude, Cursor, Windsurf, Manus, etc.) to store using the Rulip MCP tools.
Client Connection Logs: Timestamps, client application types, and connection health metrics to show you which AI tools have connected to your Rulip server.

2. How We Use Your Data

Your AI memories are stored solely to provide contextual memory to your own AI agents. Specifically:

No Model Training: We never use your stored memories, search queries, or private developer context to train AI models (neither ours nor third parties).
Data Encryption: All memory contents are encrypted in transit via SSL/TLS and encrypted at rest in our databases.
Authentication Scope: Access to your memories is securely limited to your authenticated client instances using personal OAuth tokens.

3. Data Sharing and Integrations

Rulip works by exposing a Model Context Protocol (MCP) endpoint. When you configure ChatGPT, Claude, Cursor, Windsurf, or Manus to fetch or save memories, they will make requests to our API. The privacy policy of each respective AI provider applies to their handling of data fetched from Rulip. We do not sell or monetize your memory logs to any third-party advertising companies.

4. Data Retention and Deletion

You have full ownership of your data. You can view, search, and delete your memories at any time through the centralized Rulip Dashboard. If you delete your account, all associated memories and API access tokens are permanently wiped from our active servers and backups within 30 days.

5. Changes to This Policy

We may update this Privacy Policy from time to time. If we make any material changes, we will notify you by posting a notice in the developer dashboard or via email prior to the change becoming effective.

6. Contact Us