This policy describes REMVIL's Android and iOS apps, optional account services and privacy support pages. REMVIL provides personal reminders, car checklists, parking tools, medication schedules, and shared plans.
1. Information stored on your device
Personal reminders, car checklists, parking details and coordinates, medication schedules and intake confirmations are stored locally. Creating an account does not automatically upload or back up all these records to our servers.
If you export records, send a supported reminder or include information in a message, the selected information leaves this local context. The destination you choose handles exported files. Messages and attachments may contain health or other sensitive information if you include it.
Protect your device and exports. Server account deletion does not remotely erase local records, exported files or recipients' copies. Android cloud backup is disabled for the current app. On iOS, app data may be included in device or iCloud backups according to your Apple device settings. These system backups are handled by Apple and are separate from REMVIL account services. Signing in to REMVIL does not enable automatic server backup of all local records.
2. Accounts and shared information
Guest mode provides local features. For an account we process your email, username, display name, internal account identifier, password hash, email-verification status and session credentials. A profile picture is optional. Passwords are stored as protective hashes.
Social features process friend requests, friendships, invitations, blocks, direct and group messages, selected photos, voice recordings, videos, shared reminders, group events, responses, and the locations or notes you enter. Related identifiers and timestamps organise these features.
Your username, display name and picture can be visible through supported profile and discovery features. Shared content is available to authorised recipients and event participants. They can retain downloaded copies or screenshots.
Reporting content sends the reason, explanation, relevant content snapshot and account identifiers for restricted operator review. Reporting tools do not mean that every conversation is continuously monitored.
When you email REMVIL for support, privacy questions or account deletion, we receive your sender address, message and any attachments you choose to include. We use that information to respond to your request and, when needed, verify account ownership. Do not include passwords or verification codes.
3. Location and maps
In version 0.2.5 and later, location is requested when you choose to capture your parking position in the open app. You can instead mark the map manually or save only a note and timer. Automatic car departure reminders and background location access have been removed.
Version 0.2.3 removes Home and Office checklists, map setup and departure reminders. Older Home and Office records remain locally and in exported backups; the updated app excludes them from its interface and disables their alerts. Older installed app versions may still include departure reminders and use previously granted background location access until updated. The updated app cancels old monitoring registrations and retains saved parking coordinates, notes and timers.
Saved parking coordinates are handled on the device. REMVIL does not automatically share your current precise location with other users. Location information that you deliberately put in shared content is visible to its recipients.
OpenStreetMap receives tile requests including your IP address and the requested map area. These requests can reveal the area you view. Opening directions in another maps service passes the destination and related requests to that service.
You can change location permissions in Android or iOS settings. On iOS, REMVIL requests while-in-use access for the open parking map; it does not request Always location access. Dependent features may then stop working.
4. Notifications, permissions and technical data
Local reminders are scheduled on the device. Notification and alarm permissions support their delivery; timing and sound also depend on operating-system battery restrictions, notification settings, Do Not Disturb or Focus, and silent mode. REMVIL does not use iOS Critical Alerts to bypass these settings.
If you enable social push notifications, Google Firebase Cloud Messaging processes registration tokens and installation identifiers. On iOS, Apple Push Notification service (APNs) also processes the information needed to deliver notifications, including device tokens. Our server associates your notification registration with your account. Push payloads contain generic text rather than private message contents. Disable remote notifications in the app or change Android or iOS notification permissions to control them. Signing out, disabling social notifications or deleting an account removes the relevant server registration; Firebase and Apple retain provider records under their own lifecycles.
Microphone access is used when you choose to record audio. Camera, photo and file-selection features access content you choose to capture or attach.
Network services receive technical information such as IP addresses and requests. Application logs record request time, route pattern, result and duration. They do not intentionally record passwords, authentication tokens or message bodies.
5. Purposes and legal bases
Information is used to provide requested features, verify and recover accounts, deliver notifications and account emails, maintain reliability, prevent abuse, handle reports, respond to privacy requests and comply with applicable legal obligations.
Where law requires a legal basis, the relevant basis depends on the activity: providing a requested account service, legitimate interests in security and reliability, legal obligations, or consent where required for optional processing. Where consent applies, it can be withdrawn without affecting earlier lawful processing.
REMVIL does not use the contents of reminders, medication records, messages or saved parking locations for advertising. iOS builds contain no advertising SDK. Android builds that include advertising are described in section 13; older Android builds without advertising do not perform this ad processing. REMVIL does not implement a separate app-usage analytics event system or use automated profiling to make decisions with legal or similarly significant effects.
6. Providers and recipients
- Contabo: application hosting and the PostgreSQL database for accounts and shared services.
- Cloudflare: network security and request delivery; R2 stores uploaded media and encrypted server backups.
- Resend: recipient email addresses and transactional verification or recovery messages.
- Zoho Mail: the support mailbox, including sender addresses, support and privacy correspondence, account-deletion requests and attachments you choose to send.
- Google AdMob and User Messaging Platform: advertising and advertising-privacy choices in Android builds that include ads; see section 13.
- Google Firebase Cloud Messaging: device registration and installation information for optional notifications.
- Apple: APNs delivery for iOS social notifications and, according to your device settings, Apple-managed device or iCloud backups.
- OpenStreetMap: map tiles, requested map areas and network information.
- Services you select: external navigation, exports, file destinations and email services.
Authorised operators can access information needed for support, administration, security and report handling. Information may also be disclosed when required by applicable law or necessary to protect users' rights. Content you intentionally share is disclosed to its recipients.
Providers operate internationally and may process information outside your country. Processing locations and applicable transfer safeguards depend on the actual services and agreements. Contact the operator for information relevant to your data.
Provider notices: Cloudflare, Resend, Zoho, Firebase, Apple, OpenStreetMap.
7. Security
Protections include HTTPS, password hashing, restricted administrative access, authorisation for shared data, private media storage, short-lived media links and encrypted server backups.
Chats are not end-to-end encrypted. These measures do not mean all local databases or exported files are encrypted. No system can be guaranteed completely secure. Do not send passwords or recovery codes in a support request.
8. Retention
- Local records and exports: remain until removed through local controls or the storage service you selected.
- Accounts and shared content: remain as needed for the service until removed through supported controls or account deletion, subject to the exceptions below. Signing out or uninstalling does not delete an account.
- Session and device records: expire or are removed through relevant sign-out, notification-disable and account-deletion actions. Firebase installation records and APNs device tokens have separate provider lifecycles.
- Support and privacy correspondence: the operator handles requests sent to support@remvil.app. Closed correspondence, including account-deletion requests and their attachments, is deleted after 90 days unless it is still needed for a dispute or a legal obligation. Any such exception is limited to the information and period needed for that purpose.
- Report evidence: up to 90 days after resolution, no more than 180 days from creation. Moderation audit records may remain for up to 365 days, including after account deletion.
- Operational logs: rotate by size, with up to three 10 MB files per configured service. This is not a fixed number of days. Providers have their own relevant operational retention.
- Encrypted backups: routine rotation is configured for 14 days locally and 30 days in cloud storage, preserving at least the newest three copies. Separately retained recovery copies require manual removal and are outside that schedule.
Deletion from the live system does not erase every backup immediately. Limited records may also be retained for legal obligations, security incidents, disputes or rights requests.
9. Account deletion
In REMVIL open Profile → Settings → Account → Delete account. Enter your password and the requested DELETE confirmation. You can also email support@remvil.app with the subject REMVIL account deletion, using the email address associated with your account. Include your username if you know it. You do not need to install the app to make this request. The operator handles these requests and may verify account ownership before deletion. Do not send your password or verification codes.
Deletion invalidates sign-in credentials and removes associated sessions, notification registrations, friendships, pending invitations, direct conversations and the account's uploaded media and group messages. Owned group events are cancelled and their title, location and note are cleared. Other participants' unrelated contributions remain.
A minimal de-identified reference can remain for shared-event relationships. Original email, username, picture and usable password credentials are removed or invalidated, and the display name becomes “Deleted account.”
Media access is revoked immediately, but previously issued links can remain valid for up to 60 seconds. Storage removal is queued with a one-hour safety delay and retried if necessary. Retention exceptions above still apply.
Local records, exports and recipient downloads are not remotely erased. Export records you want to keep before deletion and separately remove unwanted local copies.
10. Your choices and rights
You can use guest mode, choose what to share, change supported profile information, block users, report content, control permissions, disable optional notifications and delete your account. Export controls let you keep copies of supported local records.
Depending on applicable law, you may have rights to access, correction, erasure, restriction, objection, portability, withdrawal of consent and a complaint to your local data-protection authority.
Contact the operator using the privacy address at the top. Proportionate account-ownership verification may be needed. Do not include passwords, verification codes or unnecessary sensitive records in your request.
11. Children and health information
REMVIL is not designed for young children. Parents or guardians who believe a child provided personal information can contact the operator for assessment and appropriate action under applicable law.
Medication reminders are organisational tools. They do not diagnose conditions or recommend treatment. Medication schedules remain local unless you intentionally export or share information. Take care when selecting recipients for health information.
12. Website and changes
The REMVIL website contains no advertising, third-party fonts or sign-in form, and does not use analytics to track visitors. Hosting and network-security services still process the requests necessary to serve and protect it. External links and email actions lead to separate services.
Changes to the app, providers or practices may require policy updates. The effective date will identify the current version. Material changes will be handled with any notice or consent required by applicable law.
13. Android advertising
Advertising is being prepared for the free Android version of REMVIL and is introduced through app updates. This policy update does not itself switch on advertising in an installed app. iPhone and iPad builds remain free of advertising.
Android builds with advertising use Google AdMob for a labelled banner on the home page. REMVIL requests non-personalized ads. Non-personalized does not mean that no data is processed: Google may collect and share IP addresses (including an estimated general location), advertising and other device or account identifiers, ad and product interactions, and diagnostic or performance information for advertising, measurement and fraud prevention. This information is transmitted using TLS. Google handles provider records under its own privacy notices and retention practices.
REMVIL does not pass reminder text, medication schedules or intake history, chat content, email addresses, REMVIL account identifiers, or precise parking coordinates to AdMob as advertising inputs. We have selected Google as the advertising partner and do not integrate additional mediation partner SDKs in this version.
Google's User Messaging Platform checks which advertising privacy choices are needed. Where required, it presents a consent message before ads may be requested. You can consent, refuse consent, or manage the available purposes. Refusing consent does not remove access to free reminder features. Depending on the applicable choice and Google's rules, advertising may be limited or unavailable.
When Google requires privacy options, open Profile → Advertising privacy choices to review or withdraw the advertising choices on that device. You can also reset or delete the Android advertising ID in Android settings. Google privacy choices are separate from REMVIL notification permissions and any future optional cloud-sync choices.
Users with verified active Android Pro access are not shown banners and REMVIL does not initialize the advertising SDK for them. A privacy-availability request to Google's consent service can still be made so that a returning Pro user can change previous advertising choices. If subscription status cannot be verified, REMVIL suppresses banners until the status is known.
Provider information: Google Privacy Policy, How Google uses information from sites and apps, and Google Mobile Ads SDK data disclosure.