# Fwrd privacy Last updated: 2026-08-27 Canonical page: https://www.fwrdsms.com/privacy ## In short - Fwrd is accountless. The customer never signs in, and Fwrd holds no customer identity. - Messages are processed on the customer's iPhone and sent to customer-configured destinations. Fwrd operates no relay and no server that receives them. - Neither the iPhone app nor the website runs an advertising or analytics SDK, and neither tracks the customer across apps or websites. ## Message data A customer-created Apple Shortcuts Message automation passes the message text and sender value into Fwrd's Forward Message action. Fwrd uses those values to build a request for each active destination and sends it directly from the iPhone. The customer chooses the matching criteria, so the customer decides which messages reach Fwrd at all. The app does not request Contacts access and cannot read messages the automation does not pass in. ## Where forwarded messages go Direct destinations receive an HTTPS request from the iPhone containing the message text, the sender, and a timestamp. Every destination is customer-owned; Fwrd runs no shared webhook, bot, or inbox. Once a message reaches a destination service it is held under that service's privacy policy and retention rules, and Fwrd cannot reach or delete it. Native Shortcuts destinations are sent by Apple's or the provider's own action, under their policies. ## Data stored on the iPhone Everything the app stores stays on the device and is not transmitted to Fwrd: - A local forwarding log containing message text, sender, destination, time, and delivery result, plus attempt count and any returned error. It is stored in the app's local data on the iPhone, not on Fwrd servers, in the app's private container with iOS file protection. At most 500 entries are kept, and entries older than 30 days are dropped. - Destination settings: labels, chat identifiers, recipients, and setup progress. - A counter of free forwards used in the current calendar month. - A record of whether the Fwrd Pro entitlement was active when it was last checked, so forwarding works when an automation runs offline. ## Destination credentials Webhook URLs and bot tokens are treated as secrets. They are stored in the iOS Keychain on that device only, are not synced to iCloud, and are not sent to any Fwrd system. Destination settings store only a reference to the Keychain entry, never the secret. Editing or deleting a destination releases the entries it no longer needs. ## Subscriptions and purchases Fwrd Pro is sold through the App Store. Apple processes payment; Fwrd never sees payment methods, card details, or Apple Account credentials. Fwrd uses RevenueCat to determine entitlement. The RevenueCat SDK sends App Store purchase and receipt information, an anonymous identifier it generates for the installation, and basic device and app metadata such as iOS version and app version to RevenueCat's servers. Fwrd supplies no name, email address, or message data to RevenueCat and sets no identifier of its own, so the identifier is random and is not linked to a waitlist email address. Purchases belong to the customer's Apple Account, which is what lets Restore Purchases work without a Fwrd account. ## Notifications Forwarding notifications are scheduled locally on the iPhone. There is no push server, and a notification names the destination rather than repeating message text. Notification permission is optional and revocable in iOS Settings. ## Deleting app data The forwarding log can be cleared and destinations can be deleted inside the app at any time; deleting a destination also releases its stored credentials. Deleting Fwrd removes the forwarding log, destination settings, usage counter, and stored subscription state. Neither removes data already delivered to a destination service, which must be removed there. ## Website and waitlist When someone joins the waitlist, Fwrd stores the submitted email address in Supabase to send a product-launch notification and deliver an eligible launch offer, and sends an internal notification containing the submitted address to the configured Fwrd inbox. Fwrd does not sell the email address or use it for unrelated marketing. The waitlist email is a notification and offer-delivery channel, not an app account or app identity. The feedback form sends the provided name, reply email, selected topic, and message to the Fwrd inbox. Real message contents and destination credentials should never be entered into website forms. Waitlist email addresses are retained until the launch notification has been sent or until deletion is requested. ## Website analytics The website runs no analytics. Fwrd loads no analytics or advertising script, sets no tracking cookie, and sends visits to no measurement service. One caveat: Cloudflare fronts the site and automatically inserts its own Web Analytics beacon into the page. The site's Content Security Policy blocks that script from loading, so it does not execute and does not measure the visit. Beyond that, Vercel and Cloudflare keep the operational request logs any web host keeps in order to serve and protect the site. ## Service providers The iPhone app uses Apple for App Store purchases and RevenueCat for subscription status. The website uses Vercel for hosting, Cloudflare for DNS and content delivery, Supabase for waitlist email addresses, and Resend for feedback and internal waitlist notifications. ## Deletion and contact To request deletion of a waitlist email address or ask a privacy question, email support@fwrdsms.com.