Terms specific to the Apps Platform

Delalify issues these Apps Platform-Specific Terms ("Apps Platform Terms") as a supplement to the Delalify Terms of Service (the "General Terms"), so the parties treat these Apps Platform Terms as part of the General Terms. When you use any product on the Apps Platform, you agree to both the General Terms and these Apps Platform Terms.

The Delalify Apps Platform ("Apps Platform" or "Platform") is a suite of end-user Software-as-a-Service (SaaS) products that operate together as one connected workspace. The Apps Platform includes People, Channels, OneCloud, Teams, Tables, Builder, Wallet, and Beryl. Under these Apps Platform Terms, the parties set the rules for your workspace, your members, the content that you create or publish, and the entitlements that your plan includes.

Effective Date

These Apps Platform Terms are effective as of October 13, 2026.

Relationship to General Terms

Where these Apps Platform Terms and the General Terms are inconsistent, the parties will apply these Apps Platform Terms to your use of the Apps Platform. Each capitalized term that we use without a definition in these Apps Platform Terms has the meaning that we assign to it in the General Terms.

Some Apps Platform features are also subject to separate documents, including the Delalify AI Terms, the Data Processing Agreement, the HIPAA Business Associate Agreement, and the Enterprise Service Level Agreement. The parties will apply each of those documents within its own stated scope and will keep every one of them in force alongside these Apps Platform Terms.

What These Terms Do Not Cover

The parties apply these Apps Platform Terms only to the Apps Platform, which means that the Delalify Conjoin Platform is outside their scope. When you use Conjoin services directly through the Conjoin Console or the Conjoin APIs, your use is subject to the separate Conjoin Platform-Specific Terms. Apps Platform products use Conjoin infrastructure internally; however, for that internal use, your relationship remains with Delalify under the General Terms and these Apps Platform Terms.

Account and Workspace Creation

To use the Apps Platform, you must create a Delalify account and one or more workspaces. A workspace is the container that stores your data across People, Channels, OneCloud, Tables, Builder, Wallet, and Beryl. When you register, you must provide accurate information and keep it current. Each workspace has an owner who accepts these Apps Platform Terms on behalf of the workspace and who is responsible for billing, compliance, and member management.

Workspace Ownership and Billing Owner

The workspace owner is the person or organization that holds the legal obligations under these Apps Platform Terms for that workspace, while the billing owner is the person or organization that is responsible for paying the charges for that workspace. The same person or organization can hold both roles, although two different parties can hold them too. Members can transfer ownership to one another through the workspace settings; however, each transfer is subject to the incoming owner's acceptance and to any residual billing obligations.

Members, Roles, and Permission Cascade

You can invite members to your workspace by email. You assign each member a role through Teams, which then applies that member's permissions across every Apps Platform product that the member can access, including People, Channels, OneCloud, Tables, Builder, Wallet, and Beryl. If you remove a member from Teams or change the member's role, Teams applies that change across every product. You are responsible for assigning roles that match each member's legitimate need to access data.

Your responsibilities for your members also include each of the following.

• You must invite members accurately and remove each member promptly when they leave your organization.
• You must assign each member the least privilege that they need for their work, including for access to contacts, files, billing records, and Builder projects.
• You must review role definitions and audit logs periodically.
• You are responsible for all activity that your members perform under your workspace.

Sign-in Security

You and your members must keep sign-in credentials, session tokens, and recovery codes confidential. Notify us at support@delalify.com as soon as you suspect unauthorized access. We may suspend sessions or require a credential rotation whenever anyone suspects or reports a compromise.

Directory Sync and Single Sign-On

Teams supports SAML 2.0 and OpenID Connect for single sign-on, along with SCIM 2.0 directory sync, for identity providers that include Microsoft Entra ID, Google Workspace, and Okta. Delalify provides the integration endpoints and the protocol support, while you are responsible for configuring your identity provider, including the metadata exchange, certificate management, attribute mapping, and group provisioning rules. The timing of deprovisioning depends on how your identity provider sends change events, so verify the behavior that you expect in a test environment before you rely on it for compliance.

Multiple Workspaces and Organizations

You may create multiple workspaces under your account, each with its own data, members, billing, plan, and configuration. However, you may not create many workspaces to circumvent plan entitlements or fair-use rules, and if you do, we may review your account.

Available Plans

Delalify offers the Apps Platform plan tiers below, each with its own entitlements and support level.

Entitlements Across Products

Your plan tier determines the entitlements that you receive in each product on the Apps Platform. We publish the authoritative list of current entitlements on the pricing page. Entitlements include, but are not limited to, the items below.

• People: The People entitlements include the number of contacts per workspace, the volume of form submissions, and the retention of interaction history.
• Channels: The Channels entitlements include monthly send volumes and the maximum number of contacts per send for email, while we bill SMS against SMS credits that you purchase separately.
• OneCloud: The OneCloud entitlements include total storage, the maximum file size, the depth of version history, and the number of shared drives.
• Tables: The Tables entitlements include the number of databases, row counts, AI-computed column executions, and real-time collaboration seats.
• Builder: The Builder entitlements include the number of published sites, published apps, workflow executions, custom domains, and active environments.
• Wallet: Wallet charges usage-based fees on transactions, invoices, checkout pages, and marketplace payouts, as we describe in the Wallet section of these Apps Platform Terms.
• Beryl: The Beryl entitlements include monthly budget caps on AI tokens or requests for each workspace and each agent, with overage routing that you control through Beryl Guard.
• Teams: The Teams entitlements include the number of workspace seats, the available roles, and the availability of directory sync and single sign-on.

