Privacy Policy

Monenos And Monenos Dev

Monenos and Monenos Dev use the same Monenos service. Signing in with the same account accesses the same partner relationship and shared service data. Each installation has its own permissions, notification token and local files. Actions in Monenos Dev, including account deletion, affect the shared account and partner; testing is not an isolated copy of your data. Uninstalling an app does not delete your account.

Monenos is a private space for two adult partners. You control whom you pair with. Only one partner can be connected at a time.

We use your account ID, name and email to authenticate and pair accounts. When you choose Sign in with Apple on iOS, Apple and Firebase process authentication. We receive the account identifier and the name and email Apple makes available; if you choose Hide My Email, the email may be an Apple private relay address. Firebase stores the messages, voice notes, compressed photos, couple settings, plans, requests, reactions and timestamps you choose to share. Device notification tokens and language are used to deliver alerts. Google/Firebase may process service logs and device/network information to operate and secure the service.

QR scanning uses Google ML Kit. When you use the scanner, the SDK may collect device and app information, installation identifiers, feature events, error codes and performance metrics for diagnostics and usage analytics. Firebase also uses installation identifiers to deliver notifications. We do not use this information for advertising.

Your paired partner can see the content you share. Firebase/Google process data on our behalf. Authorized service administrators can access server data for operations, deletion and reported abuse. Monenos does not provide end-to-end encryption. Connections to the Monenos service use encrypted transport. This is not a guarantee about external websites that you choose to contact.

We do not sell your data or use your private messages for advertising. Monenos does not operate its own advertising placements. Optional embedded YouTube videos may show advertising provided by YouTube, as explained below. Photos are selected through the system picker; the camera is used for QR pairing and photos you choose to send, only when you grant permission. We store your terms acceptance by account and policy revision. Home-screen widgets may show your couple photo if enabled, but never message text. Microphone access is used when you choose to record a voice note or join a voice/video call; camera access is also used for video calls. You preview a recorded voice note and choose whether to send it. Calls transmit live after you choose Start, Join or Answer. Your quick-message list is private to your account; opening Find the words does not notify your partner. We store your personal unread-reminder interval and postponement time. Choosing Remind me later sends your partner an automatic chat reply. Notifications are optional and your device settings control permission and sound. Notification previews should be considered visible to anyone with access to your phone.

Blocking stops new communication in both directions and hides the shared space until each person who blocked removes their own block. Messages already downloaded, screenshots and notifications already delivered cannot be recalled. Reports include the reason and text you submit, your account ID and couple ID. They are visible to authorized support staff, not your partner. Do not include unnecessary sensitive information.

Either partner can choose to unpair after confirming in the app. Unpairing closes access to the old shared space for both people, ends its calls and connections, and keeps each person’s account. The other person receives a notice; if delivery is missed, Monenos checks the relationship again when they reconnect. Unpairing seals the former shared space rather than deleting it. Sealed service data remains until an explicit account-deletion request removes it. Unpairing does not recall downloaded copies, screenshots or delivered notifications.

Account deletion removes your Monenos authentication record, your current shared space and former sealed shared spaces for both participants: messages, voice notes, photos, plans, requests and settings. The other person's account remains. A current partner becomes unpaired; a former partner’s newer relationship is preserved. Your Google or Apple account is not deleted. When you delete an account using Sign in with Apple in the app, we ask you to authenticate again and revoke the Apple authorization before submitting the deletion request. You can initiate deletion in Privacy & safety or at https://mone-app-com.web.app/delete.html. Processing normally starts promptly; contact support if it has not completed within 7 days. Content already copied to another device cannot be recalled. Infrastructure logs and provider backups may remain for their configured retention periods; they are not part of the live app's shared space.

Optional calendar connections synchronize plans created in Monenos, including dates, times, location, notes and the paired partner’s invitation address. Google Calendar or iCloud processes invitations and responses under its own policies. Calendar credentials are encrypted on our server and are not accessible to your partner. You can disconnect from the app. Disconnecting or deleting Monenos does not recall emails or erase event copies already delivered to an external calendar. Shared Counts and optional plan posters are stored in the couple’s private space. Opening a YouTube trailer contacts YouTube; playback occurs only when you choose it. The embedded player uses YouTube privacy-enhanced mode through youtube-nocookie.com. YouTube may process device and network information, including IP address and approximate location, video views, playback activity and advertising interactions. If YouTube serves ads within this player, its privacy-enhanced mode uses non-personalized ads; cookies or similar identifiers may still be used for frequency capping and aggregated advertising reporting. Privacy-enhanced mode does not mean that no data is collected. If you open YouTube outside the embedded player, YouTube’s own settings and policies apply. See Google Privacy Policy and YouTube Embedded Player Privacy Information.

