Privacy

Privacy Policy

The personal data processed by Messages by OzarksMade, the purposes of that processing, and the rights available to you.

Last updated: September 20, 2026

This Privacy Policy describes the personal data collected by OzarksMade ("OzarksMade", "we", "us" or "our") in connection with the Messages by OzarksMade application (the "Application") and the OzarksMade RCS network and related services (together, the "Services"), the purposes for which that data is processed, the recipients to whom it is disclosed, the periods for which it is retained, and the rights available to you. Terms defined in the Terms of Service have the same meaning in this Policy.

1. Data controller and contact

OzarksMade is the controller of the personal data described in this Policy. Enquiries, and requests made under section 15, may be addressed to messages@ozarksmade.net.

2. Categories of personal data

OzarksMade collects the following categories of personal data:

  1. Registration data. Your phone number; the identifier, model, operating system version and Application version of each device registered to that number; the credentials issued to those devices; and the date of registration and of each subsequent connection.
  2. Message content. The text, and any photograph, video, audio recording, file, contact record, location or calendar item, comprised in a message transmitted or received by means of the OzarksMade RCS network, and, where Sync is enabled, in a message transmitted or received by SMS or MMS.
  3. Message metadata. The sender and recipient of a message, the time at which it was submitted and delivered, its delivery and read status, and the conversation to which it belongs.
  4. Conversation state. Where Sync is enabled, the read status of messages, pinned, muted and starred conversations, conversation categories, scheduled messages, the contents of Trash, the list of blocked numbers and phrases, and Application settings.
  5. Connection data. The network address from which a device connects, the type of connection, and the time of the most recent connection.
  6. Conversation indications. Whether a message has been delivered to and read by you; whether you are presently composing a message; and, as Presence, whether you are presently using the Application and whether you have a particular conversation open.
  7. Diagnostic data. Where you elect to submit a diagnostic log under section 9, the contents of that log, being a record of the operation of the Application, together with your device model, operating system version and Application version.
  8. Statistical data. The pseudonymous device identifier, Application version, release channel, device model and operating system version described in section 10.
  9. Correspondence. The content of any communication you address to OzarksMade support, and the electronic mail address from which it is sent.

OzarksMade does not collect your location, does not collect your contact list, and does not collect any advertising identifier.

3. Messages transmitted by SMS and MMS

SMS and MMS messages are transmitted and received by your mobile network operator. OzarksMade is not a party to their transmission, does not receive them in the course of their transmission, and does not store them, save as provided in section 4. Such messages are stored on your device by the Android operating system.

4. Messages transmitted over the OzarksMade RCS network

  1. Transmission. A message transmitted by means of Chat Features passes through systems operated by OzarksMade in order to be delivered. Where the recipient's device is not connected at the time of submission, the message is retained by OzarksMade until that device connects and the message is delivered, or until the applicable retention period expires.
  2. Media. A photograph, video, audio recording or file transmitted by means of Chat Features is stored by OzarksMade for a limited period in order that the recipient may retrieve it.
  3. Storage where Sync is enabled. Where you enable Sync with OzarksMade Cloud, message content, message metadata and conversation state are stored by OzarksMade in order that they may be made available to each device registered to your phone number. Sync applies to messages transmitted by SMS and MMS as well as to those transmitted by Chat Features; a copy of such messages is accordingly stored by OzarksMade while Sync is enabled.
  4. Storage where Sync is disabled. Sync is disabled until you enable it. While it is disabled, OzarksMade retains message content only for the period described in section 4.1 and section 4.2.
  5. Individual categories. Each category of conversation state listed in section 2.4 may be excluded from Sync individually within the Application while Sync remains enabled for the remainder.
  6. Deletion. Disabling Sync prevents further storage. To require erasure of data already stored, proceed as described in section 15.

5. End-to-end encryption

Chat Features implement the end-to-end encryption mechanism specified by the GSM Association in PRD RCC.16, which is based upon the Messaging Layer Security protocol (IETF RFC 9420). Encryption is applied automatically and is not subject to a setting within the Application. That is a requirement of GSMA PRD RCC.71, which provides that the provider of a client shall not enable or disable end-to-end encryption on behalf of a user.