When your usage exceeds your plan allowance, we handle the excess in one of the following ways, depending on the product and the entitlement: soft throttling until the next cycle, automatic overage billing at the rates that we publish on the pricing page, or a prompt to upgrade your plan. You are responsible for monitoring your usage and for keeping a valid payment method on file, so that your service continues without interruption.

Fair Use

Delalify applies shared-infrastructure limits to some Apps Platform features without stating them as hard entitlements, because normal use stays well below those limits. Those limits apply to concurrent workflow executions, real-time collaboration cursors on a single Table, parallel Beryl agent sessions, and Forms submissions per second. We treat sustained usage far above normal patterns, spikes from automation loops, and activity that degrades service for other customers as matters of fair use, so we may throttle, queue, or reject the excess. When we do, we will tell you and work with you on an upgrade path.

Enforcement

When your usage exceeds your entitlements or the fair-use thresholds, we may take one or more of the actions below.

• Throttling: We may delay or queue requests, sends, workflow executions, or AI calls so that your workspace stays within its allowance.
• Soft caps: We may pause further operations of the same kind until the next billing cycle or until you upgrade your plan.
• Overage billing: Where we publish overage pricing, we will include the overage amount on your next invoice.
• Temporary restrictions: If the excess continues, we may temporarily restrict the product where it occurs, giving you advance notice where circumstances permit.
• Account review: If violations repeat or a pattern of activity is consistent with abuse, we may review the account and, where we consider it warranted, suspend or terminate the workspace.

Plan Changes

You may upgrade or downgrade your plan at any time through your workspace settings. An upgrade takes effect immediately, while a downgrade takes effect at the end of the current billing period. Once a downgrade is in force, any data or features that require the higher plan may become unavailable. If you are on an Enterprise Plan under a separate order form, the parties will make any plan change under that order form alone, and the self-service terms in this section do not apply to that change.

Feature Lifecycle Stages

Delalify releases each Apps Platform feature through the lifecycle stages below.

Preview and Beta Terms

The following terms apply whenever you use a Preview or Beta feature.

• No SLA: We exclude Preview and Beta features from every service-level commitment.
• No warranties: We provide these features as-is, without warranties of any kind.
• Breaking changes: We may change the behavior of these features, modify their functionality, or discontinue them without giving the standard deprecation notice that we describe below.
• Limited support: We support these features only through documentation and community channels.
• Data migration: We are not responsible for migrating data or configurations when we make a Preview or Beta feature Generally Available or when we discontinue it.

Deprecation Policy

When we deprecate a Generally Available feature, we will give advance notice in the ways below.

• Deprecation notice: We will give at least twelve (12) months' advance notice for Generally Available features and six (6) months' notice for Beta or Preview features.
• In-product notices: We will show warnings inside the parts of each product that use the deprecated feature, with migration guidance where a replacement exists.
• Email notices: We will email workspace owners and billing owners at the email addresses on file.
• Documentation: We will mark deprecated features in the product documentation with a stated sunset date and recommended alternatives.

Deprecated features may stop working after the deprecation period ends, so you are responsible for monitoring deprecation notices and for planning your migrations to match.

Feature Removal for Legal or Safety Reasons

We may remove or restrict a feature before the standard notice period ends if keeping it available creates a legal, security, or safety risk, or if a third-party dependency that we rely on stops being available. In either case, we will tell you as soon as we can and, where reasonable, offer you an alternative.

The Acceptable Use section of the General Terms applies to all of your activity on the Apps Platform. We add the rules below because people can use or misuse each product in its own ways.

Prohibited Uses

Delalify prohibits each of the uses below, whether you use the Apps Platform in whole or in part.

• Unsolicited messages: You must have the consent that the law of each jurisdiction requires, including under TCPA, CAN-SPAM, GDPR, the Ghana DPA, and equivalent regimes, before you use Channels to send SMS or email.
• Data collection without authority: You may use Forms, People, or Tables to collect or store personal data only where you have the lawful basis or the consent to process it.
• Malicious content: You may not use Builder Sites or Builder Apps to host or distribute malware, phishing pages, credential harvesters, or content that infringes the rights of a third party.
• Illegal commerce: You may not use Wallet to accept payments in any category that we prohibit in the Wallet section of these Apps Platform Terms.
• Overload and evasion: You may not use workflows, agents, or scripted interactions to overwhelm the Platform, a third-party service, or any end user, or to circumvent entitlements, rate limits, or fair use.
• Unsafe AI use: You may not direct Beryl, whether through its chat interfaces, agents, or workflows, to produce content or take actions in breach of a restriction in the Delalify AI Terms or the AI Provider Policies.
• Competing products: You may not use Apps Platform features or data to build, train, or host a product whose primary function competes with any Apps Platform product.
• Scraping and resale: You may not scrape the Platform, its documentation, or any customer-facing part of the Platform, or resell access to the Platform without written authorization from Delalify.
• Cryptocurrency mining: You may not use Apps Platform compute, including Builder Workflows or Beryl Agents, to mine cryptocurrency or to perform blockchain validation that is unrelated to the core function of your application.
• Access-control bypass: You may not try to access any workspace, data, or resource that you are not entitled to, including through reverse engineering, probing, or unauthorized penetration testing.

