Overview
Reelevant supports PGP (Pretty Good Privacy) decryption for file-based data sources. If your data provider delivers encrypted files, you can configure your datasource with a PGP private key so that files are decrypted transparently during import — no manual decryption step required. PGP decryption is available on the following source types:PGP decryption works with both armored (
.asc) and binary (.pgp, .gpg) encrypted files. The format is detected automatically.Configuration
To enable PGP decryption, add the following fields in your source configuration:How It Works
- Reelevant fetches the encrypted file from the configured source (URL, FTP, S3, etc.).
- The file is streamed through the PGP decryption layer — the entire file is never buffered in memory.
- The decrypted stream is then decompressed (if
.gzor.zip) and parsed as usual. - Fields are extracted and made available for mapping.
Decryption only runs when
pgpPrivateKey is configured. If no key is provided, the file is processed normally without any decryption overhead.Supported Encryption Formats
Both formats are detected automatically — no additional configuration is needed.
Combining with Compression
PGP decryption is applied before decompression. This means you can have files that are both encrypted and compressed:Error Handling
If decryption fails, the datasource job reports a clear error. Common failure scenarios:Generating a PGP Key Pair
If your data provider needs a public key to encrypt files for you, you can generate a key pair using GPG:Limitations
- Single key only — each source configuration supports one private key. If files are encrypted to multiple recipients, provide the matching private key.
- Decryption only — Reelevant decrypts incoming files but does not encrypt outgoing data.
- File Upload source — PGP decryption is not supported for files uploaded directly via the platform UI. Use URL, FTP/SFTP, S3, or GCS for encrypted files instead.