A conversation is encrypted end to end where every participant is registered on the OzarksMade RCS network and every participant's client is capable of the mechanism, and where the necessary key material is available for each participant. Where those conditions are not satisfied, the conversation proceeds without end-to-end encryption. The Application indicates the status of a conversation.

Where a conversation is encrypted end to end, the content of its messages is encrypted upon your device and may be decrypted only by the devices participating in the conversation. OzarksMade transmits and, where Sync is enabled, stores that content in encrypted form and is not able to read it.

End-to-end encryption does not apply to messages transmitted by SMS or MMS, which are carrier services and are not encrypted by OzarksMade. It does not conceal message metadata, which OzarksMade requires in order to route and deliver a message.

6. Verification of your phone number

Registration on the OzarksMade RCS network requires verification that the phone number presented by your device is held by you. Verification is effected by the exchange of a short message between your device and a number operated by or on behalf of OzarksMade, together with a verification code valid for a single session.

  1. Disclosure to a processor. The transmission of that message is performed by Microsoft Azure Communication Services acting as a processor on behalf of OzarksMade. That provider receives your phone number and the content of the verification message for the purpose of transmitting it, and processes them under a data processing agreement. No other personal data is disclosed to that provider.
  2. Handling on your device. Where a verification message is received by your device, the Application identifies that message, extracts the verification code and discards the message without storing or displaying it. The Application does so only while a verification initiated by you is in progress and only in respect of a message matching the form used by OzarksMade.
  3. Carrier charges. A verification message transmitted by your device may be charged by your mobile network operator at its standard rates.
  4. Access. A verification code is not accessible to OzarksMade support personnel.

7. Continuity

Where you enable Continuity, the association between your primary device and each secondary device, and the phone numbers shared with each, are stored by OzarksMade in order to route messages to the correct devices. Continuity is disabled until you enable it.

8. Conversation indications and Presence

These indications are enabled by default. Delivery notifications, read notifications, composing indications and Presence are transmitted to the persons with whom you exchange messages by means of Chat Features, without further action on your part. They are a function of the Rich Communication Services standard and of the conversation experience the Application provides.

  1. Delivery and read notifications. Where a message addressed to you is delivered to your device, and where you open the conversation in which it appears, a notification to that effect is transmitted to the sender.
  2. Composing indications. While you are composing a message, an indication to that effect is transmitted to the other participants in the conversation. The indication expires automatically if you cease composing.
  3. Presence. Whether you are presently using the Application, and whether you have a particular conversation open, is published to the other participant in that conversation. An enquiry is answered only in respect of the person making it; the service does not disclose to any person which other conversation you may have open, or with whom.
  4. Disabling. Each of the foregoing may be disabled within the settings of the Application, and Presence may in addition be disabled for an individual conversation. Where disabled, the indication is not transmitted from your device.
  5. Reciprocity. Where a person with whom you exchange messages has disabled an indication, that indication is not transmitted to you.
  6. Scope. These indications apply to messages transmitted by means of Chat Features. They do not apply to messages transmitted by SMS, and apply to messages transmitted by MMS only to the extent supported by your mobile network operator.

9. Diagnostic logs

The Application provides an option, within its settings, to submit a diagnostic log to OzarksMade. Submission occurs only upon your express instruction and is never automatic. A diagnostic log records the operation of the Application, including the screens opened, the outcome of network operations and the text of errors. It does not contain the content of your messages and does not contain your contact list. Your device model, operating system version and Application version are transmitted with it.

10. Statistical data

The Application periodically transmits to OzarksMade a report comprising a pseudonymous device identifier, the Application version and release channel, the device model and the operating system version, for the purpose of determining the number of devices in active use and of reproducing faults that arise only upon particular hardware.

The identifier is derived from the Android ANDROID_ID value by a one-way hash computed upon your device, such that OzarksMade receives an irreversible value. It is unique to the Application upon that device, persists across reinstallation and the clearing of Application data, and changes upon a factory reset. It is not your phone number, a Google account identifier, an advertising identifier, an IMEI or any hardware serial number. The report does not include message content, message metadata, contacts, your phone number or your location. These statistics are collected by OzarksMade for its own purposes and are not disclosed to any third party.

