@proseid v1.0.0 US

FTC Safeguards Rule notification-event determination

Determines whether a covered financial institution's security event enters the FTC's 500-consumer notification track and records the required report content and timing.

Compatible with

FormGuided assessmentDeterminationCompliance checklistAPI

Use Schema in a Flow

Publication

Protocol: Proseid_v1.0
Version: v1.0.0
Applies in: United States
Fields: 20
Flow price: $0.20
Publisher fee: None

Legal history

Time periods

notification_rule_20242024-05-13 → continues indefinitely

Current

Controlling sources

Legal references

FTC Safeguards Rule 16 CFR § 314.4(j)

Source ↗

Schema fields

20 fields

Field

Type

Description

Req

Why the event date or range cannot yet be identified

String

—

Opt

The event date or date range can be identified

Boolean

—

Req

FTC notification outcome

String

—

Opt

Financial institution

String

—

Req

Institution contact information

String

—

Opt

FTC notification submitted

Boolean

—

Opt

The institution is covered by the FTC Safeguards Rule

Boolean

—

Req

Law enforcement asked the FTC to delay public disclosure of the report

Boolean

—

Opt

Known event date or date range

String

—

Opt

Consumers whose information was involved

Number

—

Req

Types of customer information involved

String

—

Opt

Unauthorized acquisition of customer information occurred

Boolean

—

Req

FTC notified within 30 days after discovery

Boolean

—

Opt

Date the notification event was discovered

Date

—

Req

General description of the event

String

—

Opt

Consumers affected or potentially affected

Number

—

Opt

Reliable evidence shows acquisition did not and could not reasonably occur

Boolean

—

Req

The customer information was unencrypted

Boolean

—

Req

Unauthorized access to customer information occurred

Boolean

—

Req

An unauthorized person accessed the encryption key

Boolean

—

Req

Example payload

JSON

{
  "responses": {
    "event_date_range_unavailable_reason": "",
    "event_date_range_known": false,
    "institution_name": "",
    "institution_contact": "",
    "ftc_notified": false,
    "covered_by_safeguards_rule": false,
    "law_enforcement_publication_delay_requested": false,
    "event_date_range": "",
    "consumers_whose_information_was_involved": null,
    "information_types": "",
    "unauthorized_acquisition": false,
    "notified_within_30_days": false,
    "discovered_at": "",
    "event_description": "",
    "consumers_affected_or_potentially_affected": null,
    "reliable_evidence_no_acquisition": false,
    "information_unencrypted": false,
    "unauthorized_access": false,
    "encryption_key_accessed": false
  },
  "effective_at": "2026-07-23"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL

curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json

200 OK

{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}

422 Invalid

{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "event_date_range_unavailable_reason",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}

A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions

Loading published versions…

Trust ledger

Crowd → credentialed

Provenance

Community publisher (unverified)

@proseid · latest v1.0.0

Community signal

0 votes

No votes yet.

Attestations · by version

0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments

to join the discussion.

Time periods

Legal references

Schema fields

Example payload

API usage

Published versions

Trust ledger

Discussion

EU right-of-withdrawal record

OSHA fatality or severe-injury reporting determination

SEC material cybersecurity incident disclosure record

California CCPA consumer-request lifecycle