Regulated Data

Your obligations for health data depend on the Delalify entity that you contract with and on where your end users are based. Because HIPAA is a United States federal law, you need a signed HIPAA Business Associate Agreement only when you contract with Delalify LLC and qualify as a Covered Entity or Business Associate under 45 CFR Parts 160 and 164. The parties must have that BAA in place before you store or transmit protected health information through the Apps Platform.

HIPAA applies only in the United States, so customers elsewhere process health data under their own laws. Customers of Delalify LTD in Ghana process health data as special personal data under the Ghana Data Protection Act, while customers subject to GDPR process it as a special category of personal data under Article 9. Customers in the United Kingdom and other regions follow their local health privacy laws. In each case, the parties set out the processor relationship in the Data Processing Agreement, while you are responsible for consent, retention, and access control under the law that applies to you.

The DPA also applies whenever you process personal data through the Apps Platform that is subject to GDPR, the Ghana DPA, or another data protection law, whether or not that data includes health information. You are responsible for identifying the frameworks that apply to you and for configuring the Platform to meet your obligations to your end users.

Monitoring and Enforcement

We may monitor usage patterns, investigate suspected violations, and take the actions that we list in the Enforcement section above. Where a violation involves a security, legal, or safety risk, we may act without advance notice. If we suspend or terminate your workspace for a violation of this Acceptable Use section, you are not entitled to a refund of prepaid fees or credits.

Your Data, Your Responsibility

You own the data that you bring into the Apps Platform, including contacts in People, conversations in Channels, files in OneCloud, rows and schemas in Tables, projects in Builder, customer and payment records in Wallet, and the AI prompts and outputs that you store through Beryl. You are responsible for the lawfulness of that data, for your right to process it, and for honoring any commitments that you give to the people to whom that data relates.

Our Role as a Processor

Delalify processes your data on your behalf to operate the Apps Platform, in line with our Privacy Policy and the Data Processing Agreement. We list our subprocessors on the Subprocessors page and update that list whenever our supply chain changes.

Export and Portability

Every Apps Platform product lets you export your data through that product's own export tools. You can export contacts from People, conversation history from Channels, files from OneCloud, rows and schemas from Tables, project bundles from Builder, invoices and payout records from Wallet, and audit trails from Teams and Beryl. We document the export formats and frequency limits in the product documentation. You are responsible for keeping your own backups of any data that you cannot afford to lose.

Accuracy and Integrity

You are responsible for the accuracy of the data that you enter. Delalify validates customer content only through technical checks for file integrity, schema constraints, and format validation, and through the content restrictions that we describe in these Apps Platform Terms. If your data contains errors that affect downstream behavior, you are responsible for correcting that data, for example when a bad email address causes a bounce or an incorrect tax category affects a Wallet invoice.

In the sections below, we add terms for each product to the general rules above. The terms for a product apply only when you use that product.

People

People is the contact and relationship product on the Apps Platform, which you can use to store contact profiles, custom fields, interaction history, notes, and linked files. People also provides Forms, which collect data from the public internet into your workspace.

Scope of People

• Contacts: Contacts are individual records with custom fields, timeline events, and linked activity across Channels, OneCloud, and Wallet.
• Groups: Groups are static and dynamic groupings of contacts that you can use to drive sends, permissions, and automations.
• Tags: Tags are labels that you can use to filter contacts, and they can trigger workflows through sticky tag rules.
• Forms: Forms are public-facing data collection tools that create or update contacts from the answers that people submit.

Customer Responsibilities

• You must have a lawful basis for every contact that you store, whether that basis is consent, contractual necessity, legitimate interest, or any other basis that is valid under applicable law.
• Where consent is your basis, you must capture and retain proof of consent, including for the Forms that you collect through embedded widgets or links.
• You must process data subject rights requests within the timeframes that apply in your jurisdiction, using the export and deletion workflows that People provides.
• You must keep your contact imports clean, so you may import data from Google Contacts, Outlook, or other CRMs only if you are entitled to re-process that data.
• You may use People only for people with whom you have a relationship, so you may not use it to store cold outreach lists that you buy from third parties.

Data Subject Workflows

People includes data export and deletion workflows that cascade across People, Channels, and OneCloud. When you start the deletion workflow, it removes the contact and the related records from every product that supports the cascade. Where the law requires us to retain records such as financial records, tax records, and audit logs, we may keep those records longer, as we describe in the Data Retention section below.

Protected Health Information

The Regulated Data rules above apply to your handling of protected health information (PHI) in People. US customers of Delalify LLC with a signed HIPAA Business Associate Agreement may store PHI in contact profiles, notes, attached files, Form submissions, and the other parts of People within the scope of the BAA. You must sign the BAA before you enter any PHI into People. Customers outside the United States handle health data under the Ghana Data Protection Act, GDPR, or their local health privacy law, together with the Data Processing Agreement. In those cases, People applies the same storage, export, and deletion controls to that health data.

Channels

Channels is the email and SMS product on the Apps Platform. Channels personalizes each message with data from People and records each reply in the contact's timeline automatically. Channels also provides Multisend, which delivers the same content over SMS and email according to each recipient's channel preferences.

Consent and Compliance

