These Conjoin-Specific Terms ("Conjoin Terms") supplement and form part of the Delalify Terms of Service (the "General Terms"). By using any Conjoin service, you agree to both the General Terms and these Conjoin Terms.

The Delalify Conjoin Platform ("Conjoin" or "Platform") is a cloud infrastructure and developer platform providing APIs, services, and tools for building, deploying, and scaling applications. These terms govern your access to and use of the Conjoin Platform and its services.

Effective Date

These Conjoin-Specific Terms are effective as of November 7th, 2025.

Relationship to General Terms

In the event of any conflict between these Conjoin Terms and the General Terms, these Conjoin Terms shall prevail with respect to your use of the Conjoin Platform. All capitalized terms not defined in these Conjoin Terms have the meanings given to them in the General Terms.

Account Registration

To access Conjoin services, you must create a Conjoin account through the Conjoin Console at console.conjoin.delalify.com. You must provide accurate and complete registration information and keep your account information current.

API Keys and Credentials

Before you can access Conjoin services via the API, you will need to create and manage API keys via the Conjoin Console to authenticate your API requests. You are responsible for:

• Keeping your API keys, credentials, and authentication tokens secure and confidential
• Not sharing, publishing, or exposing your API keys in public repositories, client-side code, or any publicly accessible location
• Immediately notifying us at conjoin@delalify.com if you suspect unauthorized use or exposure of your credentials
• All activity that occurs under your API keys, whether authorized by you or not, until you revoke or rotate them

We reserve the right to revoke or suspend API keys that are exposed, compromised, or used in violation of these terms.

Projects and Organizations

Conjoin organizes resources into projects. You may create multiple projects under your account or organization. Each project has its own API keys, configurations, and resource quotas. You are responsible for managing access controls and permissions within your projects.

Available Plans

Conjoin offers the following subscription plans, each with distinct features and usage limits:

Pricing and Billing

Conjoin services are billed based on usage, with pricing varying by service, resource type, and geographic region. Detailed pricing information for each service and resource is available at conjoin.delalify.com/pricing.

Billing is calculated based on your actual usage, which may include:

• Number of API requests made to Conjoin services
• Data storage volume (measured in GB or TB)
• Data transfer and bandwidth consumption (egress and ingress)
• Compute time and processing resources consumed
• Number of messages sent, emails delivered, or SMS transmitted
• Active user accounts, authentication requests, or API calls
• Other service-specific metrics detailed in the Conjoin documentation

Each plan includes a base allowance of resources. Usage beyond plan limits is billed at the rates specified in the pricing documentation. You are responsible for monitoring your usage and ensuring sufficient billing payment methods are configured to avoid service interruption.

Payment Processing

Conjoin billing is processed through the same payment infrastructure as the Delalify Apps Platform, as described in the General Terms. All payment terms, refund policies, and billing practices outlined in the General Terms apply to Conjoin services.

Plan Changes and Upgrades

You may upgrade or downgrade your plan at any time through the Conjoin Console. Plan changes take effect immediately for upgrades. Downgrades take effect at the end of the current billing period. If your usage exceeds your plan limits, we may automatically upgrade you to a higher tier or apply overage charges as specified in the pricing documentation.

Rate Limits

To ensure fair usage and platform stability, Conjoin enforces rate limits on API requests. Rate limits vary by service, resource, endpoint, and subscription plan. Detailed rate limit specifications for each service are documented in the Conjoin API documentation at conjoin.delalify.com/resources/docs.

Rate limits are typically measured across multiple time windows, including:

• Requests per second (RPS)
• Requests per minute (RPM)
• Requests per hour
• Requests per day

Rate Limit Enforcement

When you exceed applicable rate limits, Conjoin may take the following actions:

• Throttling: Requests may be delayed or queued to comply with rate limits
• Rejection: Requests exceeding limits may be rejected with HTTP 429 (Too Many Requests) status codes
• Temporary Restrictions: Repeated or severe violations may result in temporary suspension of API access for specified durations
• Account Review: Sustained excessive usage may trigger account review to prevent abuse and protect platform resources

Rate limits exist to protect both Delalify's infrastructure and our customers from abuse, denial of service, and resource exhaustion. We strongly recommend implementing exponential backoff and retry logic in your applications to handle rate limit responses gracefully.

Rate Limit Headers

