Download PDFMarkdown Version

Connect Location History Retention Plan to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Organize and manage geographic telemetry data lifecycle policies.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

How Vinkius works: one connection, every tool, in any AI
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Location History Retention Plan.

  1. 01

    Analyze retention plan

    This capability evaluates location records against your specific retention rules to sort them into categories.

  2. 02

    Calculate retention expiration

    Use this to find the exact date a specific record is scheduled to be flagged for deletion.

  3. 03

    Filter by provider device

    This capability narrows down your records to a specific provider or device before you start the retention analysis.

  4. 04

    Summarize retention status

    Get a statistical breakdown and a high-level count of how many records sit in each bucket.

Real work

What teams actually run

01

Privacy Compliance

Automatically flag old location data for deletion to meet regulatory requirements.

02

Telemetry Auditing

Filter records by specific devices to check how different hardware handles data retention.

03

Data Lifecycle Automation

Set up rules that move records from Keep to Review as they age.

04

Storage Optimization

Identify large volumes of data in the Delete-On bucket to manage storage costs.

One connector, every AI

Location History Retention Plan works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Location History Retention Plan to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

961ms average. Fast in production.

Location History Retention Plan is checked daily against the live service.

Daily averagePeak 1155ms
Sep 30Today
Fastest day
883ms
Slowest day
1155ms
14-day trend
Improving-19%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Location History Retention Plan, so you can see the experience inside your AI.

It does not authenticate your account with Location History Retention Plan. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Location History Retention Plan Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_CEvS3MZ8NfE1i8CcNuqPRd0OrjE2R0WekqjzSGwH/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Location History Retention Plan capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "location-history-retention-plan-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_CEvS3MZ8NfE1i8CcNuqPRd0OrjE2R0WekqjzSGwH/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Location History Retention Plan in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Location History Retention Plan owners hand off.

This MCP is built for professionals managing large-scale geographic datasets who need to automate data lifecycle policies.

  • 01

    Data Privacy Officers

    They hand off the task of auditing telemetry data against compliance rules to the AI.

  • 02

    Data Engineers

    They use the capability to automate the categorization of telemetry streams.

  • 03

    Compliance Managers

    They rely on the capability to verify that data retention policies are being followed.

FAQ

Questions Location History Retention Plan owners ask.

  • 01

    Does this MCP delete my data automatically?

    No. The MCP organizes data into Keep, Review, or Delete-On buckets without performing destructive deletions.

  • 02

    Can I filter data by specific hardware?

    Yes. You can use the filter capability to narrow down records to a specific device or provider.

  • 03

    How does the agent know when to delete a record?

    The agent uses the expiration capability to calculate the exact date a record is scheduled to be flagged based on your rules.

  • 04

    What kind of data does this work with?

    This MCP is designed for geographic telemetry and location history records.

  • 05

    Can I see a summary of my data status?

    Yes. You can request a statistical breakdown of how many records fall into each retention bucket.

  • 06

    Does this capability delete my location data?

    No. This capability is a classification engine. It flags records for future deletion using the analyze_retention_plan capability, but it does not perform the actual deletion.

  • 07

    How can I filter records by a specific device?

    You can use the filter_by_provider_device capability to narrow down your records to a specific device ID before running a full retention analysis.

  • 08

    What are the different retention buckets?

    Records are categorized into Keep (preserved), Review (gray area/approaching expiration), or Delete-On (ready for removal).

Explore

More in Data Management

Suggestions

Connect Location History Retention Plan to Claude, Cursor, ChatGPT & more