Privacy Policy

This policy describes the current PostAIGen application and should receive professional legal review before commercial launch.

Information we may collect

PostAIGen may process account information such as names, email addresses, authentication records, locale, and timezone; business/account information and account access records; content, revisions, media, SEO fields, and publishing selections; and technical logs used for security and troubleshooting.

Connected publishing destinations

When you connect a service, we may store destination names, URLs, provider identifiers, connection status, synchronized metadata, and authorization information needed to provide the integration. Supported access tokens, WordPress Application Passwords, and similar credentials are encrypted at rest and are not displayed after storage.

WordPress

PostAIGen connects to WordPress sites that users are authorized to manage. It may retrieve site identity, users, categories, tags, and publishing status and may send content or media when an authorized user requests publication.

How information is used

Information is used to operate accounts, create and manage content, connect destinations, perform requested publishing, show results, secure the service, diagnose errors, and meet legitimate operational obligations. We do not claim uses beyond the capabilities described here.

Third-party services and future payments

Connected providers process information under their own policies. If online billing is introduced, a payment processor such as Stripe may process billing and payment information under its own privacy terms. PostAIGen does not currently provide checkout.

Retention

Account data remains while needed to provide the service. Content and publishing data follow application retention rules; temporary content may be cleared after publishing targets complete, while limited publication and security history may remain for operational, integrity, or legal purposes. Retention may also depend on backups and applicable obligations.

PostAIGen keeps temporary generated and uploaded publication images while they are actively used by your draft. Images that are no longer needed are automatically removed. Unused candidates become eligible for cleanup after 24 hours; removed or replaced images and images of deleted articles may be cleaned immediately when safe. Files required for pending or active transfers are protected until that work finishes. WordPress becomes the destination host for transferred publication media; removing PostAIGen files does not delete WordPress media.

PostAIGen minimizes retained publication content. Eligible historical revision content and publication-content snapshots are removed after 7 days when no longer needed for active work. Current articles and necessary account, security, billing, audit and publishing records, including destination mappings, may remain. Scheduled cleanup runs periodically, so expiration is not a to-the-second deletion guarantee.

Security

PostAIGen uses account isolation, authorization controls, encrypted supported credentials, HTTPS assumptions, and audit records. No system can guarantee absolute security.

Your choices and rights

You may disconnect integrations locally and may request account-data access, correction, or deletion through the contact page. Requests may require identity and authority verification and may be subject to legitimate retention obligations.

Policy updates

This policy may change as PostAIGen develops. Material updates should be reflected by revising this page and its update date.