@tantainnovative/ndpr-toolkit 3.4.1 → 3.5.1

package/dist/consent-CmVzqZUk.d.ts

@@ -1,99 +0,0 @@
-/**
- * Consent types aligned with NDPA 2023 Section 25-26
- * Consent must be freely given, specific, informed, and unambiguous
- */
-/**
- * Represents a consent option that can be presented to users
- */
-interface ConsentOption {
-    /** Unique identifier for the consent option */
-    id: string;
-    /** Display label for the consent option */
-    label: string;
-    /** Detailed description of what this consent option covers */
-    description: string;
-    /** Whether this consent option is required (cannot be declined) */
-    required: boolean;
-    /**
-     * The specific purpose for which data will be processed
-     * NDPA Section 25(2) requires consent to be specific to each purpose
-     */
-    purpose: string;
-    /**
-     * Default state of the consent option
-     * @default false
-     */
-    defaultValue?: boolean;
-    /**
-     * Categories of personal data covered by this consent option
-     */
-    dataCategories?: string[];
-}
-/**
- * Represents the user's consent settings
- */
-interface ConsentSettings {
-    /** Map of consent option IDs to boolean values indicating consent status */
-    consents: Record<string, boolean>;
-    /** Timestamp when consent was last updated */
-    timestamp: number;
-    /** Version of the consent form that was accepted */
-    version: string;
-    /** Method used to collect consent (e.g., "banner", "settings", "api") */
-    method: string;
-    /** Whether the user has actively made a choice (as opposed to default settings) */
-    hasInteracted: boolean;
-    /**
-     * The lawful basis under which processing is conducted
-     * Required by NDPA Section 25(1)
-     */
-    lawfulBasis?: LawfulBasisType;
-}
-/**
- * Lawful basis for processing personal data per NDPA Section 25(1)
- */
-type LawfulBasisType = 'consent' | 'contract' | 'legal_obligation' | 'vital_interests' | 'public_interest' | 'legitimate_interests';
-/**
- * Represents the storage mechanism for consent settings
- */
-interface ConsentStorageOptions {
-    /**
-     * Storage key for consent settings
-     * @default "ndpr_consent"
-     */
-    storageKey?: string;
-    /**
-     * Storage type to use
-     * @default "localStorage"
-     */
-    storageType?: 'localStorage' | 'sessionStorage' | 'cookie';
-    /**
-     * Cookie options (only used when storageType is "cookie")
-     */
-    cookieOptions?: {
-        /** Domain for the cookie */
-        domain?: string;
-        /**
-         * Path for the cookie
-         * @default "/"
-         */
-        path?: string;
-        /**
-         * Expiration days for the cookie
-         * @default 365
-         */
-        expires?: number;
-        /**
-         * Whether the cookie should be secure
-         * @default true
-         */
-        secure?: boolean;
-        /**
-         * SameSite attribute for the cookie
-         * @default "Lax"
-         */
-        sameSite?: 'Strict' | 'Lax' | 'None';
-    };
-}
-
-export type { ConsentOption as C, LawfulBasisType as L, ConsentSettings as a, ConsentStorageOptions as b };

package/dist/consent-audit-BdByjYlM.d.mts