API responses include rate limit headers that indicate your current usage and remaining quota. Monitor these headers to avoid exceeding limits:

• X-RateLimit-Limit: Maximum requests allowed in the current time window
• X-RateLimit-Remaining: Remaining requests in the current time window
• X-RateLimit-Reset: Timestamp when the rate limit resets

Request for Higher Limits

If your application requires higher rate limits than your current plan allows, you may request a limit increase by contacting conjoin@delalify.com with details about your use case, expected traffic patterns, and current plan. We will review your request and may approve increases for legitimate production workloads.

Versioning Strategy

Conjoin APIs are versioned to ensure backward compatibility and allow developers to adopt new features at their own pace. API versions are primarily date-based, with version identifiers following the format YYYY-MM-DD (e.g., 2025-11-07). Some services may use semantic versioning (e.g., v1, v2) for major version releases.

API Changes and Updates

We classify API changes into three categories:

• Backward-Compatible Changes: New features, optional parameters, or additional response fields that do not break existing integrations. These changes may be introduced without version changes.
• Non-Breaking Enhancements: Improvements to performance, reliability, or security that maintain compatibility with existing API contracts.
• Breaking Changes: Modifications that alter existing behavior, remove features, or change response structures in ways that may affect existing integrations. Breaking changes require a new API version.

Deprecation Policy

When we deprecate an API version or feature, we will provide advance notice as follows:

• Deprecation Notice: At least twelve (12) months advance notice for generally available (GA) APIs and six (6) months for beta or preview features
• Documentation Updates: Deprecated features will be clearly marked in the API documentation with migration guidance and recommended alternatives
• Console Notifications: Warnings in the Conjoin Console for projects using deprecated APIs
• Email Notifications: Direct communication to affected customers via registered email addresses

After the deprecation period ends, deprecated API versions may be sunset and cease to function. We strongly recommend monitoring our changelog and documentation to stay informed of deprecation announcements and plan migrations accordingly.

Migration Support

We provide migration guides, code examples, and technical support to help you transition from deprecated API versions to current versions. Enterprise customers receive dedicated migration assistance from their assigned Business Solutions Architect.

Permitted Uses

You may use Conjoin services to build, test, deploy, and operate applications and services that comply with these terms and applicable laws. You are responsible for ensuring that your use of Conjoin does not violate any third-party rights or applicable regulations.

Prohibited Uses

In addition to the prohibited activities outlined in the General Terms, you may not use Conjoin services for the following purposes:

• Cryptocurrency Mining: Using Conjoin compute resources for cryptocurrency mining, blockchain validation, or similar resource-intensive activities not directly related to your application functionality
• Spam and Abuse: Sending unsolicited bulk emails, SMS messages, or other communications through Conjoin Messaging services without proper opt-in consent
• Denial of Service: Engaging in activities designed to overwhelm, disrupt, or degrade Conjoin services or third-party services
• Security Testing Without Permission: Conducting penetration testing, vulnerability scanning, or security research on Conjoin infrastructure without prior written authorization
• Resource Abuse: Creating excessive accounts, projects, or resources for the purpose of circumventing usage limits or rate limits
• Malicious Content: Hosting, distributing, or facilitating the distribution of malware, viruses, ransomware, or other harmful software
• Illegal Content: Storing, processing, or distributing content that violates applicable laws, including but not limited to child exploitation material, illegal weapons, or controlled substances
• Phishing and Fraud: Using Conjoin services to impersonate others, conduct phishing attacks, or engage in fraudulent activities
• Excessive API Calls: Making API requests at volumes or frequencies that significantly exceed normal usage patterns for your plan without legitimate application need

Content Restrictions for AI Services

When using Conjoin AI services, you may not submit content that includes:

• Personal information of individuals without proper consent and data protection measures
• Content designed to generate harmful, illegal, or unethical outputs (e.g., instructions for illegal activities, hate speech, or disinformation)
• Content that infringes intellectual property rights or violates confidentiality obligations

Monitoring and Enforcement

We reserve the right to monitor usage patterns, investigate suspected violations, and take appropriate enforcement actions, including:

• Issuing warnings to account owners
• Throttling or rate-limiting abusive traffic
• Temporarily suspending access to specific services or resources
• Terminating accounts or projects that violate these terms
• Reporting illegal activities to law enforcement authorities