• Consent: You must obtain the consent that the law of each jurisdiction requires, including under TCPA, CAN-SPAM, GDPR, the Ghana DPA, and equivalent regimes, before you send SMS or email. You are also responsible for keeping a record of that consent.
• Opt-out: Channels processes the standard opt-out keywords STOP and UNSUBSCRIBE, and their localized equivalents, automatically. When a recipient opts out, Channels suppresses future sends to that recipient and tags the recipient's profile in People. You must also honor the opt-out requests that recipients send you through any other channel.
• Brand and campaign registration: If you send SMS in the United States or in another jurisdiction that requires brand or campaign registration, you must complete registration with the relevant program, including The Campaign Registry for U.S. long-code SMS, and you must maintain compliant messaging practices. Delalify helps with registration, but you are responsible for the accuracy of the information that you submit.
• Email authentication: You must configure SPF, DKIM, and DMARC records for each sending domain as we document in Channels. You are responsible for correcting any missing or misconfigured authentication, which harms deliverability.

Delivery and Sender Reputation

Delivery rates, timing, and reliability depend on upstream carriers, email providers, recipient devices, and the sender reputation that your activity generates. Channels monitors bounce rates, complaint rates, and engagement signals and alerts you when any of them crosses a threshold. If poor sending practice continues, such as high bounce rates, high complaint rates, blacklisting, or spam-trap hits, we may throttle or suspend your send privileges to protect the shared infrastructure.

Verification and One-Time Passwords

If you use Channels to deliver verification codes or one-time passwords, delivery depends on the same chain of carriers and providers that we describe above. Each code expires after the window that you configure. We recommend that you provide an alternate verification path for recipients whenever code delivery fails.

SMS Credits

We bill SMS against SMS credits that you purchase separately from your plan subscription. The price of a credit varies by destination country and carrier route, and we deduct credits for each message segment that we deliver. We refund unused credits only where the law requires a refund. Credit balances expire according to the terms that we publish at the time of purchase.

Prohibited Content

The prohibitions below apply to everything that you send through Channels.

• You may not send unsolicited bulk messages, commercial messages without consent, or spam.
• You may not send phishing attempts, fraudulent messages, or messages that impersonate another party.
• You may not send malware, malicious links, or content that depends on disguising its origin.
• You may not send content that violates applicable law or promotes illegal activity.
• You may not send content that infringes intellectual property rights or breaches confidentiality obligations.

Compliance Retention

Channels retains compliance records, including consent signals, opt-out events, and delivery status, for up to seven (7) years so that you can respond to inquiries from regulators or carriers. You may request an export of your compliance records through the product.

OneCloud

OneCloud is the file storage product on the Apps Platform. You can attach files to contacts in People and to records in Tables, while Shared Drives let teams collaborate under the access controls that Teams manages.

Storage Limits and File Sizes

The maximum file size depends on your plan tier and ranges from 100 MB on Starter to 4 TB on Enterprise, as we document on the pricing page. The total storage for each workspace also depends on your plan. You are responsible for monitoring your usage and for removing the files that you no longer need.

Encryption and Integrity

OneCloud encrypts files at rest with AES-256 and in transit with TLS 1.3. It also computes an integrity checksum for every upload. When you enable version history, OneCloud retains the previous versions of each file so that you can compare or restore them. On plans where versioning counts against storage, you are responsible for the cost of retaining those versions.

Access Controls and External Links

• Internal access: Teams roles control who can read, write, or manage each folder and Shared Drive.
• Shared Drives: A team owns each Shared Drive, so the shared content remains available to the team when you deactivate a member.
• External links: You can create time-limited, signed links for people outside your workspace. You are responsible for expiring or revoking each link once its recipients no longer need access, since a misconfigured external link can expose content to unintended audiences.

Retention, Legal Holds, and Deletion

You can configure retention schedules for a folder or a Shared Drive so that OneCloud deletes its files after a set period. A legal hold overrides any retention schedule and preserves the affected files until the hold ends. When a retention schedule deletes a file, OneCloud permanently removes that file after the grace period that we describe in the Data Retention section below, at which point the file becomes unrecoverable.

Prohibited Content

The prohibitions below apply to everything that you store or distribute through OneCloud.

• You may not store or distribute content that violates applicable law, including child exploitation material.
• You may not store or distribute malware, viruses, or any software whose purpose is to harm third parties.
• You may not store or distribute content that infringes intellectual property rights or that bypasses technical protection measures.
• You may not store or distribute pirated or otherwise unauthorized copyrighted material.

Teams

Teams is the access management product on the Apps Platform. Teams applies membership and roles across People, Channels, OneCloud, Tables, Builder, Wallet, and Beryl. It also connects to your identity provider so that provisioning and deprovisioning stay in step with your HR records.

Roles and Audit

The standard roles, which are Admin, Editor, and Viewer, and your custom roles determine what members can do in each product. Teams records every permission-relevant action in the audit trail, which you can export for compliance reviews. You are responsible for reviewing the audit trail, for investigating anomalous activity, and for keeping role definitions aligned with the least privilege that each member needs.

Single Sign-On and Directory Sync

Teams supports SAML 2.0 and OpenID Connect for single sign-on, along with SCIM 2.0 directory sync. The identity providers that Teams supports include Microsoft Entra ID, Google Workspace, Okta, OneLogin, and any compatible SAML 2.0 or SCIM provider. You are responsible for configuring your identity provider, including the metadata exchange, certificate management, attribute mapping, and group-to-role provisioning rules. Because the timing of deprovisioning depends on how your identity provider delivers change events, confirm the behavior that you expect in a test environment before you rely on it to remove access.