@@ -1,65 +0,0 @@
-import { a as ConsentSettings, C as ConsentOption } from './consent-CmVzqZUk.mjs';
-
-/**
- * Validates consent settings to ensure they meet NDPA requirements
- * @param settings The consent settings to validate
- * @returns An object containing validation result and any error messages
- */
-declare function validateConsent(settings: ConsentSettings): {
-    valid: boolean;
-    errors: string[];
-};
-/**
- * Validates that consent options meet NDPA Section 26 requirements.
- * Each consent option must specify a purpose for which data will be processed,
- * as consent must be specific and informed per the Nigeria Data Protection Act.
- * @param options The consent options to validate
- * @returns An object containing validation result and any error messages
- */
-declare function validateConsentOptions(options: ConsentOption[]): {
-    valid: boolean;
-    errors: string[];
-};
-
-/**
- * Represents a single entry in the consent audit trail.
- * Each entry captures what happened, when, and the full consent state
- * at that point in time, satisfying NDPA recordkeeping requirements.
- */
-interface ConsentAuditEntry {
-    /** The type of consent action that occurred */
-    action: 'consent_given' | 'consent_withdrawn' | 'consent_updated' | 'consent_expired';
-    /** Unix timestamp (ms) when the action occurred */
-    timestamp: number;
-    /** Version of the consent form at the time of the action */
-    version: string;
-    /** Full snapshot of consent category states */
-    categories: Record<string, boolean>;
-    /** How consent was collected (e.g. "banner", "customize", "api") */
-    method: string;
-    /** Browser user-agent string for forensic traceability */
-    userAgent?: string;
-}
-/**
- * Creates a new audit entry from consent settings. If `previousSettings` is
- * provided, the action is automatically determined by comparing old and new
- * states. Otherwise `action` defaults to `'consent_given'`.
- */
-declare function createAuditEntry(settings: ConsentSettings, previousSettings?: ConsentSettings | null, actionOverride?: ConsentAuditEntry['action']): ConsentAuditEntry;
-/**
- * Retrieves the full consent audit log from localStorage.
- * Returns an empty array if no log exists or parsing fails.
- *
- * @param storageKey - Base storage key (the audit key is derived as `${storageKey}_audit`)
- */
-declare function getAuditLog(storageKey?: string): ConsentAuditEntry[];
-/**
- * Appends a single audit entry to the consent audit log in localStorage.
- * The log is append-only; existing entries are never modified.
- *
- * @param entry     - The audit entry to append
- * @param storageKey - Base storage key (the audit key is derived as `${storageKey}_audit`)
- */
-declare function appendAuditEntry(entry: ConsentAuditEntry, storageKey?: string): void;
-
-export { type ConsentAuditEntry as C, appendAuditEntry as a, validateConsentOptions as b, createAuditEntry as c, getAuditLog as g, validateConsent as v };

package/dist/consent-audit-DhbfMR0n.d.ts

@@ -1,65 +0,0 @@
-import { a as ConsentSettings, C as ConsentOption } from './consent-CmVzqZUk.js';
-
-/**
- * Validates consent settings to ensure they meet NDPA requirements
- * @param settings The consent settings to validate
- * @returns An object containing validation result and any error messages
- */
-declare function validateConsent(settings: ConsentSettings): {
-    valid: boolean;
-    errors: string[];
-};
-/**
- * Validates that consent options meet NDPA Section 26 requirements.
- * Each consent option must specify a purpose for which data will be processed,
- * as consent must be specific and informed per the Nigeria Data Protection Act.
- * @param options The consent options to validate
- * @returns An object containing validation result and any error messages
- */
-declare function validateConsentOptions(options: ConsentOption[]): {
-    valid: boolean;
-    errors: string[];
-};
-
-/**
- * Represents a single entry in the consent audit trail.
- * Each entry captures what happened, when, and the full consent state
- * at that point in time, satisfying NDPA recordkeeping requirements.
- */
-interface ConsentAuditEntry {
-    /** The type of consent action that occurred */
-    action: 'consent_given' | 'consent_withdrawn' | 'consent_updated' | 'consent_expired';
-    /** Unix timestamp (ms) when the action occurred */
-    timestamp: number;
-    /** Version of the consent form at the time of the action */
-    version: string;
-    /** Full snapshot of consent category states */
-    categories: Record<string, boolean>;
-    /** How consent was collected (e.g. "banner", "customize", "api") */
-    method: string;
-    /** Browser user-agent string for forensic traceability */
-    userAgent?: string;
-}
-/**
- * Creates a new audit entry from consent settings. If `previousSettings` is
- * provided, the action is automatically determined by comparing old and new
- * states. Otherwise `action` defaults to `'consent_given'`.
- */
-declare function createAuditEntry(settings: ConsentSettings, previousSettings?: ConsentSettings | null, actionOverride?: ConsentAuditEntry['action']): ConsentAuditEntry;
-/**
- * Retrieves the full consent audit log from localStorage.
- * Returns an empty array if no log exists or parsing fails.
- *
- * @param storageKey - Base storage key (the audit key is derived as `${storageKey}_audit`)
- */
-declare function getAuditLog(storageKey?: string): ConsentAuditEntry[];
-/**
- * Appends a single audit entry to the consent audit log in localStorage.
- * The log is append-only; existing entries are never modified.
- *
- * @param entry     - The audit entry to append
- * @param storageKey - Base storage key (the audit key is derived as `${storageKey}_audit`)
- */
-declare function appendAuditEntry(entry: ConsentAuditEntry, storageKey?: string): void;
-
-export { type ConsentAuditEntry as C, appendAuditEntry as a, validateConsentOptions as b, createAuditEntry as c, getAuditLog as g, validateConsent as v };

package/dist/cross-border-BBi9rZyO.d.mts