Your optional couple profile contains the nicknames, couple name and individual profile photos you choose to add. Both partners can edit the shared profile. These names and pictures do not change your Google or Apple sign-in profile, and they are removed with the shared space.

WhatsApp is optional. If you add a WhatsApp number, Monenos stores it in your private couple space so your paired partner can open your WhatsApp chat. Only you can edit your number; you can remove it in Settings. Deleting the shared space deletes both stored numbers. Tapping the WhatsApp shortcut opens WhatsApp or its website with the selected number, under WhatsApp’s own privacy policy. Monenos does not read your WhatsApp conversations or contacts, send WhatsApp messages automatically, or start calls automatically.

For voice and video calls, Monenos uses the communication provider accepted by both partners. ZEGO calls transmit audio and video through ZEGOCLOUD, which processes pseudonymous participant identifiers, a random room identifier and the device/network information needed to operate calls. WebRTC calls transmit audio and video between the connected peers. Firebase stores provider agreement and connection/call signaling to authorize the current pair. Google and Apple may deliver incoming-call invitations and process the device tokens and call identifiers needed for notification delivery. Monenos does not record calls or save call audio/video in chat. This is not a claim of end-to-end encryption for the whole app or zero provider log retention. ZEGOCLOUD's privacy policy is available at https://www.zegocloud.com/privacy-policy.

Calls transmit live only after you choose Start, Join or Answer. Normal incoming-call mode can keep call audio active while the app is in the background or the phone is locked; background video is suspended. Chat Join Only (Test) requires both partners to open chat and ends the call when the app leaves the foreground. You can end a call deliberately in either mode. Changing the communication provider does not itself answer a call or activate microphone/camera capture.

When both partners select WebRTC, direct text and its receipt history are stored in app-private local files on each phone and transmitted through the peer connection. Firebase carries setup signaling, not that direct text or call media. Other features, such as shared profiles and plans, still use the couple's Firebase space. Switching providers keeps their chat histories separate. Copies already stored on another phone cannot be recalled.

Cloudflare And WebRTC Connections

WebRTC uses Cloudflare STUN to discover network connectivity. When the partners select the relay route, Cloudflare Realtime TURN relays encrypted WebRTC packets for text and calls. Cloudflare processes connection metadata, including network addresses, ports and session timing; it cannot read the encrypted media or data-channel content. Monenos does not operate a Cloudflare chat archive. Direct text history stays in app-private files on the participating phones; Firebase stores authorization and connection signaling. Direct connections can reveal network addresses to the other peer. Other shared features continue to use Firebase.

Provider operational logs are separate from your chat and are governed by the applicable provider retention practices. We do not promise zero logs or immediate erasure of every backup. Providers may process information outside your country. See Cloudflare TURN Privacy Information, Cloudflare Privacy Policy, Firebase Privacy Information and ZEGOCLOUD Privacy Policy.

Keep a secure screen lock on your device. Contact support for privacy, safety and deletion requests: orlando.rodriguez@empowerhr.net. Operator: EMPOWER HR. Last updated: October 8, 2026.

Personal Appearance And Affection

You can optionally choose a gender value used only for Spanish affection wording. Prefer Not To Say is the default. Your choice and chat appearance settings are private to your account. Affection messages retain the wording selected when sent. A background photo is stored with your private appearance settings.

Link previews are fetched by the sender's phone. The linked site can see that phone's network address and the requested URL. A preview of an HTTP link uses that site's unencrypted connection; avoid sharing private tokens in URLs. The receiving phone displays the supplied preview without fetching the site. Opening a link deliberately uses your browser and the site's privacy policy.

