Party Privacy and Preferences

The Party Privacy and Preferences business feature in Open Cloud MDM enables the storage and management of individuals' or organizations' choices regarding how, when, and under what circumstances they prefer to be contacted. Additionally, it allows for the management of preferences related to contracts, such as the format for receiving account statements (e.g., hardcopy or electronic).

This feature provides services to capture and store privacy and personal preferences across various business objects within the MDM system. It helps organizations respect individuals' preferences and meet institutional or legal requirements related to data privacy and communication.

Business Objects for Preferences:

• Person: Personal preferences related to contact methods, communication frequency, or preferred telephone numbers.
• Organization: Preferences associated with organizational contacts and communication channels.
• Party Address: Preferences regarding specific addresses, such as no early-morning doorbell ringing at a particular address.
• Party Contact Method: Preferences related to contact methods, such as opting out of marketing emails for a specific email address.
• Contract Role Location: Preferences concerning contract-related communication, such as the choice to receive statements by mail for a particular policy or account.

Primary Purposes:

• Satisfying Personal Preferences: Individuals or organizations can specify their preferred modes of communication, contact hours, and communication channels. These preferences ensure that communication aligns with the recipient's choices and enhances the customer experience.
• Compliance with Institutional or Legal Requirements: In some cases, institutions are required by law or regulations to adhere to specific privacy provisions. For example, the Gramm-Leach-Bliley (GLB) Act mandates financial institutions to disclose their privacy policies, offer customers the option to opt out of data sharing within a specific timeframe, and consider non-protest as consent.

Example Use Cases:

1. Marketing Communication Preferences:
• Description: An organization wants to respect its customers' preferences regarding marketing communication.
• Use Case: Customers' preferred contact methods (e.g., email, phone, or postal mail) and frequency of marketing communications (e.g., monthly newsletters) are stored in the system. Customers who opt out of specific communication channels are excluded from related marketing campaigns.
2. Doorbell Ringing Preferences:
• Description: A residential property management company wants to respect the privacy and preferences of tenants.
• Use Case: Tenants' preferences regarding doorbell ringing times are stored for their respective addresses. For example, a tenant might prefer no doorbell ringing before noon. Property management staff adhere to these preferences during visits.
3. Email Marketing Opt-Out:
• Description: An e-commerce company must comply with email marketing regulations.
• Use Case: Customers can indicate their preference to opt out of marketing emails for specific email addresses. The company ensures that marketing emails are not sent to these addresses to remain compliant with privacy laws.
4. Financial Statement Delivery Preferences:
• Description: A financial institution needs to cater to customers' preferences for receiving account statements.
• Use Case: Customers specify their preferred statement delivery method (e.g., hardcopy or electronic) for specific policies or accounts. The institution ensures that statements are delivered according to these preferences to maintain compliance with privacy and regulatory requirements.
5. GLB Privacy Compliance:
• Description: A financial institution must comply with the Gramm-Leach-Bliley Act's privacy provisions.
• Use Case: The institution provides customers with the option to opt out of certain data-sharing practices within the specified timeframe. Those who do not opt out are considered to have consented to data sharing, in adherence to GLB requirements.
6. Preferred Telephone Numbers for Solicitation:
• Description: A telecommunications company wants to optimize its customer engagement strategies.
• Use Case: Customers can specify their preferred telephone numbers for solicitation or promotional offers. The company targets marketing calls to these preferred numbers to enhance campaign effectiveness.
7. Privacy Policy Consent Management:
• Description: An online service provider must manage user consent to its privacy policy.
• Use Case: Users can indicate their consent to the privacy policy within the application. Non-protest is considered as consent, aligning with privacy compliance requirements.

The Party Privacy and Preferences feature is essential for organizations to respect individuals' choices, adhere to privacy regulations, and enhance customer satisfaction by aligning communication with recipients' preferences. It offers flexibility in managing preferences across different business objects and use cases.