@@ -1,54 +0,0 @@
-import { a as CrossBorderTransfer, b as TransferMechanism } from './cross-border-UyT00llA.mjs';
-
-/**
- * Validation result for a cross-border transfer
- */
-interface TransferValidationResult {
-    isValid: boolean;
-    errors: string[];
-    warnings: string[];
-}
-/**
- * Risk assessment result for a cross-border transfer
- */
-interface TransferRiskResult {
-    riskLevel: 'low' | 'medium' | 'high';
-    riskScore: number;
-    factors: string[];
-    recommendations: string[];
-}
-/**
- * Returns whether NDPC approval is required for a given transfer mechanism.
- * Approval is required for standard contractual clauses (Section 42),
- * binding corporate rules (Section 43), and specific NDPC authorization (Section 44).
- *
- * @param mechanism The transfer mechanism
- * @returns Whether NDPC approval is required
- */
-declare function isNDPCApprovalRequired(mechanism: TransferMechanism): boolean;
-/**
- * Returns a human-readable description of a transfer mechanism with its NDPA section reference.
- *
- * @param mechanism The transfer mechanism
- * @returns Description including the relevant NDPA section
- */
-declare function getTransferMechanismDescription(mechanism: TransferMechanism): string;
-/**
- * Validates a cross-border transfer record for completeness and compliance.
- * Checks required fields, verifies that NDPC approval is documented when required,
- * and ensures safeguards are in place.
- *
- * @param transfer The cross-border transfer to validate
- * @returns Validation result with errors and warnings
- */
-declare function validateTransfer(transfer: CrossBorderTransfer): TransferValidationResult;
-/**
- * Performs a basic risk assessment of a cross-border transfer based on adequacy status,
- * transfer mechanism, and data sensitivity.
- *
- * @param transfer The cross-border transfer to assess
- * @returns Risk assessment result with score, factors, and recommendations
- */
-declare function assessTransferRisk(transfer: CrossBorderTransfer): TransferRiskResult;
-
-export { type TransferRiskResult as T, type TransferValidationResult as a, assessTransferRisk as b, getTransferMechanismDescription as g, isNDPCApprovalRequired as i, validateTransfer as v };

package/dist/cross-border-Dy-U9Hu6.d.ts

@@ -1,54 +0,0 @@
-import { a as CrossBorderTransfer, b as TransferMechanism } from './cross-border-UyT00llA.js';
-
-/**
- * Validation result for a cross-border transfer
- */
-interface TransferValidationResult {
-    isValid: boolean;
-    errors: string[];
-    warnings: string[];
-}
-/**
- * Risk assessment result for a cross-border transfer
- */
-interface TransferRiskResult {
-    riskLevel: 'low' | 'medium' | 'high';
-    riskScore: number;
-    factors: string[];
-    recommendations: string[];
-}
-/**
- * Returns whether NDPC approval is required for a given transfer mechanism.
- * Approval is required for standard contractual clauses (Section 42),
- * binding corporate rules (Section 43), and specific NDPC authorization (Section 44).
- *
- * @param mechanism The transfer mechanism
- * @returns Whether NDPC approval is required
- */
-declare function isNDPCApprovalRequired(mechanism: TransferMechanism): boolean;
-/**
- * Returns a human-readable description of a transfer mechanism with its NDPA section reference.
- *
- * @param mechanism The transfer mechanism
- * @returns Description including the relevant NDPA section
- */
-declare function getTransferMechanismDescription(mechanism: TransferMechanism): string;
-/**
- * Validates a cross-border transfer record for completeness and compliance.
- * Checks required fields, verifies that NDPC approval is documented when required,
- * and ensures safeguards are in place.
- *
- * @param transfer The cross-border transfer to validate
- * @returns Validation result with errors and warnings
- */
-declare function validateTransfer(transfer: CrossBorderTransfer): TransferValidationResult;
-/**
- * Performs a basic risk assessment of a cross-border transfer based on adequacy status,
- * transfer mechanism, and data sensitivity.
- *
- * @param transfer The cross-border transfer to assess
- * @returns Risk assessment result with score, factors, and recommendations
- */
-declare function assessTransferRisk(transfer: CrossBorderTransfer): TransferRiskResult;
-
-export { type TransferRiskResult as T, type TransferValidationResult as a, assessTransferRisk as b, getTransferMechanismDescription as g, isNDPCApprovalRequired as i, validateTransfer as v };

package/dist/cross-border-UyT00llA.d.mts