Member Activity

You are responsible for all activity that the members of your workspace perform, whether or not that activity is authorized, until you remove the member or change the member's role. When a member leaves your organization, we recommend that you rotate credentials, revoke sessions, and review the audit logs.

Tables

Tables is the collaborative database product on the Apps Platform. Each database uses a managed Postgres or SQLite engine with indexing, constraints, and real-time collaboration, while AI-computed columns use Beryl Lens.

Data Storage and Integrity

We store your Tables data on managed database infrastructure that we operate through Conjoin. We encrypt that data in transit with TLS and at rest with AES-256. We also take an automated snapshot of every database each day, while the point-in-time recovery window and the snapshot retention period depend on your plan tier. For critical data, we recommend that you also export your own backups through the Tables export tools.

Real-Time Collaboration

Tables merges concurrent edits through conflict-free resolution. It also shows the activity of other members through live cursors and presence indicators. Tables records every edit in the change history, together with the member, the timestamp, and the previous value. When someone makes an unwanted change, you are responsible for restoring the previous value, either through the change history or through a point-in-time restore.

AI-Computed Columns

Each AI-computed column sends the content of its row to Beryl Lens, along with the content of any related rows that you configure it to include. Before Beryl Lens sends any request to a third-party AI model provider, it applies the policies that you set in Beryl Guard, including redaction and budget caps. Beryl Lens then writes each output back to the column as data that you own. The Delalify AI Terms and the AI Provider Policies apply to your use of AI-computed columns.

Customer Responsibilities

• You must design schemas and relations that match your data and your privacy commitments.
• You must review the outputs of AI-computed columns before you act on them in regulated workflows.
• You must export periodic backups of any data that you cannot afford to lose.
• You may store in Tables only the data that you are permitted to process.

Builder

Builder, which consists of Sites, Apps, Workflows, and Components, is the no-code creation product on the Apps Platform. When you describe what you want, Beryl Agents generate sites, mobile apps, desktop apps, and workflows, which you can then review, adjust, and publish.

Customer Content Responsibility

You are solely responsible for the content, code, and behavior of everything that you build with Builder, including pages, logic, data, third-party integrations, and anything that Beryl Agents draft on your behalf. You warrant that your Builder projects contain no malicious software, infringe no third-party rights, and violate no applicable law.

Hosted Sites and Apps

When you publish a Builder Site or a web-based Builder App, Delalify hosts your project on Delalify-managed infrastructure and makes it available on the public internet. Your project receives a Delalify subdomain by default, although you can connect a custom domain when you are ready. You are responsible for configuring the DNS records for your custom domain, while Delalify provisions TLS certificates automatically for verified domains. Hosted projects scale automatically under normal traffic; however, under load, during traffic spikes, or during denial-of-service attacks, Delalify may throttle a hosted project, or the project may cost more to operate. Delalify is not liable for charges that result from traffic spikes, misconfigured scaling, or attack traffic that targets your project.

Native Apps

Builder can generate native apps for iOS, Android, macOS, Windows, and Linux. When you distribute a native app through a platform store, such as the Apple App Store or Google Play, that store's own policies apply to the distribution. You are responsible for registering the store account, submitting the app, complying with the store's review, and the ongoing distribution of the app. Delalify does not warrant that any store will accept a native app that Builder generates.

Workflows

Builder Workflows provide visual backend logic for your Builder projects. Builder saves the state of a workflow after each completed step, so an interrupted execution resumes from the last saved point. Builder delivers webhooks and API calls to external systems on an at-least-once basis, so you are responsible for designing the receiving side to be idempotent. An approval gate pauses a workflow until a person records a decision or until the configured timeout expires. You are responsible for monitoring pending approvals and for configuring timeout actions that match your business rules.

Hosting Acceptable Use

The prohibitions below apply to every hosted Builder Site and App.

• You may not use a hosted project to mine cryptocurrency or to perform proof-of-work computations.
• You may not use a hosted project to serve malware, phishing pages, or credential harvesters.
• You may not use a hosted project to operate open proxies, anonymization relays, or traffic-laundering services.
• You may not use a hosted project to host pirated content or to help anyone circumvent technical protection measures.
• You may not use a hosted project to host any content that applicable law prohibits.
• You may not use a hosted project to build or operate a product whose primary function competes with Builder or with Apps Platform hosting.

If anyone uses a hosted project in breach of this acceptable-use section, we may suspend or terminate that project. We will give advance notice where circumstances permit; however, where the breach creates a security, legal, or safety risk, we may act immediately.

Deployment Lifecycle

Each deployment remains in place until you remove it. Builder retains previous deployment versions for rollback within the limits of your plan tier. When you delete a project, Builder removes its hosted site or app, its domain bindings, and its workflow schedules. However, the related data in Tables, OneCloud, and People remains until you delete it through those products.

Wallet

Wallet is the payments product on the Apps Platform. It provides invoicing, recurring billing, branded checkout pages, marketplace split payments, and tax calculation. Wallet processes payments through regulated payment processors and sends customer notifications through Channels.

What Wallet Is Not

Wallet is not a bank, and it does not issue payment cards, hold stored-value balances, or take deposits. Wallet also does not act as a money transmitter on its own behalf. All custody of customer funds remains with the regulated payment processors that Wallet uses, which hold those funds under their own licenses and their own agreements with you.