Just For You photos can be retrieved once by the recipient account. The server removes the image when it is opened, and the viewing app clears its image cache afterwards. Screenshots, another camera and copies made outside Monenos cannot be fully blocked. Delete For Me hides a message on this phone only.

Selfie Together requires both people to enable their cameras and each person to approve their own photo. No microphone is used. The completed strip is saved in Our Space. Motion sensors can tilt hearts or shake a reasons jar; this motion stays on your phone. Account/shared-space deletion also removes stored appearance, wording and selfie data.

AI Master Dev Privacy Disclosure

Prepared October 12, 2026. This section applies to AI Master Dev (Android package ai.master.dev), a development client for viewing authorized Codex chats and process information from a connected computer. The separate Monenos disclosure on this page continues to apply to Monenos.

Operator: EMPOWER HR. Privacy Contact: orlando.rodriguez@empowerhr.net.

Information Used By AI Master Dev

Google sign-in provides a verified Google account identifier and email address. AI Master uses these to authenticate access and obtain the computer connections authorized for that account. Having a Google account does not itself authorize access to a computer. The app also uses an installation identifier, authentication challenges, session identifiers and access and renewal credentials to establish and maintain its authenticated connection.

When you select an authorized computer or chat, AI Master sends the relevant connection and chat identifiers and any pagination cursor to its backend. It receives connection names and availability, chat titles, project names, process status and reported progress, and conversation history. Conversation history can contain personal information or other information previously entered into the connected Codex system. Do not use development testing to expose confidential or third-party information.

Authentication and session material is kept behind the native protected-storage boundary. The app displays account email and connection and conversation information. Draft text in the current development interface is maintained in app memory. Signing out clears active client session state; it does not delete the underlying Codex chats.

How Information Is Used And Transferred

Information is used for sign-in, account and connection authorization, session renewal and revocation, and displaying the selected computer's chats and process information. The Android client communicates with the AI Master Dev backend over HTTPS. Google handles the Google sign-in operation. The authorized computer and its existing Codex services provide chat and process information. Those systems' own terms and privacy practices apply to their processing.

The current Android development interface supports viewing authorized chats. Shared backend code also contains operations for replies, visibility and archiving; availability depends on the delivered client and the selected connection's capabilities. If reply functionality is enabled in a later release, submitted text and its delivery identifiers will be sent through the backend to the selected computer and its Codex services. A reply's acceptance is separate from any subsequent AI response.

Account And Session Data Deletion Requests

AI Master's backend maintains authentication, authorization and session records. Access credentials have a limited lifetime; that lifetime is not a promise that all associated backend records are deleted. The current development implementation does not provide a fixed automatic purge period for account, authorization or session records. Revoking or signing out of a session does not by itself erase the underlying Google account or Codex conversation records. Those conversations remain under the connected computer's and Codex system's existing retention controls.

To request deletion of your AI Master account and session data, email orlando.rodriguez@empowerhr.net. Include AI Master Dev, your sign-in email address and your request to delete the AI Master account and session records. Support handles verified account and session deletion requests and must verify that you own the relevant account before acting. Do not send passwords, authentication tokens or confidential conversation contents. This request does not delete your Google account or the connected Codex conversation records; those independently controlled records retain their own rules and request channels. The current DEV service does not promise automatic deletion or a fixed completion deadline. You may use the same support address for privacy questions or a request status update.

Permissions And Development Scope

The reviewed Android manifest requests Internet access. The reviewed client does not request location, contacts, microphone or camera permissions. The current package does not include an advertising or analytics SDK in its Flutter dependencies. Infrastructure and service providers may process connection metadata as part of operating their services.

AI General Privacy Disclosure

Effective November 3, 2026. Controller and privacy contact: EMPOWER HR, SRL, orlando.rodriguez@empowerhr.net.

This supplemental disclosure covers EMPOWER HR, SRL's AI General Dev (Android package and Apple bundle ID ai.general.dev; Microsoft identity EMPOWERHRSRL.AIGeneralDev) and AI General (Android package and Apple bundle ID ai.general.pro; Microsoft identity EMPOWERHRSRL.AIGeneral) when connecting to the authorized-computer services described below. The existing AI Master Dev disclosure remains available separately on this page.

Account And Connection Information

