VoraCommVoraComm

VoraComm membership agreement

Membership, payments, privacy, and cancellation.

These terms describe the operating policy for a VoraComm membership. Membership activation requires agreement to these terms and acknowledgment that BrainFabric is the backend communications fabric included with VoraComm.

Presale activation and billing

Presale access begins only when VoraComm is released.

A membership purchased during presale remains in a pending-activation state until release. Presale enrollment does not grant early access to the authenticated VoraComm workspace.

The calendar month in which presale access activates is the paid presale membership month. The following calendar month is provided without a membership charge. Standard membership billing resumes in the third calendar month.

Memberships created on or after release activate immediately after successful account, membership, payment, and policy validation and follow the normal billing schedule.

Monthly usage overview

Each operating period is one calendar month.

The operating and local-analytics period begins on the first day of each calendar month and closes on the final day of that same month.

On the first day of the following month, VoraComm makes the completed prior-month usage overview available to the user. Metrics are calculated locally from product usage and are not advertising-surveillance data.

Communication content itself is not a usage metric.

Automatic payment

Automatic payment is enabled by default when a recurring membership is activated. A customer may deactivate automatic payment before the next scheduled renewal.

Before the due date

Payment reminders are sent two days before the due date and again one day before the due date.

Days 1–3 late

After a failed or missed payment, VoraComm may retry collection once every 24 hours for the first three days. On day 3, Cancellation Notice 1 is issued.

15 days late

Cancellation Notice 2 is issued if the membership remains unpaid 15 days after the due date.

30 days late

Cancellation Notice 3 is issued if the membership remains unpaid 30 days after the due date.

45 days late

The membership account is canceled at 45 days past due. A canceled user must re-enroll to restore membership.

Notifications

Membership and payment notices may be delivered by BrainMail or VoraMail email, in-app notification, and text message. SMS notices are optional and the user may opt out of SMS delivery.

Email account requirement

A VoraComm membership account must use an approved BrainMail or VoraMail email account. The authentication backend is responsible for enforcing the accepted domains.

BrainFabric acknowledgment

BrainFabric is included as part of the VoraComm backend. A membership cannot be activated until the user has been informed of this integration and the required acceptance has been recorded by the authentication or membership backend.

Communication privacy

No sale of user information

VoraComm does not sell user information or communication data for advertising or data-broker purposes.

No ambient recording or advertising tracking

VoraComm policy does not permit hidden ambient recording, silent livestreaming, or advertising-profile tracking of user communications.

Live and non-live communications

Live audio or video is processed as live media only while the relevant live session is active. Content that is not part of an active live session is not livestreamed.

Encryption requirement

Communication content must be protected with encryption. Channels represented to users as end-to-end encrypted must satisfy the applicable end-to-end encryption contract before production availability.

Minimal operational records

VoraComm does not use communication content for behavioral advertising. Minimal account, billing, payment-attempt, consent, security, and user-requested evidence records may exist when required to operate the service, enforce these membership terms, protect the system, or fulfill an explicit user action.

Recording, evidence capture, or retention of communication content must be initiated by an authorized feature and is subject to applicable consent and policy controls.