11. Data accessed upon your device

The Application requests the following permissions, and uses the data to which they grant access for the following purposes only:

  1. SMS and MMS. To compose, transmit, receive and display text and multimedia messages.
  2. Contacts. To display the name and photograph associated with a phone number and to enable the selection of recipients. Contact records are read upon your device and are not transmitted to OzarksMade.
  3. Phone number and telephony state. To determine the subscriber identity and number associated with each subscriber identity module and to direct messages accordingly.
  4. Notifications. To inform you of received messages.
  5. Camera, microphone, storage and location. Where you elect to attach a photograph, video, audio recording, file or location to a message. Such data is processed only upon your instruction and only as message content.
  6. Calendar. Where a contact record includes a date of birth or anniversary, the Application reads that date upon your device in order to display a reminder. Those dates are not transmitted to OzarksMade and the feature may be disabled within the Application.
  7. Biometric authentication. Where you lock a conversation, the Application requests authentication by means of the facilities of the operating system. OzarksMade does not receive biometric data, which is retained by the operating system and is not accessible to the Application.

12. Purposes of processing

OzarksMade processes personal data for the following purposes: to transmit, deliver and display messages; to register devices and to verify the phone numbers associated with them; to synchronize message history and conversation state between the devices registered to a number, where Sync is enabled; to operate Continuity and Presence, where enabled; to maintain the security and integrity of the Services and to prevent abuse; to provide support and to diagnose faults; to determine the number of devices in active use; to administer subscriptions; and to comply with legal obligations.

13. Disclosure of personal data

OzarksMade does not sell personal data, does not disclose personal data for advertising purposes, and does not permit any third party to use personal data for its own purposes. Personal data is disclosed only as follows:

  1. Recipients of your messages. The content and metadata of a message are disclosed to the recipient you have selected and to the devices registered to that recipient.
  2. Processors. To providers engaged to perform services on behalf of OzarksMade, upon written terms restricting them to processing upon instruction. These comprise the message transmission provider identified in section 6.1 and the hosting and infrastructure providers upon which the Services operate.
  3. Businesses you contact. Where you exchange messages with a business by means of the network, the content of that exchange is disclosed to that business, which is responsible for its own handling of it.
  4. Google. Purchases and subscriptions are transacted by Google Play. OzarksMade receives confirmation of entitlement and does not receive your payment instrument details.
  5. Legal. Where required by law, by an order of a competent authority, or where necessary to establish, exercise or defend a legal claim, or to protect the rights, property or safety of OzarksMade, its users or the public.
  6. Corporate transactions. In connection with a merger, acquisition, reorganization or sale of assets, subject to the recipient being bound by terms no less protective than this Policy.

14. Retention

  1. A message awaiting delivery is retained until it is delivered or until the applicable delivery period expires, whichever occurs first, and is then deleted.
  2. Media transmitted by means of Chat Features is retained for a limited period sufficient for retrieval by the recipient, and for as long as Sync remains enabled in respect of the conversation.
  3. Where Sync is enabled, message content, message metadata and conversation state are retained until you delete them, until Sync is disabled and erasure is requested, or until the account is closed.
  4. Registration and connection data is retained for the period during which the number remains registered, and thereafter for such period as is necessary for security and abuse prevention.
  5. A diagnostic log is retained for no longer than is necessary to diagnose the fault to which it relates.
  6. Records of administrative actions taken by support personnel are retained for one year, as described in section 16.
  7. Records required to be retained by law are retained for the period the law requires.

15. Your rights

Subject to applicable law, you have the right to request access to the personal data OzarksMade holds concerning you, the correction of inaccurate data, the erasure of data, the restriction of processing, the portability of data you have provided, and to object to processing. You also have the right to lodge a complaint with a supervisory authority in your jurisdiction.

A request may be made by electronic mail to messages@ozarksmade.net, stating the phone number to which the request relates. Neither an account nor an installation of the Application is required, and a request may accordingly be made after the Application has been removed from your device. OzarksMade will take reasonable steps to verify that the request is made by the person entitled to make it, and will respond within the period required by applicable law. Data held upon your own devices is not affected by a request and remains under your control.