If your account or project is suspended or terminated for violation of this Acceptable Use Policy, you are not entitled to refunds for prepaid services or credits.

Standard Retention Practices

Conjoin follows industry-standard data retention practices designed to balance operational needs, legal requirements, and customer expectations. Retention periods vary by service and data type, as detailed in the service-specific documentation at conjoin.delalify.com/resources/docs.

Customer Control

For most Conjoin services, you have control over how your data is retained. You can configure retention settings, automatic deletion policies, and data lifecycle management rules through:

• Conjoin Console: Configure retention policies and lifecycle rules at conjoin.delalify.com/console
• API Configuration: Programmatically manage data retention through Conjoin APIs
• Email Requests: Contact conjoin@delalify.com for custom retention configurations or bulk deletion requests

Data Deletion Upon Account Termination

When you delete a project or terminate your Conjoin account:

• Immediate Deletion: Resources marked for immediate deletion (e.g., ephemeral data, temporary caches) are removed within 24 hours
• Grace Period: For production data, we provide a grace period of thirty (30) days during which you can request data recovery
• Permanent Deletion: After the grace period, data is permanently deleted and cannot be recovered
• Backup Retention: Encrypted backups for disaster recovery purposes may be retained for up to ninety (90) days before permanent deletion

We are not responsible for data loss resulting from account deletion, project deletion, or failure to maintain adequate backups. You are solely responsible for backing up your data before deletion.

Legal and Compliance Retention

Notwithstanding the above, we may retain certain data as required by law, regulation, or legal obligation, including:

• Financial records and billing information for tax and accounting purposes
• Audit logs and security records for compliance and investigation purposes
• Data subject to legal holds, litigation, or regulatory investigations

Such data is retained securely in accordance with our Privacy Policy and Data Processing Agreement.

The following sections outline additional terms specific to individual Conjoin services. These terms supplement the general Conjoin Terms and apply when you use the respective services.

Conjoin Messaging

Conjoin Messaging provides SMS, email, and other messaging capabilities through APIs. By using Conjoin Messaging, you agree to the following:

SMS and Phone Number Regulations

• Brand Registration: For sending SMS messages in the United States, you must complete brand registration with The Campaign Registry (TCR) or relevant carrier programs as required by U.S. carriers and the CTIA (Cellular Telecommunications Industry Association). We will assist with registration, but you are responsible for providing accurate business information and maintaining compliant messaging practices.
• Campaign Registry: You must register your messaging campaigns with appropriate regulatory bodies and carrier programs in jurisdictions where such registration is required. Campaign registration includes declaring the purpose, frequency, and content type of your messages.
• Consent Requirements: You must obtain prior express written consent from recipients before sending SMS messages, as required by the Telephone Consumer Protection Act (TCPA), CAN-SPAM Act, GDPR, and other applicable regulations. You are solely responsible for obtaining, documenting, and maintaining proof of consent.
• Opt-Out Compliance: You must honor opt-out requests (e.g., STOP, UNSUBSCRIBE) within the timeframes required by applicable law, typically within 24 hours. Conjoin Messaging automatically handles standard opt-out keywords, but you remain responsible for compliance.

Message Delivery

Message delivery rates, timing, and reliability depend on upstream telecommunications providers, carrier networks, and recipient device availability. While Conjoin strives to deliver messages at industry-standard speeds and success rates, we do not guarantee delivery of any specific message.

Factors affecting delivery include but are not limited to:

• Carrier filtering and spam detection systems
• Recipient device status (powered off, out of coverage, full inbox)
• International routing and regulatory restrictions
• Message content that triggers carrier filtering
• Temporary network congestion or outages

You are responsible for implementing appropriate error handling, retry logic, and delivery confirmation mechanisms in your application to account for delivery variability.

Email Deliverability

For email messaging, you must follow email best practices, including proper SPF, DKIM, and DMARC configuration, to maintain sender reputation and deliverability. Conjoin provides tools and documentation to help you configure these authentication mechanisms. You are prohibited from sending spam, unsolicited commercial email, or emails that violate the CAN-SPAM Act or similar regulations.

Prohibited Content

You may not use Conjoin Messaging to send:

• Spam, unsolicited bulk messages, or commercial messages without proper consent
• Phishing attempts or fraudulent messages
• Messages containing malware, viruses, or malicious links
• Illegal content or content promoting illegal activities
• Messages that violate third-party intellectual property rights