Payment Processing

Wallet routes each payment to either Stripe or Paystack, depending on the jurisdiction of your billing entity. Stripe and Paystack each collect and process payment information. Each of them may also collect additional information, including device identifiers, transaction details, and data that it gathers through cookies and similar technologies. They use that information to process payments, prevent fraud, strengthen authentication, and improve their services. For details, review the Stripe Privacy Policy and the Paystack Terms. Each processor handles the data that it receives under its own terms, applicable law, and the Delalify Privacy Policy.

Card Data and PCI

Delalify servers never store, process, or transmit card data, and your servers never do so either when you use Wallet's hosted checkout pages or payment elements. The payment processor is responsible for the PCI DSS scope of card data. If you choose to collect card data outside Wallet's hosted pages, you must maintain the PCI DSS compliance that is appropriate to how you handle that data.

Merchant of Record

When you use Wallet, you act as the merchant of record for the transactions that you process, which means that you are responsible for each item below.

• You must comply with the applicable payment regulations and card-network rules.
• You must give your customers accurate descriptions of your products or services, accurate pricing, and accurate refund policies.
• You must handle customer disputes, chargebacks, and refund requests.
• You must determine, collect, remit, and report the taxes that apply to your transactions, as we describe below.
• You must carry out the identity verification (KYC) and anti-money-laundering checks that applicable law requires of you.

Invoicing and Recurring Billing

Wallet generates branded PDF invoices, tracks payment status, and manages subscription lifecycles, including trials, pauses, proration, and automatic retries of failed charges. Wallet applies proration and dunning schedules automatically according to its current calculation methods, which Delalify may update with notice. You are responsible for verifying the proration amounts in your own billing scenarios.

Checkout Pages and Collections

Wallet Collections provides public-facing branded checkout pages that Delalify hosts on its own infrastructure. You are responsible for the accuracy of the products, prices, descriptions, and refund policies on each page, and for honoring the terms that the page shows to the customer at checkout.

Marketplace

Wallet Marketplace handles buyer payments, configurable platform fees, vendor payouts, escrow, and payout schedules. During vendor onboarding, Wallet Marketplace collects the identity verification and payout details that the underlying processor requires. You are responsible for each item below.

• You are responsible for your agreements with vendors and buyers, including the terms of sale and the refund policy.
• You must verify that your vendors have the legal right to sell what they list.
• You must carry out any additional KYC, AML, or sanctions screening that the law requires in each jurisdiction where you operate.
• You must configure platform fees, escrow rules, and payout schedules so that they match your agreements with your vendors.

You may process transactions through Wallet Marketplace only within the rules below.

• You may not process transactions for illegal goods or services.
• You may process transactions for gambling or gaming services only where applicable law explicitly permits them and the services hold the required license.
• You may process transactions for adult content or services only where the law explicitly permits them and proper age verification is in place.
• You may not process transactions for cryptocurrency exchanges, unregulated financial instruments, or securities offerings.
• You may not process transactions for multi-level marketing or pyramid schemes.
• You may not process transactions for counterfeit goods or for goods whose sale violates intellectual property rights.
• You may process debt collection transactions only in a jurisdiction where you hold the license to collect.
• You may not process transactions in any category that the underlying processor prohibits under its own acceptable-use rules.

Tax Calculation

Wallet Tax is an optional tax calculation feature that you can enable for your invoices, subscription charges, and checkout payments. If you enable it, the following terms apply.

Tax calculation is a tool, not tax advice. Wallet's tax calculation feature provides estimated tax amounts for your convenience, and those estimates are not tax, legal, or accounting advice. Consult qualified tax professionals about your obligations in each jurisdiction where you operate or sell.

Delalify gives no guarantee of accuracy or completeness. Delalify updates tax rates periodically for supported jurisdictions, but Delalify does not warrant that any tax calculation is accurate, complete, current, or applicable to your specific transactions. Because tax laws and rates change, Wallet's rate data may be out of date in some jurisdictions. Product classification, nexus determination, and exemption eligibility are outside the scope of Wallet's tax calculation feature.

You bear sole responsibility for tax compliance. Whether or not you use Wallet's tax calculation feature, you are solely responsible for each item below.

• You must determine which taxes apply to your transactions and in which jurisdictions.
• You must verify every tax amount that Wallet calculates before you issue an invoice.
• You must register for tax collection in each applicable jurisdiction.
• You must file returns and remit the taxes that you collect to the appropriate tax authorities.
• You must maintain the records that applicable tax laws and regulations require.
• You must configure the tax settings in Wallet correctly, including whether tax is inclusive or exclusive, the applicable tax types, and each customer's exemption status.

You indemnify Delalify for your use of tax calculation. You agree to indemnify, defend, and hold harmless Delalify and its officers, directors, employees, and agents from and against any claims, penalties, fines, assessments, liabilities, damages, costs, and expenses, including reasonable legal fees, that arise from or relate to your use of or reliance on Wallet's tax calculation feature, including errors or omissions in tax amounts, any failure to collect or remit taxes, and any non-compliance with applicable tax laws.

Delalify excludes liability for tax calculation. Under no circumstances will Delalify be liable for tax deficiencies, penalties, interest, or other costs that result from inaccurate tax calculations, whether or not you relied on Wallet's tax calculation feature. This limitation applies even if Delalify was advised of the possibility of such damages.

Fees