Where processing is founded upon your consent, you may withdraw that consent at any time by disabling the corresponding feature within the Application. Withdrawal does not affect the lawfulness of processing carried out before it.

16. Access by support personnel

OzarksMade support personnel may access an account in order to diagnose and resolve a reported fault. The internal support facility discloses the following:

  1. The phone number and the date upon which the account was created.
  2. The devices registered to the account, their model, Application version, enabled status and the time at which each was last connected.
  3. Whether a device is presently connected, the type of connection and the network address from which it connects.
  4. Where Sync is enabled, the number of messages and conversations stored, the number unread, the dates spanned by the stored history, the storage consumed, and the synchronization state of each device.
  5. The number of messages awaiting delivery to a device and the period for which they have been awaiting delivery.
  6. Whether a verification is in progress and the number of attempts made.

The facility does not disclose the content of any message, whether stored or awaiting delivery; any photograph, video, file or audio recording; the parties to any particular message; any verification code; or any credential belonging to the account.

Support personnel may sign a device out, disconnect a device, disable a device without removing its registration, cause a device to synchronize from the beginning, reset the credential used by devices to connect, and erase stored history upon request. Each such action is recorded, identifying the person who performed it, the account affected, the time and the change made. Those records are retained for one year.

Where Sync is disabled, the data disclosed by the facility is limited to the registered devices and their connection state.

17. Transfer to a new device and operating system backup

Where you transfer data to a new device using Samsung Smart Switch or the device-to-device transfer facility of the Android operating system, Application data, comprising conversations, settings, pinned and starred items and the contents of Trash, is transferred directly between your devices and does not pass through OzarksMade.

The Application is excluded from the cloud backup facility of the Android operating system. Application data is accordingly not copied to Google Drive or to any Google account.

18. Companion Mode

Companion Mode, by which the Application formerly displayed conversations obtained from the Google Messages application installed upon the same device, has been discontinued. While that feature operated, authentication was performed by Google upon its own sign-in page; OzarksMade did not receive or store any Google account credential, and the pairing keys created were stored solely upon your device. Those keys are not transmitted to OzarksMade and are removed when the feature is disabled or the Application is uninstalled.

19. Business messaging and third-party clients

A business may register an identity upon the OzarksMade RCS network in order to exchange messages with users. Where you exchange messages with such a business, the exchange is carried by the network as described in section 4, and the business is responsible for informing you of its own handling of information you provide to it. Where OzarksMade bills such a business, it counts the number of distinct phone numbers with which that business has exchanged messages in a billing period. That count is not disclosed to any other party.

20. Security

Messages stored upon your device are protected by the security facilities of the device, including its screen lock and storage encryption. Data transmitted between your device and OzarksMade is encrypted in transit; signalling is carried over Transport Layer Security and the Services do not offer an unencrypted alternative. Data stored by OzarksMade is encrypted at rest. Access to production systems is restricted to authorized personnel, is subject to the limitations described in section 16, and is recorded. No method of transmission or storage is entirely secure, and OzarksMade does not warrant absolute security.

21. International transfer

OzarksMade operates in the United States of America, and personal data is processed there. Where you access the Services from another jurisdiction, your personal data is transferred to the United States. Where such a transfer is subject to a legal mechanism in your jurisdiction, OzarksMade relies upon the appropriate safeguards or derogations available under the applicable law.

22. Children

The Application is not directed to children under the age of 13, and OzarksMade does not knowingly collect personal data from them. Where OzarksMade becomes aware that such data has been collected, it will be erased. A parent or guardian who believes that a child has provided personal data may contact messages@ozarksmade.net.

23. Amendment of this Policy

OzarksMade may amend this Policy from time to time. The amended Policy will be published upon this page and the date at the head of the document will be revised. Where an amendment materially affects the processing of your personal data, OzarksMade will give notice before it takes effect, by means of the Application or of this website.

24. Contact

Enquiries concerning this Policy may be addressed to messages@ozarksmade.net, or submitted by means of the "Contact us" option within the settings of the Application.