@@ -1,141 +0,0 @@
-/**
- * Cross-Border Data Transfer types aligned with NDPA 2023 Part VI (Sections 41-45)
- * Personal data may only be transferred outside Nigeria under specific conditions
- */
-/**
- * Transfer mechanisms recognized under the NDPA
- */
-type TransferMechanism = 'adequacy_decision' | 'standard_clauses' | 'binding_corporate_rules' | 'ndpc_authorization' | 'explicit_consent' | 'contract_performance' | 'public_interest' | 'legal_claims' | 'vital_interests';
-/**
- * Adequacy status of a destination country
- */
-type AdequacyStatus = 'adequate' | 'inadequate' | 'pending_review' | 'unknown';
-/**
- * Represents a cross-border data transfer record
- */
-interface CrossBorderTransfer {
-    /** Unique identifier */
-    id: string;
-    /** Destination country or territory */
-    destinationCountry: string;
-    /** ISO country code */
-    destinationCountryCode?: string;
-    /** Adequacy status of the destination */
-    adequacyStatus: AdequacyStatus;
-    /** The transfer mechanism being relied upon */
-    transferMechanism: TransferMechanism;
-    /** Categories of personal data being transferred */
-    dataCategories: string[];
-    /** Whether sensitive personal data is included */
-    includesSensitiveData: boolean;
-    /** Estimated number of data subjects whose data is transferred */
-    estimatedDataSubjects?: number;
-    /** Name of the recipient organization */
-    recipientOrganization: string;
-    /** Contact details of the recipient */
-    recipientContact: {
-        name: string;
-        email: string;
-        phone?: string;
-        address?: string;
-    };
-    /** Purpose of the data transfer */
-    purpose: string;
-    /** Safeguards in place to protect the data */
-    safeguards: string[];
-    /** Risk assessment summary */
-    riskAssessment: string;
-    /** Risk level of the transfer */
-    riskLevel: 'low' | 'medium' | 'high';
-    /** NDPC approval details (required for some transfer mechanisms) */
-    ndpcApproval?: {
-        required: boolean;
-        applied: boolean;
-        approved?: boolean;
-        referenceNumber?: string;
-        appliedAt?: number;
-        approvedAt?: number;
-    };
-    /** Whether a Transfer Impact Assessment has been conducted */
-    tiaCompleted: boolean;
-    /** Reference to the TIA document */
-    tiaReference?: string;
-    /** Frequency of the transfer */
-    frequency: 'one_time' | 'periodic' | 'continuous';
-    /** Start date of the transfer */
-    startDate: number;
-    /** End date of the transfer (if applicable) */
-    endDate?: number;
-    /** Status of the transfer */
-    status: 'active' | 'suspended' | 'terminated' | 'pending_approval';
-    /** Timestamp when the record was created */
-    createdAt: number;
-    /** Timestamp when the record was last updated */
-    updatedAt: number;
-    /** Next review date */
-    reviewDate?: number;
-}
-/**
- * Transfer Impact Assessment (TIA) for cross-border transfers
- */
-interface TransferImpactAssessment {
-    /** Unique identifier */
-    id: string;
-    /** ID of the associated cross-border transfer */
-    transferId: string;
-    /** Date the assessment was conducted */
-    assessmentDate: number;
-    /** Person who conducted the assessment */
-    assessor: {
-        name: string;
-        role: string;
-        email: string;
-    };
-    /** Analysis of the destination country's legal framework */
-    destinationLegalFramework: string;
-    /** Whether the destination has data protection legislation */
-    hasDataProtectionLaw: boolean;
-    /** Whether the destination has an independent supervisory authority */
-    hasIndependentAuthority: boolean;
-    /** Risk of government access to the data */
-    governmentAccessRisk: 'low' | 'medium' | 'high';
-    /** Overall assessment of data protection level */
-    dataProtectionLevel: 'adequate' | 'partially_adequate' | 'inadequate';
-    /** Supplementary measures to address gaps */
-    supplementaryMeasures: string[];
-    /** Technical measures (encryption, pseudonymization, etc.) */
-    technicalMeasures: string[];
-    /** Contractual measures */
-    contractualMeasures: string[];
-    /** Organizational measures */
-    organizationalMeasures: string[];
-    /** Overall conclusion */
-    conclusion: string;
-    /** Whether the transfer can proceed based on the assessment */
-    approved: boolean;
-    /** Conditions for the transfer (if approved with conditions) */
-    conditions?: string[];
-}
-/**
- * Summary of cross-border transfer compliance
- */
-interface CrossBorderSummary {
-    /** Total number of active transfers */
-    totalActiveTransfers: number;
-    /** Breakdown by transfer mechanism */
-    byMechanism: Record<TransferMechanism, number>;
-    /** Breakdown by adequacy status */
-    byAdequacy: Record<AdequacyStatus, number>;
-    /** Transfers pending NDPC approval */
-    pendingApproval: CrossBorderTransfer[];
-    /** Transfers due for review */
-    dueForReview: CrossBorderTransfer[];
-    /** Transfers missing TIA */
-    missingTIA: CrossBorderTransfer[];
-    /** High-risk transfers */
-    highRiskTransfers: CrossBorderTransfer[];
-    /** Last updated timestamp */
-    lastUpdated: number;
-}
-
-export type { AdequacyStatus as A, CrossBorderSummary as C, TransferImpactAssessment as T, CrossBorderTransfer as a, TransferMechanism as b };