Sign-in and access to configured computers use an authorized Google account. The service processes account identifiers and email addresses, authorized computer and connection identifiers, and session information to authenticate users and enforce access. A signed-in account does not automatically grant access to every computer or conversation.

Conversations And Instructions

The app and connected service process the conversation identifiers, history, process status and reported progress requested by the user. Where a delivered client supports sending instructions or managing a conversation, the submitted content and requested action are sent to the authorized connected service or computer. Availability depends on the client version and connected service. Do not submit information you are not authorized to share with that computer or with the AI service configured for it.

Sessions And Local Storage

Installation identifiers, authentication challenges, session identifiers and access or refresh credentials may be processed to establish and maintain a signed-in session. Storage mechanisms vary by platform and delivered version. Signing out ends the app's signed-in access; it does not by itself delete server-side history or records held by a connected computer or AI provider.

Service Providers And Network Transfers

Google handles Google sign-in under its own privacy terms. The app communicates with the configured EMPOWER HR service and authorized computers to provide its features. If a connected computer uses an external AI service, the content sent to that service is also subject to its configuration and privacy terms. This disclosure does not promise a particular AI provider, storage location, or provider retention setting for every connection.

Retention And Data Deletion Requests

No fixed automatic deletion period is promised by this disclosure. Account, connection, conversation and operational records may have different retention requirements. To request access, correction or deletion, contact orlando.rodriguez@empowerhr.net and identify AI General or AI General Dev, your sign-in email address, and the account, session or other data you want deleted. We must verify account ownership before acting. Deleting app/service records does not delete your Google account. Do not include passwords, access tokens or refresh tokens. Requests concerning information held by a separately configured computer or provider may require that operator's action.

Permissions And Changes

Network access is needed for sign-in and remote connections. Any additional platform permission is governed by the delivered app and the permission prompt presented to the user. The separate Monenos and AI Master sections describe those products; their features and permission statements do not apply automatically to AI General. This notice will be updated when the applications' data practices change.

AI Army Privacy Disclosure

Effective November 3, 2026. Operator and privacy contact: EMPOWER HR, SRL, orlando.rodriguez@empowerhr.net.

This section covers AI Army Dev (Microsoft identity EMPOWERHRSRL.AIArmyDev) and AI Army (Microsoft identity EMPOWERHRSRL.AIArmy), the computer agent used with authorized controllers such as AI General. The separate Monenos, AI Master and AI General sections remain in effect for those products. Available capabilities depend on the installed version, configuration and permissions granted to a controller.

Computer Registration And Account Information

Registration and owner approval process computer and request identifiers, public signing keys and signatures, computer name, operating system and version, processor architecture, application version, and available computer manufacturer and model information. Google enrollment associates the request with a verified Google email address and an account identifier derived from that account. These records identify the computer and let its owner review and control access. A Google sign-in alone does not authorize remote commands.

Remote Commands And Computer Content

Within the configured authorization, AI Army can report computer and process status, run diagnostics, start or stop Codex, restart the computer, and pass work instructions to the selected runtime. Supported work can include reading or creating conversations, returning conversation history, sending a reply, and working in an allowed project folder. Commands and responses can contain prompts, conversation text, project or folder paths, process information, results and errors. Work executed by the selected runtime can read or change files within its granted access. Only authorize controllers and share folders or content that you are permitted to expose to those controllers and services.

Local Records And Recovery

The computer maintains device and controller credentials, authorization grants, preferences, allowed work-folder settings, and pending-operation and recovery records. Operation journals retain identifiers, command types, status and ordering information to avoid losing or repeating uncertain operations. Conversation and project records may also remain in the connected Codex runtime or project folders. A connection ending, an authorization expiring, or an operation finishing does not mean that all of these records are erased.

Network Transfers And Service Providers

Enrollment, authorization and relay operations communicate with the configured EMPOWER HR service over HTTPS. Approved connections may also use SSH to the authorized computer. Requested command content and results are transferred between the agent and the authorized controller through the configured route. Network and service operators may process connection metadata when delivering these services.

Google handles Google sign-in. The selected Codex or other configured AI runtime processes the work submitted to it under its own service settings and privacy terms. Where ChatGPT prompt suggestions are enabled and authorized, the selected model receives the stated goal, latest user prompt and latest assistant reply to produce a suggestion. Account identifiers, email and access or renewal credentials are used to connect that account. Turning off a connection does not by itself delete records already held by an AI provider. Provider retention and processing locations depend on the chosen service and account settings; this notice does not promise one setting for every computer.