Wallet charges transaction and platform fees according to the schedule that we publish on the pricing page. Each payment processor, such as Stripe or Paystack, charges its own processing fees directly, separately from Wallet fees.

Beryl

Beryl, which consists of Context, Insight, Compose, Orchestrate, Guard, Agents, and Lens, is the AI layer that Delalify builds into every Apps Platform product. When Beryl accesses your data, it uses the same roles and permissions that each member already has. Beryl can act on that data through chat interfaces, workflows, and autonomous agents.

Scope and Components

• Context: Context provides semantic search across People, Channels, OneCloud, Tables, and Teams, and limits the results to what each member's existing permissions allow.
• Insight: Insight derives engagement, health, and risk signals from activity across the Platform.
• Compose: Compose drafts replies, summaries, and follow-ups that reference your data.
• Orchestrate: Orchestrate provides cross-product workflows that call on Beryl for the steps that require reasoning.
• Guard: Guard enforces policy, including PII redaction, budget caps, topic restrictions, and audit logging.
• Agents: Agents provides goal-directed agents that can operate for up to 24 hours per session, with full permission checks on every action.
• Lens: Lens provides the AI-computed columns in Tables, which categorize, summarize, score, and extract data from rows.

AI Terms Apply

The Delalify AI Terms apply to your use of Beryl. In those terms, we set out third-party provider obligations, training-data commitments, output disclaimers, content restrictions, and restricted use cases. We keep the list of third-party AI model providers that Beryl may route requests to at any given time, together with their acceptable-use policies, current on the AI Provider Policies page and the Subprocessors page.

Governance Through Beryl Guard

Beryl Guard applies organization-level policy to every Beryl request before Beryl sends that request to a third-party AI model provider. Guard redacts personal data, financial identifiers, and health information patterns from prompts and caps spending for each workspace, team, agent, or user. Guard also restricts topics and behaviors and records each decision in an audit trail. Guard applies the policies that you configure to match your compliance needs. Delalify does not warrant that Guard detects and redacts every possible sensitive token in every language or format, so you remain responsible for the content that you put into prompts.

Permission Inheritance

On every request, Beryl checks the permissions that the member holds through Teams, so Beryl accesses a record on a member's behalf only when that member can open the record directly. That permission check applies to Context searches, Compose drafts, Orchestrate steps, Agent actions, and Lens column computations.

Agents

Beryl Agents can operate for up to 24 hours per session, with full permission enforcement on every action. Agents may write to your data across products, including by creating records, sending messages, uploading files, and initiating transactions, but only where the initiating member and the agent configuration permit the action. You are responsible for each item below.

• You must configure approval gates for steps that affect customers, money, or regulated data.
• You must monitor agent sessions and intervene when an agent goes off track.
• You must set Guard policies that limit spending, topics, and permissions.
• You must review agent output before you act on it in a legal, medical, financial, or safety context.

Customer Responsibilities

• You must review and verify AI outputs before you use them in production workflows or in decisions that affect your customers.
• You must configure Beryl Guard policies that match your compliance and security requirements.
• You must use Beryl in line with the acceptable-use rules of the underlying third-party AI model providers.
• You must monitor AI usage and costs through the workspace dashboard and the Guard reports.

Cross-Product Orchestration

Automation and Integration are capabilities that connect the Apps Platform products, but Delalify does not offer either one as a standalone product. Automation operates event-driven workflows across People, Channels, OneCloud, Tables, Wallet, and Builder, while Integration connects the Apps Platform to third-party systems through pre-built connectors and two-way sync.

Automation

Automation uses the same workflow engine as Builder Workflows. Its triggers include contact and tag changes in People, messages in Channels, files in OneCloud, row and field changes in Tables, payments in Wallet, and webhooks from external systems. For each execution, the engine saves state after every step, retries with a configurable backoff, and records a full audit trail. The engine delivers webhooks and API calls to external systems on an at-least-once basis, so the receiving side should be idempotent.

Integration

Integration provides pre-built connectors for customer relationship management systems such as Salesforce and HubSpot, help desks such as Zendesk, and productivity suites such as Google Workspace and Microsoft 365. Two-way sync keeps People and the connected system aligned under the rules that you configure. You are responsible for each item below.

• You must provide credentials for the connected system and limit their scope to the minimum that the connection requires.
• You must comply with the terms of the connected system.
• You must resolve sync conflicts and manage the duplicate detection rules and the field mapping.
• You are responsible for the accuracy of the data that you import into the connected system or export from it, including the records that Integration syncs into People from external sources.

Delalify is not liable for the behavior, availability, or data practices of connected third-party systems. If the provider of a third-party system changes its API, terms, or availability, we may need time to update the Integration connector for those changes.

Customer-Controlled Deletion

You can delete data in every Apps Platform product through that product's own interface. You can delete contacts from People, conversations from Channels, files from OneCloud, rows and tables from Tables, projects from Builder, invoices and customers from Wallet where the underlying processor permits it, and audit records for members who leave Teams in line with your retention policy.

Workspace Termination

When you or Delalify terminates a workspace, the rules below apply.

• Grace period: We retain the workspace data for thirty (30) days after termination, during which you may request recovery or export of the data.
• Permanent deletion: After the grace period ends, we permanently and irreversibly delete the workspace data from live systems.
• Backup retention: We may retain encrypted disaster-recovery backups for up to ninety (90) days before we permanently delete them.
• Legal and compliance retention: Where the law requires it, we retain some data beyond these windows, including financial records, tax records, audit logs, and data that is subject to a legal hold or an investigation.