package/dist/cross-border-UyT00llA.d.ts

@@ -1,141 +0,0 @@
-/**
- * Cross-Border Data Transfer types aligned with NDPA 2023 Part VI (Sections 41-45)
- * Personal data may only be transferred outside Nigeria under specific conditions
- */
-/**
- * Transfer mechanisms recognized under the NDPA
- */
-type TransferMechanism = 'adequacy_decision' | 'standard_clauses' | 'binding_corporate_rules' | 'ndpc_authorization' | 'explicit_consent' | 'contract_performance' | 'public_interest' | 'legal_claims' | 'vital_interests';
-/**
- * Adequacy status of a destination country
- */
-type AdequacyStatus = 'adequate' | 'inadequate' | 'pending_review' | 'unknown';
-/**
- * Represents a cross-border data transfer record
- */
-interface CrossBorderTransfer {
-    /** Unique identifier */
-    id: string;
-    /** Destination country or territory */
-    destinationCountry: string;
-    /** ISO country code */
-    destinationCountryCode?: string;
-    /** Adequacy status of the destination */
-    adequacyStatus: AdequacyStatus;
-    /** The transfer mechanism being relied upon */
-    transferMechanism: TransferMechanism;
-    /** Categories of personal data being transferred */
-    dataCategories: string[];
-    /** Whether sensitive personal data is included */
-    includesSensitiveData: boolean;
-    /** Estimated number of data subjects whose data is transferred */
-    estimatedDataSubjects?: number;
-    /** Name of the recipient organization */
-    recipientOrganization: string;
-    /** Contact details of the recipient */
-    recipientContact: {
-        name: string;
-        email: string;
-        phone?: string;
-        address?: string;
-    };
-    /** Purpose of the data transfer */
-    purpose: string;
-    /** Safeguards in place to protect the data */
-    safeguards: string[];
-    /** Risk assessment summary */
-    riskAssessment: string;
-    /** Risk level of the transfer */
-    riskLevel: 'low' | 'medium' | 'high';
-    /** NDPC approval details (required for some transfer mechanisms) */
-    ndpcApproval?: {
-        required: boolean;
-        applied: boolean;
-        approved?: boolean;
-        referenceNumber?: string;
-        appliedAt?: number;
-        approvedAt?: number;
-    };
-    /** Whether a Transfer Impact Assessment has been conducted */
-    tiaCompleted: boolean;
-    /** Reference to the TIA document */
-    tiaReference?: string;
-    /** Frequency of the transfer */
-    frequency: 'one_time' | 'periodic' | 'continuous';
-    /** Start date of the transfer */
-    startDate: number;
-    /** End date of the transfer (if applicable) */
-    endDate?: number;
-    /** Status of the transfer */
-    status: 'active' | 'suspended' | 'terminated' | 'pending_approval';
-    /** Timestamp when the record was created */
-    createdAt: number;
-    /** Timestamp when the record was last updated */
-    updatedAt: number;
-    /** Next review date */
-    reviewDate?: number;
-}
-/**
- * Transfer Impact Assessment (TIA) for cross-border transfers
- */
-interface TransferImpactAssessment {
-    /** Unique identifier */
-    id: string;
-    /** ID of the associated cross-border transfer */
-    transferId: string;
-    /** Date the assessment was conducted */
-    assessmentDate: number;
-    /** Person who conducted the assessment */
-    assessor: {
-        name: string;
-        role: string;
-        email: string;
-    };
-    /** Analysis of the destination country's legal framework */
-    destinationLegalFramework: string;
-    /** Whether the destination has data protection legislation */
-    hasDataProtectionLaw: boolean;
-    /** Whether the destination has an independent supervisory authority */
-    hasIndependentAuthority: boolean;
-    /** Risk of government access to the data */
-    governmentAccessRisk: 'low' | 'medium' | 'high';
-    /** Overall assessment of data protection level */
-    dataProtectionLevel: 'adequate' | 'partially_adequate' | 'inadequate';
-    /** Supplementary measures to address gaps */
-    supplementaryMeasures: string[];
-    /** Technical measures (encryption, pseudonymization, etc.) */
-    technicalMeasures: string[];
-    /** Contractual measures */
-    contractualMeasures: string[];
-    /** Organizational measures */
-    organizationalMeasures: string[];
-    /** Overall conclusion */
-    conclusion: string;
-    /** Whether the transfer can proceed based on the assessment */
-    approved: boolean;
-    /** Conditions for the transfer (if approved with conditions) */
-    conditions?: string[];
-}
-/**
- * Summary of cross-border transfer compliance
- */
-interface CrossBorderSummary {
-    /** Total number of active transfers */
-    totalActiveTransfers: number;
-    /** Breakdown by transfer mechanism */
-    byMechanism: Record<TransferMechanism, number>;
-    /** Breakdown by adequacy status */
-    byAdequacy: Record<AdequacyStatus, number>;
-    /** Transfers pending NDPC approval */
-    pendingApproval: CrossBorderTransfer[];
-    /** Transfers due for review */
-    dueForReview: CrossBorderTransfer[];
-    /** Transfers missing TIA */
-    missingTIA: CrossBorderTransfer[];
-    /** High-risk transfers */
-    highRiskTransfers: CrossBorderTransfer[];
-    /** Last updated timestamp */
-    lastUpdated: number;
-}
-
-export type { AdequacyStatus as A, CrossBorderSummary as C, TransferImpactAssessment as T, CrossBorderTransfer as a, TransferMechanism as b };