Retention And Data Deletion Requests

No single automatic deletion period is promised for all AI Army records. Enrollment, authorization, local configuration, recovery journals, project files and provider-held conversations serve different purposes. Removing a controller or revoking access prevents that authorization from being used; it is not a request to erase all local files, server records or conversations.

To request access, correction or deletion, email orlando.rodriguez@empowerhr.net. Identify AI Army or AI Army Dev, your sign-in email address, the relevant computer and the records concerned. We must verify account ownership and authority over the computer before acting. Do not send passwords, private keys, access tokens or confidential conversation contents. Records controlled by the computer owner, Google or an AI provider may require that party's action. An AI Army deletion request does not delete your Google or AI-provider account. Use the same address for privacy questions or request status.

Computer Access And Changes

AI Army is a desktop agent with network and local-runtime access appropriate to the approved installation and granted capabilities. Review the computer, project-folder and controller approvals before enabling remote work. The permission and SDK statements in other products' sections do not automatically apply to AI Army. This notice will be updated when AI Army's data practices change.

AI General Content Reports

This supplements the AI General Privacy Disclosure above for delivered versions that include the Report Content feature. Reporting is optional. Before you submit, the app shows the content excerpt that will be included. A report contains that selected excerpt, your chosen reason, any explanation you add, your account identifier, available source references, and submission and review timestamps. It does not automatically include your entire conversation.

EMPOWER HR, SRL processes these reports to investigate offensive or unsafe content and improve application safety. Authorized operators can review the reports through protected administrative access. The reporting feature does not send reports to an AI service for review. Do not include passwords, access tokens, or unrelated confidential information in your report.

The retention and access, correction, and deletion request process in the AI General disclosure also applies to reports. Include your report receipt identifier when available. Submitting a report does not itself remove the original conversation or copies held by a separately configured computer or AI provider.

AI Captain Dev Privacy Disclosure

Updated November 9, 2026. This disclosure covers AI Captain Dev for Windows, Microsoft package identity EMPOWERHRSRL.AICaptainDev, and Android, package identity ai.captain.dev. Operator and privacy contact: EMPOWER HR, SRL, orlando.rodriguez@empowerhr.net. Other products and editions have separate disclosures.

Account And Device Information

Google sign-in provides a verified account identifier and email address. The service uses these, installation and session identifiers, and authentication credentials to sign you in and enforce access. A Google account alone does not grant access to a Soldier computer. Authorized device assignments, account roles and current duty state determine which operations are available.

The application processes identifiers and names of authorized computers, enrollment and assignment references, application and device status, diagnostics, and the results of requested operations. Diagnostics and results may contain computer, process, project or file-path information. Only use devices and information you are authorized to access.

Requests, Decisions And Results

When you request an operation, the configured service processes its target, operation type, parameters, identifiers, timestamps, status and results. Where General approval is required, the request and relevant information are made available to an authorized General, and the approval or denial and any entered explanation are recorded. Permissions and supported operations depend on the delivered application, backend and enrolled Soldier configuration.

If a supported operation passes work or conversation content to a connected Codex or other AI runtime, that runtime processes it under its own service configuration and privacy terms. Do not submit passwords, private keys or information you are not authorized to share with the selected computer and its configured services.

Storage And Transfers

The Windows client keeps authentication and recovery state behind its native protected-storage boundary. The Android client encrypts its authentication and pending-operation recovery state using Android KeyStore-backed AES-GCM and stores that protected state in the application's no-backup directory. Pending-operation records help reconcile uncertain outcomes. The service retains authentication, device assignment, authorization, request, decision and result records needed to operate access and command delivery. Authorized service operators may access these records for operation, support and security.

Google handles sign-in. The application connects to the configured EMPOWER HR DEV service over HTTPS; that service and the enrolled computer exchange authorized requests and results. Infrastructure and configured AI providers may process network metadata and submitted content under their own practices. This notice does not promise end-to-end encryption, a particular processing country or zero provider logging. The reviewed Flutter dependency list contains no advertising or analytics SDK.