Conjoin Auth

Conjoin Auth provides user authentication and identity management services using industry-leading security practices. By using Conjoin Auth, you agree to the following:

Security Standards

Conjoin Auth implements the following security measures:

• Encryption: All authentication data is encrypted in transit using TLS 1.2 or higher and at rest using AES-256 encryption
• Password Security: Passwords are hashed using bcrypt with adaptive cost factors and are never stored or transmitted in plain text
• Multi-Factor Authentication: Support for time-based one-time passwords (TOTP), SMS-based verification, and hardware security keys
• OAuth 2.0 and OpenID Connect: Standards-compliant implementation for secure authorization and authentication flows
• Session Management: Secure session tokens with configurable expiration, automatic rotation, and revocation capabilities
• Brute Force Protection: Automatic rate limiting and account lockout mechanisms to prevent credential stuffing and brute force attacks
• Anomaly Detection: Machine learning-based detection of suspicious login patterns and account takeover attempts

Compliance and Certifications

Conjoin Auth is designed to support compliance with major security and privacy regulations. For detailed information about certifications, audit reports, and compliance documentation, visit delalify.com/company/trust.

Customer Responsibilities

When using Conjoin Auth, you are responsible for:

• Configuring authentication settings appropriate for your security requirements
• Implementing proper authorization logic in your application to control access to resources based on user identity and permissions
• Monitoring authentication logs and responding to security alerts
• Protecting authentication secrets, client IDs, and client secrets
• Complying with applicable data protection regulations when collecting and processing user authentication data

Conjoin Storage

Conjoin Storage provides scalable object storage for files, media, and application data. By using Conjoin Storage, you agree to the following:

Data Storage Locations

• Metadata Storage: Primary metadata, access control lists, and indexing information for Conjoin Storage are stored in data centers located in the United States.
• Object Storage (Business Plan): Customers on the Business plan and higher can configure the geographic region where actual object data (files, media, binary data) is stored. Available regions are documented in the Conjoin Console and may include North America, Europe, Asia-Pacific, and other locations.
• Default Storage (Free and Pro Plans): For Free and Pro plan customers, objects are stored in our primary United States data centers. Regional storage is not available on these plans.

Data Redundancy and Durability

Conjoin Storage is designed for high durability and availability. Objects are automatically replicated across multiple availability zones within the selected region to provide protection against hardware failures and ensure data durability of 99.999999999% (11 nines) for standard storage classes.

Access Control

You are responsible for configuring appropriate access controls for your stored objects. Conjoin Storage supports:

• Private storage with API key authentication
• Public storage with configurable access policies
• Signed URLs for temporary, time-limited access
• Container-level object policies
• Additional access controls with support for Conjoin Auth accounts, organizations, and organization groups.

Misconfigured access controls may result in unauthorized access to your data. We recommend following the principle of least privilege and regularly reviewing access policies.

Content Restrictions

You may not use Conjoin Storage to store or distribute:

• Illegal content or content that violates applicable laws
• Malware, viruses, or malicious software
• Content that infringes intellectual property rights
• Pirated or unauthorized copyrighted materials

Conjoin Billing

Conjoin Billing provides payment processing, subscription management, and billing infrastructure for your applications. By using Conjoin Billing, you agree to the following:

Payment Processing and your Privacy

Depending on your location, Conjoin Billing will use either Stripe or Paystack for payment processing, analytics, and other essential business services. These trusted third-party providers may collect and process personal data, including:

• Transactional information
• Device identifiers
• Data collected through cookies and similar technologies

This information is used to:

• Facilitate secure payment transactions
• Detect and prevent fraud
• Enhance authentication processes
• Conduct analytics to improve service performance

Both Stripe and Paystack are committed to data privacy and security. They use the collected information solely to operate and improve the services they provide to us and to comply with legal obligations.

For more detailed information about their data practices, please refer to:

• Stripe Privacy Policy
• Paystack Terms

We ensure that all data shared with these providers is handled in accordance with these terms and applicable data protection laws and Delalify's General Privacy Policy.

Merchant of Record

When you use Conjoin Billing, you act as the merchant of record for transactions processed through your application. You are responsible for:

• Complying with applicable payment processing regulations and card network rules
• Maintaining PCI DSS compliance if you handle cardholder data directly
• Providing accurate product descriptions, pricing, and refund policies to your customers
• Handling customer disputes, chargebacks, and refund requests
• Remitting applicable taxes and reporting revenue as required by law