package/dist/docx-4n8g4zul.d.mts

@@ -1,64 +0,0 @@
-import { c as PrivacyPolicy } from './privacy-Ca6te9Ir.mjs';
-import { H as HTMLExportOptions, g as PDFExportOptions, f as DOCXExportOptions } from './policy-engine-5qTfp2z4.mjs';
-
-/**
- * Export a PrivacyPolicy as a self-contained HTML string.
- *
- * The returned string includes:
- * - An embedded `<style>` block (responsive, dark/light, print-friendly)
- * - An `<article>` wrapper with semantic markup
- * - A `<nav>` table of contents with anchor links
- * - A `<section>` for every included policy section
- * - A metadata footer (org name, effective date, version, generator credit)
- * - Optional custom CSS injection via `options.customCSS`
- */
-declare function exportHTML(policy: PrivacyPolicy, options?: HTMLExportOptions): string;
-
-/**
- * Export a PrivacyPolicy as a clean Markdown string.
- *
- * Structure:
- * ```
- * # Policy Title
- * _Effective: date | Version: X | Org Name_
- *
- * ## Table of Contents
- * - [Section Title](#anchor)
- *
- * ## 1. Section Title
- * Section content...
- * ```
- */
-declare function exportMarkdown(policy: PrivacyPolicy): string;
-
-/**
- * Export a PrivacyPolicy to a PDF Blob using jspdf (optional peer dependency).
- *
- * Features:
- * - Optional cover page with title, organisation, date, version and compliance badge
- * - Optional table of contents page
- * - One section per heading, content reflowed to fit the page
- * - Automatic page breaks
- * - Page header (org name) and footer (page X of Y) on every page
- * - PDF metadata (title, author, subject, keywords)
- *
- * @throws {Error} if the `jspdf` package is not installed
- */
-declare function exportPDF(policy: PrivacyPolicy, options?: PDFExportOptions): Promise<Blob>;
-
-/**
- * Export a PrivacyPolicy as a Word (.docx) Blob using the `docx` library
- * (optional peer dependency).
- *
- * Features:
- * - Title paragraph with large bold text
- * - Organisation name + version subtitle
- * - Optional table of contents placeholder heading
- * - All included policy sections as Heading 1 + body paragraphs / bullet lists
- * - Running header (org name) and page-number footer on every page
- *
- * @throws {Error} if the `docx` package is not installed
- */
-declare function exportDOCX(policy: PrivacyPolicy, options?: DOCXExportOptions): Promise<Blob>;
-
-export { exportHTML as a, exportMarkdown as b, exportPDF as c, exportDOCX as e };