Retention And Data Deletion Requests

No fixed automatic deletion period is promised for all records. Session expiration, signing out, withdrawing a request, revoking access or uninstalling the app does not by itself erase historical service records, local project files or conversations held by a separate computer or AI provider.

To request access, correction or deletion, email orlando.rodriguez@empowerhr.net. Identify AI Captain Dev, your sign-in email, the relevant computer or request when known, and the records concerned. Ownership and authority must be verified before acting. Do not send passwords, access tokens, private keys or confidential conversation contents. Requests concerning another computer or provider may require that operator's action. Deleting app or service records does not delete your Google account. Use the same contact for questions and request status; no fixed completion deadline is promised here.

Permissions And Changes

Network access supports sign-in and authorized remote operations on both platforms. The Windows desktop application capability applies to Windows; the Android edition uses Android network access and its native protected storage. Available features depend on the installed version and its permissions. Review the selected computer, requested action and any approval before dispatch. This disclosure must be updated if the application's data practices change.

AI Soldier Dev Privacy Disclosure

Prepared November 8, 2026. This disclosure covers AI Soldier Dev for Windows, Microsoft package identity EMPOWERHRSRL.AISoldierDev. Operator and privacy contact: EMPOWER HR, SRL, orlando.rodriguez@empowerhr.net. Other products and editions have separate disclosures.

Account And Computer Enrollment

Google sign-in provides an account identifier and email address. The application and configured EMPOWER HR service process these together with computer and installation identifiers, computer name, public-key information, enrollment references, authentication credentials and session information to register the computer and enforce access. Enrollment, General approval, account roles, assignments and current duty state govern which operations are available; a Google sign-in alone does not authorize remote control.

Authorized Operations And Diagnostics

The local Windows application and its service process device status, duty and presence, operation identifiers, target and request details, parameters, timestamps, decisions, progress and results. Authorized General or Captain users and service operators may receive the information needed to manage enrollment and approved operations. Diagnostics may include operating-system, hardware, process, application, project and file-path information. Available commands depend on the delivered version, configuration and permissions.

When a supported, configured operation invokes Codex or another AI runtime, that runtime may process task instructions, files within authorized work areas and resulting content under its own service configuration and privacy terms. Runtime setup and qualification are separate from enrollment. Only approve folders, tasks and information you are authorized to share; do not place passwords or private keys in task instructions. This disclosure does not claim that every development build supports or has qualified every operation.

Local Storage And Transfers

The client and service keep authentication, device binding, enrollment and recovery information locally. Operation journals help reconcile pending or uncertain outcomes. Local application preferences, approved work-folder configuration and separately configured AI-runtime credentials or files may also be stored. The server retains authentication, enrollment, assignment, authorization, request, decision and result records needed for operation, support and security.

Google handles sign-in. The application and device service communicate with the configured EMPOWER HR DEV service over HTTPS. Authorized operators and configured AI providers may process submitted information and network metadata. This notice does not promise end-to-end encryption, a specific processing country, zero provider logging or a fixed deletion period for every record. The reviewed Flutter dependency list contains no advertising or analytics SDK.

Retention And Data Deletion Requests

Signing out, going Off Duty, withdrawing or revoking enrollment, or uninstalling the application does not by itself erase historical server records, local project files, recovery records or information held by a separate AI provider. Command and enrollment recovery may retain records needed to avoid repeating an uncertain operation.

For access, correction or deletion requests, email orlando.rodriguez@empowerhr.net. Identify AI Soldier Dev, your sign-in email, the relevant computer or request when known, and the records concerned. Ownership and authority must be verified before action. Do not email passwords, tokens, private keys or confidential task contents. Separate computer or AI-provider records may require that operator's action. Deleting app or service records does not delete your Google account. Use the same contact for questions and request status; no fixed completion deadline is promised here.

Windows Permissions And Changes

The desktop application and device service support local device setup, protected state and authorized operations. The package includes an automatically started background Windows service that runs as LocalSystem. Its service privileges and startup are separate from opening the desktop interface or choosing a duty state. Some setup or maintenance requires Windows administrator approval; routine task authority remains subject to the configured service and local controls. The app's duty controls, local folder approvals and supported settings have distinct effects. This disclosure must be updated when the application's data practices change.