Privacy,in plain terms.

Epafi is contact data infrastructure. To run it, we process two distinct categories of data, and we never blur the line between them:

• +Account data — your name, email, profile image, preferences, and billing identifiers.
• +Contact data — the records you import or push through the API: names, emails, phone numbers, employers, job titles, social profiles, tags, and custom fields.
• +Usage data — product telemetry such as feature usage, error logs, and performance timings. This contains no contact record content.

We do not collect data about your contacts’ behavior, we do not track your contacts across the web, and we do not enrich anyone you have not explicitly imported.

Contact data enters Epafi only through actions you take:

• +File imports you run (CSV, vCard, LinkedIn or Google Contacts exports).
• +Records you create through the web application or REST API.
• +Enrichment attributes returned by our data providers for records you chose to enrich.

If you import personal data about other people, you are responsible for having a lawful basis to do so — typically legitimate interest for B2B contact management. Section 6 and our GDPR page explain how we support your obligations.

We keep the sub-processor list short, named, and current. No anonymous "partners", no marketing pixels on contact data.

These are the providers represented in the current application and deployment configuration. Their contracted locations, transfer terms, and notice obligations must be confirmed in executed provider agreements before this service is launched.

• +Sell, rent, or broker your data or your contacts’ data — to anyone, in any form.
• +Train shared or third-party ML models on your contact data.
• +Run advertising trackers on authenticated pages.
• +Use your contact records for purposes unrelated to operating and securing the service.

Archiving a contact is reversible. Permanent deletion removes the contact from the primary database and queues removal from the search index. Previously generated export files are point-in-time snapshots taken when you requested them: deleting a contact does not rewrite an export that already exists, and those artifacts expire after seven days under the current application setting.

A file you upload to import contacts is deleted as soon as the import finishes. If an import fails, the uploaded file is kept for seven days so the import can be retried, then deleted. The import record itself — file name, counts, and any row errors, not the contact data — is kept for twelve months so import history stays available, and is removed with your account.

Closing your account schedules its data for erasure after a 30-day recovery period. Billing records are held by Polar under its applicable retention obligations. Backup retention is controlled by the deployment provider and must be documented before launch.

Regardless of where you live, we extend the core GDPR rights to every user:

• +Access — export contacts through the export interface or REST API.
• +Rectification — correct any account data at any time.
• +Erasure — permanently delete contact records or schedule your account for deletion.
• +Portability — contact exports are available as CSV, JSON, or vCard.
• +Objection & restriction — the current product has no dedicated record-freeze or suppression workflow; requests require an operational support process.

If your contacts exercise their rights against you, our API and UI give you the tools to honor access, correction, export, and permanent-deletion requests. Backup handling remains a deployment-policy requirement rather than an application-enforced workflow.