# Location History Retention Plan AI Agent Connect

> Location History Retention Plan MCP acts as a classification engine for your sensitive geographic telemetry data. It lets your AI client apply specific lifecycle policies to location records by filtering through dates, providers, or devices. You can organize data into Keep, Review, or Delete-On buckets to maintain control without accidental deletions.

## Overview
- **Category:** data-management
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_CEvS3MZ8NfE1i8CcNuqPRd0OrjE2R0WekqjzSGwH/ai-agent-connect
- **Tags:** location, retention, telemetry, data-lifecycle, privacy-compliance

## Description

Managing large volumes of geographic telemetry data is a headache, especially when privacy and compliance are on the line. This MCP gives your AI client the ability to act as a data lifecycle manager. Instead of manually sorting through thousands of coordinates, you can instruct your agent to categorize records based on your specific retention rules. 

You can isolate data by provider or device before running analysis, ensuring you only touch the subsets that matter. The system organizes records into three distinct buckets: Keep, Review, or Delete-On. This approach lets you stage data for deletion without actually performing destructive actions, giving you a safety net to verify records before they are gone. It turns raw telemetry into a structured, actionable dataset that follows your exact compliance requirements.

## Tools

### analyze_retention_plan
This tool evaluates location records against your specific retention rules to sort them into categories.

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

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

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

## Prompt Examples

**Prompt:** 
```
Analyze these location records using a 30-day retention policy.
```

**Response:** 
```
The analysis is complete. 45 records are marked to Keep, 12 are in Review, and 5 are flagged as Delete-On.
```

**Prompt:** 
```
How many records are scheduled for deletion based on my current plan?
```

**Response:** 
```
There are currently 8 records in the Delete-On bucket.
```

**Prompt:** 
```
Calculate the expiration date for a record from January 1st, 2024, with a 90-day retention period.
```

**Response:** 
```
The record is scheduled to be flagged for deletion on March 31st, 2024.
```

## Capabilities

### Data Categorization
Your agent sorts telemetry into Keep, Review, or Delete-On buckets.

### Granular Filtering
The AI isolates specific data subsets using provider or device identifiers.

### Expiration Tracking
Your agent calculates precise dates for when records should be flagged.

### Statistical Summaries
The tool provides counts and breakdowns of the current retention status.

### Non-Destructive Management
The MCP organizes data into buckets without performing immediate deletions.

## Use Cases

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

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

### Data Lifecycle Automation
Set up rules that move records from Keep to Review as they age.

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

## Benefits

- Prevents accidental data loss by using non-destructive buckets.
- Reduces manual sorting through automated provider and device filtering.
- Provides clear visibility into data expiration through precise date calculations.
- Automates the classification of telemetry into actionable lifecycle stages.

## How It Works

Connect your client to Vinkius and start managing telemetry through natural language.

1. Connect your MCP-compatible client to the Vinkius platform.
2. Define your retention rules and policies.
3. Instruct your agent to filter or analyze specific telemetry subsets.
4. Review the categorized buckets and expiration dates provided by the agent.

## Frequently Asked Questions

**Does this MCP delete my data automatically?**
No. The MCP organizes data into Keep, Review, or Delete-On buckets without performing destructive deletions.

**Can I filter data by specific hardware?**
Yes. You can use the filter tool to narrow down records to a specific device or provider.

**How does the agent know when to delete a record?**
The agent uses the expiration tool to calculate the exact date a record is scheduled to be flagged based on your rules.

**What kind of data does this work with?**
This MCP is designed for geographic telemetry and location history records.

**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.

**Does this tool delete my location data?**
No. This tool is a classification engine. It flags records for future deletion using the `analyze_retention_plan` tool, but it does not perform the actual deletion.

**How can I filter records by a specific device?**
You can use the `filter_by_provider_device` tool to narrow down your records to a specific device ID before running a full retention analysis.

**What are the different retention buckets?**
Records are categorized into Keep (preserved), Review (gray area/approaching expiration), or Delete-On (ready for removal).