Compliance and Risk Management

You must comply with all applicable laws and regulations when using Conjoin Billing, including anti-money laundering (AML) regulations, know-your-customer (KYC) requirements, and sanctions screening. We may request additional information to verify your identity and business legitimacy.

You may not use Conjoin Billing to process payments for:

• Illegal goods or services
• Gambling or gaming services (except where explicitly permitted by applicable law)
• Adult content or services (except where explicitly permitted and properly age-verified)
• Cryptocurrency exchanges or unregulated financial instruments
• Multi-level marketing or pyramid schemes
• Counterfeit or unauthorized goods

Fees and Charges

Conjoin Billing charges transaction fees based on payment volume and plan tier. Detailed fee schedules are available at conjoin.delalify.com/pricing. Payment processor fees (Stripe and Paystack fees) are separate and will be charged in addition to Conjoin Billing fees.

Feature Lifecycle Stages

Conjoin services and features progress through the following lifecycle stages:

Beta and Preview Terms

When using beta or preview features:

• No SLA: Beta and preview features are explicitly excluded from service-level agreements and uptime commitments
• No Warranties: These features are provided "as-is" without warranties of any kind
• Breaking Changes: We may introduce breaking changes, modify functionality, or discontinue features without the standard deprecation notice period
• Limited Support: Support for beta and preview features may be limited to documentation and community forums
• Data Migration: We are not responsible for migrating data or configurations when beta features transition to GA or are discontinued

The Conjoin documentation at conjoin.delalify.com/resources/docs clearly indicates the lifecycle stage of each feature. We recommend using only generally available features for production workloads.

Developer Documentation

Comprehensive documentation for all Conjoin services, including API references, quickstart guides, tutorials, and code examples, is available at conjoin.delalify.com/resources/docs. Documentation is updated regularly to reflect new features, best practices, and API changes.

Support Channels

Support availability varies by plan:

• Free Plan: Access to documentation, community forums, and self-service support resources
• Pro Plan: Email support with response times as outlined in the General Terms
• Business Plan: Priority email support and access to developer success resources
• Enterprise Plan: Dedicated support channels including Slack, phone support, and assigned Business Solutions Architect as detailed in the Enterprise Service Level Agreement

For technical support and general inquiries, contact conjoin@delalify.com.

Status and Incident Communication

Real-time service status, scheduled maintenance notifications, and incident updates are available at status.conjoin.delalify.com. You can subscribe to status updates via email, SMS, or webhook to receive proactive notifications about service disruptions.

Security and Compliance Certifications

Delalify maintains industry-standard security practices and compliance certifications across both the Delalify Apps Platform and the Conjoin Platform. Detailed information about our security controls, compliance certifications, audit reports, and trust practices is available at delalify.com/company/trust.

Data Protection

Your use of Conjoin services is subject to our Privacy Policy and Data Processing Agreement, which detail how we collect, process, and protect personal data in compliance with Ghana DPA, GDPR, and other applicable data protection regulations.

Security Incident Response

In the event of a security incident affecting your data or account, we will notify you in accordance with applicable legal requirements and our incident response procedures. You are responsible for notifying us promptly if you discover a security vulnerability or incident related to Conjoin services.

Shared Responsibility Model

Security is a shared responsibility. Delalify is responsible for the security of the Conjoin infrastructure, while you are responsible for security in the cloud, including:

• Securing your API keys, credentials, and authentication tokens
• Implementing proper access controls and authorization logic in your applications
• Encrypting sensitive data before storing it in Conjoin services
• Monitoring your account for suspicious activity
• Keeping your application dependencies and libraries up to date with security patches

Updates and Changes

We may modify these Conjoin Terms from time to time to reflect changes in our services, legal requirements, or business practices. We will provide notice of material changes as follows:

• Advance Notice: At least thirty (30) calendar days advance notice for material changes that reduce your rights or increase your obligations
• Notification Methods: Email to the address associated with your account, announcements in the Conjoin Console, or updates to the Conjoin documentation

Your continued use of Conjoin services after the effective date of changes constitutes your acceptance of the modified terms. If you do not agree to the changes, you must discontinue use of Conjoin services before the effective date.

For questions, concerns, or clarifications regarding these Conjoin-Specific Terms, please contact: