Privacy policy

What PostifyNow processes

PostifyNow is a workspace for planning, reviewing, scheduling, and tracking product posts.

• Email and password. When you create an account with email, we store your name, email address and a securely hashed password. Browser sessions use a secure cookie; the iOS app stores its signed session in Keychain, and the Android app stores its signed session encrypted with a key held in Android Keystore.
• Google sign-in. When you choose Google sign-in, PostifyNow receives basic profile information from Google, such as your name and email address, to create or recognize your account. Browser sessions use a secure cookie; the iOS app stores its signed session in Keychain, and the Android app stores its signed session encrypted with a key held in Android Keystore. PostifyNow does not store a session token in browser storage. PostifyNow also stores the profile image address provided by Google with your account; this does not require access to your photo library.
• Sign in with Apple. When enabled, Apple provides a stable account identifier, your email address or private relay address, and your name when first authorized. PostifyNow stores the linked identity and provider tokens on its server to recognize your account. Browser sessions use a secure cookie; the iOS app stores its signed session in Keychain, and the Android app stores its signed session encrypted with a key held in Android Keystore.
• Workspace activity. Workspace audit records include actions, their actor and timestamps. They support approval and delivery history, workspace administration and activity reports.
• Workspace and content data. We store the workspaces connected to your account and the content needed to operate them, including posts, organic content, configured channels, delivery attempts, approvals, and audit records.
• Customer support. When you email contact@postifynow.app, we process your email address, message and any information you choose to include to respond to your request.
• Billing data. A one-time 7-day workspace trial is handled in PostifyNow and does not collect a card. Paid plan checkout and subscription billing use Stripe. PostifyNow stores billing references and subscription state needed to apply entitlements; it does not receive full card numbers from Stripe. These billing references, plan and subscription records apply to the same workspace account when accessed through the web or native app. When native subscriptions are enabled, RevenueCat processes your workspace billing identifier and store purchase and subscription records to confirm access and provide subscription analytics, such as purchase history and charts. This identifier can be linked through PostifyNow to the workspace billing owner. Apple processes App Store payments and Google processes Google Play payments.
• Native notifications. The native app stores a random installation identifier and notification binding and tap identifiers in app preferences. The installation identifier can be created when notification status is checked, before push permission is granted. When push is configured and permission is granted, the app sends its installation identifier, device token, platform, app identifier and notification environment to PostifyNow to register notifications for your signed-in account and workspace. The server stores an encrypted token and a token hash. Apple Push Notification service (APNs) on iOS and Firebase Cloud Messaging (FCM) on Android receive the device token and notification delivery data, including notification and binding identifiers and an expiry time; push messages do not contain your post text. Signing out clears local notification bindings and attempts to revoke the server registration; it does not remove the installation identifier.
• Connected services. Connection data is processed when you configure a service connection. A connected service may receive a request when you use a configured workflow. Demo connections return simulated delivery results for testing and demonstration.

Why we use it

We use this information to authenticate you, keep workspace access boundaries intact, provide content and delivery workflows, apply plan entitlements, protect the service, and respond to support requests.

When information is shared

Google and Apple provide sign-in when enabled. Resend receives your email address and verification message to deliver account verification and password-reset emails. Stripe handles paid web billing when enabled. Configured social providers receive authorization and account-verification requests; PostifyNow stores the selected account identifiers, names and encrypted grants within the workspace. Hosting, storage, networking and monitoring providers process information needed to run and secure the service. Current demo publishing shows simulated results. Research, drafting and website-content previews do not send your content to external AI services. We do not sell personal information or use sign-in data for advertising.

Cookies and session security

PostifyNow uses a necessary session cookie to keep you signed in. Production sessions are configured with Secure, HttpOnly and SameSite=Lax protection. The session ends when you sign out or it expires. The optional demo is limited to the current browser tab and is separate from an account session.

Read the cookie and storage page for the current inventory, lifetimes and optional measurement controls. Language, appearance and selected billing offers are preferences; they contain no account credentials. Cookie settings

Your requests

To ask about the information associated with your account, request a correction, or request account data deletion, contact support. Account deletion is not currently a self-service action, so support must review the request and any related service or legal requirements.

Policy updates

We may update this page when the product or its data flows change. The version published at this address is the current description.