You are responsible for exporting anything that you want to keep before the grace period ends. Delalify is not liable for data loss that results from workspace deletion, mis-scoped retention rules, or missed export deadlines.

Audit Log Retention

We retain Teams audit logs and Beryl Guard audit logs for the period that applies to your plan tier, although customers on an Enterprise plan can negotiate longer retention windows. We retain the Channels compliance audit logs, including consent and opt-out records, for up to seven (7) years, as we describe in the Channels section.

Legal and Compliance Retention

Notwithstanding the windows above, Delalify may retain certain data where law or regulation requires it, including financial and billing records, the audit trails that compliance attestations require, data that is subject to a legal hold or a regulatory investigation, and the records that Delalify needs to defend legal claims. We store retained data under the protections that we describe in the Privacy Policy and the Data Processing Agreement.

Some Apps Platform surfaces are visible on the public internet, including Builder Sites, Builder Apps with public routes, People Forms that you embed on third-party sites, Wallet Collections checkout pages, Wallet Marketplace listings, and OneCloud external shared links. In this section, we add the rules that apply to those public surfaces.

Your Content on Public Surfaces

Delalify does not review published content or Form submissions in advance, so the decision about what appears on your public surfaces is yours. You are responsible for the legality and accuracy of that content, for honoring the commitments that you make to visitors, such as the prices at checkout or the privacy notices on forms, and for handling the data that you collect through public surfaces under applicable law.

Custom Domains and TLS

When you connect a custom domain, you must configure the DNS records that we document in the product. Delalify issues and renews TLS certificates automatically for verified domains. You are responsible for keeping your DNS records correct, because a DNS misconfiguration can affect certificate issuance and availability.

Traffic, Abuse, and Takedown

Hosted surfaces scale automatically under normal traffic; however, Delalify may throttle them under load, during spikes, or during attacks. Delalify is not liable for charges that result from traffic spikes, misconfigured scaling, or denial-of-service attacks. We may take down or restrict content on public surfaces in response to a security or safety issue, a credible report of abuse, or a valid legal request, including a DMCA request. We handle copyright complaints through the process that we describe in the General Terms.

External Shared Links

OneCloud external shared links give people outside your workspace access to your content. Anyone who holds a valid link may access the content that it points to until the link expires or someone revokes it, so you are responsible for the expiration, revocation, and audience of every link that you issue. Treat each shared link as a capability token, and do not use shared links to publish sensitive content.

Documentation

We publish the documentation for every Apps Platform product, including guides, how-tos, and reference material, in the Delalify knowledge base.

Support Channels

The support that you receive depends on your plan tier.

• Starter Plan: Starter Plan customers can use the documentation, community resources, and self-service help.
• Pro Plan: Pro Plan customers receive email support, with the response times that we describe in the General Terms.
• Teams Plan: Teams Plan customers receive priority email support and access to onboarding and success resources.
• Enterprise Plan: Enterprise Plan customers receive dedicated support channels, including shared Slack channels, phone support, and an assigned Business Solutions Architect, as we describe in the Enterprise Service Level Agreement.

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

Status and Incident Communication

We publish the service status, scheduled maintenance windows, and incident updates for the Apps Platform at status.delalify.com. You can subscribe to status updates by email or webhook so that you receive a notification whenever a disruption occurs.

Platform Security

Delalify operates the Apps Platform in line with industry-standard security practices and maintains the certifications and attestations that we list on the trust center. We encrypt data in transit with TLS 1.3 where the connection supports it and encrypt customer content at rest with AES-256 in every data store that holds it. Our incident response program includes detection, containment, customer notification, and post-incident review.

Customer Security Responsibilities

Security on the Apps Platform is a shared responsibility, which means that you are responsible for each item below.

• You must protect the sign-in credentials, recovery codes, and session tokens of every member.
• You must configure Teams roles, single sign-on, and directory sync to match your security policy.
• You must keep Channels consent records and Forms consent disclosures accurate.
• You are responsible for choosing what to publish on Builder Sites, Builder Apps, Forms, Collections checkout pages, and Marketplace listings.
• You must configure Beryl Guard policies, agent approval gates, and budget caps.
• You must review the audit logs in Teams, OneCloud, Wallet, and Beryl Guard on a schedule that matches your risk.
• You must notify Delalify promptly of any suspected incident that affects your workspace or your data.

Incident Notification

We notify customers of security incidents that affect their data in line with applicable law and our incident response policy. For an incident that involves personal data subject to the Data Processing Agreement, we follow the notification timing that we commit to in that agreement.

Updates and Changes

We may update these Apps Platform Terms from time to time to reflect changes in our products, our legal obligations, or our business practices. Before a material change that reduces your rights or increases your obligations takes effect, we will give you at least thirty (30) calendar days' advance notice through one or more of the channels below.

• We can email the workspace owner and the billing owner at the addresses associated with the workspace.
• We can post notices inside the Apps Platform products that you use.
• We can update the documentation.

If you continue to use the Apps Platform after a change takes effect, you accept the updated terms. If you disagree with a change, stop using the Apps Platform before its effective date and work with our team on a wind-down.

If you have a question, a concern, or a request for clarification about these Apps Platform-Specific Terms, contact us at the address below that matches your request.