Marshall McKinley Works

Remply Privacy Policy

Effective date: October 4, 2026

Marshall McKinley Works LLC, doing business as Remply (“Remply,” “we,” “us,” or “our”) provides a reminder and reply-assistance application. This Privacy Policy explains how we collect, use, disclose, and protect information when you use Remply.

1. Information we collect

Remply processes screenshots or images that you choose to submit for AI analysis, text that you type or paste and submit for a suggested reply, and the resulting extracted text, suggested replies, or reminder details. An image or message may contain information about you or other people. Submit only content you have the right to share.

Remply does not require a Remply account. Saved reminder titles, notes, categories, dates, times, urgency and completion status, local notification identifiers, app settings, local usage counters, onboarding status, and the version and time of your legal acceptance are stored on your device. Manually created reminders are not sent to our AI backend merely because you save them.

The app creates a persistent installation identifier and obtains an anonymous RevenueCat customer identifier. It sends these identifiers to our backend with AI requests. The backend also receives your network IP address and, for screenshot-reminder analysis, your device timezone. It stores keyed hashes of installation, network, or billing identifiers together with request counts, usage-bucket types, bucket dates, and update timestamps. These hashes are pseudonymous identifiers, not anonymous information, because they allow repeated activity to be associated with the same installation, network, or billing record.

RevenueCat receives subscription and transaction information, such as receipts or transaction identifiers, products, purchases, renewals, expiration, restoration activity, and entitlement status. Its iOS SDK also sends technical metadata, including the Apple identifier for vendor (IDFV), device model, operating-system and app versions, locale and storefront information, SDK configuration, and system tracking-consent status. Customer records may include last-seen activity. No name or email address is required by Remply for subscription setup.

Our hosting and service-provider systems receive connection and operational information. Application logs include request timestamps, request IDs, methods, URL paths without query strings, response status, response duration, server/process information, and error details. Ordinary request logs are configured to omit request bodies, headers, IP addresses, and installation or billing identifiers. Error details can nevertheless contain identifying information or content fragments, and hosting-level records may include IP-related information.

Subscriptions are processed through Apple or the applicable app store and RevenueCat. Remply does not receive or store your full payment card number. If you contact us for support or a privacy request, we receive the contact information and other information you provide in that communication.

2. Screenshots and AI processing

When you submit a screenshot, image, or typed or pasted message for AI processing, our backend sends that content and task instructions to OpenAI. For screenshot reminders, instructions include your timezone and the current date and time so the service can interpret dates correctly. The backend does not explicitly include your Remply installation ID, RevenueCat customer ID, or phone IP address in the OpenAI prompt, but the content itself may identify you or another person.

Remply does not intentionally create a persistent backend archive of submitted screenshots, messages, or AI results. They are processed for the request and returned to the app. This does not mean that service providers retain no content: error logs may contain content fragments, and OpenAI has its own retention rules.

OpenAI states that, by default, API abuse-monitoring logs may contain prompts, responses, and related safety metadata and are retained for up to 30 days, unless longer retention is required by law or reasonably necessary to protect its services or others. Image inputs are screened for child sexual abuse material; images flagged as potentially containing such material may be retained for manual review, including under certain reduced-retention arrangements. API features may also use temporary application state or prompt caches.

OpenAI states that API content is not used to train or improve its models by default unless the API customer explicitly opts in. Retention and data-sharing controls depend on the API account configuration and provider terms. Remply does not promise Zero Data Retention or that every provider copy is deleted immediately after a request.

Saved reminder details remain on your device until you delete them or remove app data. Suggested replies and selected-image previews may remain in the current app session; copying or sharing a reply sends it to the clipboard or destination you choose. Original images remain in your photo library until you delete them, and operating-system or image-picker caches may have separate lifetimes.

AI-generated results may be incomplete or inaccurate. Review generated reminders and replies before relying on them or sending them.

3. How we use information

4. Service providers

OpenAI processes submitted content and generates results. RevenueCat manages subscription status, purchase validation, entitlements, restoration, and subscription reporting. Apple and the applicable app store provide distribution and payment services. Replit hosts our backend and database and provides operational monitoring; our backend subscription checks also pass the RevenueCat customer identifier through Replit’s connector service to RevenueCat.

Provider processing, retention, backups, security measures, and legally required disclosures are subject to the applicable service agreements and provider terms. Provider information is available at https://developers.openai.com/api/docs/guides/your-data, https://www.revenuecat.com/privacy, and https://www.revenuecat.com/dpa.

The current Remply app does not display advertisements or include advertising-attribution integrations. Its installation and subscription identifiers are used for functionality, security, purchase validation, and subscription reporting, not to target advertisements. Sending information to a service provider, or using IDFV for device identification, is not by itself cross-app advertising tracking.

5. Notifications

If you enable notifications, Remply schedules local alerts using your device’s notification system. The current implementation does not register a remote push token or send your reminder titles and notes to a remote push service. Notification text may be visible on your lock screen depending on device settings. Delivery depends on permissions, device settings, and operating-system restrictions. You can disable notifications in Remply or your device settings.

6. Retention and deletion

Submitted content is not intentionally archived by Remply after request processing, subject to possible content fragments in error records and the provider retention described above. Saved reminders, preferences, legal-acceptance records, and the installation identifier remain locally until you delete the relevant data or remove the app’s data. Device backups and restores may preserve or restore local data.

Backend usage records contain keyed identifier hashes, counts, and timestamps. They currently have no fixed automatic deletion schedule. Minute, day, or month quota resets do not delete historical records. Records remain until removed through an operational or applicable deletion process; they are not automatically deleted when you uninstall the app.

Replit documents 30-day retention for deployment application logs. This is not a promise that all hosting metadata, database backups, provider operational records, or legally retained copies have the same retention period. Separate infrastructure and backup retention periods depend on the applicable provider terms and configuration.

RevenueCat and the app store maintain purchase and customer records independently of local app data. Their retention is subject to service agreements, backup practices, and legal requirements; Remply does not promise a fixed automatic deletion period for those records. OpenAI retention is described in section 2.

You may contact us about privacy questions or deletion requests at support@marshallmckinleyworks.com. Because Remply does not require accounts, we may need sufficient information to locate and verify the relevant installation or subscription record. Where applicable, we will coordinate requests with service providers, subject to legal obligations, fraud prevention, and backup limitations. Deleting the app does not itself delete provider records or cancel a subscription.

7. Children

Remply is not directed to children under 16. You may not use Remply if you are under 16.

8. Your privacy rights

Depending on where you live, you may have rights to request access to, correction of, or deletion of personal information, or to ask questions about how your information is handled. Contact us at support@marshallmckinleyworks.com.

9. Security

We use reasonable administrative, technical, and organizational measures to protect information. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

10. Changes and contact

We may update this Privacy Policy from time to time and will update the effective date when changes are made. Questions may be sent to support@marshallmckinleyworks.com.

Remply support