---
name: algolia-data-handling
description: >-
  Design and audit the data lifecycle for records and user events sent to Algolia. Use when minimizing indexed fields, handling deletion requests, or documenting retention and privacy boundaries. Trigger with "Algolia privacy", "delete Algolia user data", or "index data review".
argument-hint: "[repository-path] [dataset-or-request-id]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - saas
  - algolia
  - privacy
model: inherit
effort: medium
compatibility: Designed for Claude Code
title: algolia-data-handling
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-data-handling
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-data-handling/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/algolia-data-handling`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/algolia-data-handling`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/algolia-data-handling) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/algolia-data-handling`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/algolia-data-handling --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/algolia-data-handling --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Algolia Data Handling Review

## Overview

This skill maps which data leaves the source system, how it becomes searchable records or events, and how correction and deletion propagate. It does not claim legal compliance; it produces technical evidence for the responsible privacy owner.

## Prerequisites

- A named repository, environment, and Algolia application or index in scope
- The local lockfile and installed client types as implementation authority
- A safe read-only query or explicitly disposable test target
- Current first-party documentation for any provider behavior that affects the change

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect local code, configuration names, tests, and dependency versions. Use `WebFetch` only for current official Algolia documentation. Use `Write` or `Edit` only after identifying the target files, constraints, and verification plan.

## Current Contract

- Index only fields required for retrieval, ranking, filtering, display, or approved analytics.
- Treat `attributesToRetrieve` as response shaping, not as a substitute for excluding sensitive data from records.
- Keep source-system identity mappings so corrections and deletions are reproducible.
- Handle record deletion and Insights user-token deletion as separate surfaces with separate evidence.

## Authentication

Use a restricted backend write key for record changes and the documented authorization for user-data deletion. Never include raw secrets or direct personal identifiers in logs or example events.

## Instructions

1. Inventory record fields, derived attributes, event fields, user tokens, environments, and downstream exports.
2. Classify each field by purpose, sensitivity, source authority, and deletion requirement.
3. Remove unnecessary fields before indexing and test that UI and ranking behavior still work.
4. Implement idempotent correction and deletion paths with request IDs and target indices.
5. Verify absence using bounded lookups and preserve evidence without retaining the deleted value.
6. Document retention ownership, incident escalation, and gaps for privacy or legal review.

## Approval Boundaries

Do not make legal conclusions, bulk-delete records, change retention policy, or expose protected values while verifying a request.

## Output

Return the data-flow map, field inventory, minimization changes, deletion/correction procedure, verification evidence, unresolved provider retention questions, and named policy owner.

## Error Handling

| Condition | Response |
|---|---|
| Identity mapping missing | Stop and reconcile the source identity before deletion. |
| Deletion task incomplete | Retain the task ID and verify state before closing. |
| Event token contains PII | Stop sending it and escalate remediation. |
| Policy answer unavailable | Record the question for the privacy owner or provider. |

## Examples

Use this compact input and expected handoff to calibrate scope and evidence quality.

Input:

```text
request=privacy-123; surfaces=records,events; indices=customer_search
```

Expected handoff:

```text
records=removed-and-verified; events=requested; legal-determination=not-made
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-data-handling/references/official-docs.md)
- [Security best practices](https://www.algolia.com/doc/guides/security/security-best-practices)
- [Delete user token events](https://www.algolia.com/doc/rest-api/insights/delete-user-token)
- [API keys](https://www.algolia.com/doc/guides/security/api-keys)
