Effective October 17, 2026.
This notice covers Rivell Connections, operated by Rivell, LLC, and the authorized internal applications that use its account connections. The YouTube features use YouTube API Services. Contact [email protected] with privacy questions or data-removal requests.
Account and Platform Information Used by Rivell
The service uses corporate identity and membership to control access; platform account identifiers, permission scopes and resource selections to manage connections; and selected records for the workflows you authorize. OAuth tokens and API credentials are encrypted in the central vault and used on the server. An approved consuming application receives permitted records or results, rather than the platform credential.
Optional Google features include reporting aggregates, Tag Manager metadata, Gmail headers, calendar events, contacts, tasks, selected Drive folder and document metadata, and YouTube channel and upload metadata. The general Google reader excludes Gmail message bodies and Drive document contents. Connecting one feature does not authorize every Google feature.
Publishing uses the content, media address, schedule, audience and other settings you review. Delivery records include timestamps, internal request identifiers and provider receipts. The YouTube uploader transfers video bytes from an approved public HTTPS source or the optional private Studio exchange described below. Rivell Connections does not maintain a permanent video archive. The source application, authorized receiving application and destination provider manage their copies.
Use and sharing
Data is used to operate the features you authorize, maintain access controls, diagnose failures and prevent duplicate actions. Necessary data is sent to the selected provider and the specifically approved internal application. Rivell’s configured hosting and identity services support operation and security. Separately authorized intake workflows may send selected business call, voicemail or form content to a configured model provider and CRM. A Google account connection alone does not authorize those transfers.
Rivell Connections follows the Google API Services User Data Policy, including Limited Use. Google user data is not sold, transferred for resale, used for advertising or used to train generalized AI or machine-learning models. Access by administrators or service providers is limited to authorized functionality, permitted security purposes and applicable legal obligations.
Publishing may make your content available outside Rivell according to the audience you select. Connecting a platform does not make private workspace files public. Corporate authentication uses necessary session and access cookies; the public informational website may use its own cookie controls.
YouTube data and removal
In the current service, YouTube account metadata is refreshed or removed within 30 days. Imported analytics and comments are removed within 30 days of retrieval; delivery content and provider receipts are removed within 30 days of their first dispatch. Requests to remove app-held YouTube data are handled promptly and within seven days, including authorized downstream copies. Use the account’s data-removal control or contact [email protected]. User-authored drafts can remain unless separately removed.
New current-service backups exclude YouTube API records and YouTube-specific credentials. Restoring a backup requires reconnecting YouTube. Shared Google credentials needed for other separately authorized features remain subject to the account’s revocation and removal controls.
Legacy hosting history: YouTube records and stored account tokens were removed from the retired Sites application on October 17, 2026, and its Google connection setup was disabled. Provider-managed recovery copies remain under an active removal request. Their erasure has not yet been confirmed; we do not count those copies as deleted or use them to restore YouTube data.
Removing a local workspace binding is different from revoking Google authorization. A Google project can contain several authorized connections for the same person; revocation can affect all of them. The app will show the affected connections before that broader action. Opaque internal delivery markers may remain to prevent duplicate submissions after content is erased.
You can also revoke access in Google account permissions. Removing data held by Rivell Connections does not delete a video or other content stored by YouTube. Use YouTube’s own controls to manage that content. Google explains its handling in the Google Privacy Policy.
Optional Tesla fleet connections
When you authorize a Tesla connection and choose vehicles, Rivell Connections can retrieve your Tesla account identity and the selected vehicles’ identifiers, battery and range readings, charging readings, odometer, vehicle condition, software and other available vehicle information. Precise location and movement information require the separate vehicle-location permission. The connection is used for inventory, tracking and observed fleet analytics in the specifically authorized CoreHexa Fleet Manager workspace. Authorizing the account does not automatically share every vehicle with every application.
Tesla account tokens stay encrypted in the central vault. Fleet Manager receives only records allowed by its server-side application and vehicle grants. The service does not request vehicle-command permissions, wake sleeping vehicles, collect camera/audio recordings, sell Tesla data, use it for advertising or send it to a model provider for training. Missing readings remain unavailable. Periodic snapshots are not complete historical trip or charging records.
Fleet Manager keeps the latest permitted position for tracking. Its metric history excludes coordinates and retains observed samples for up to 365 days. The Hub keeps the current selected snapshot. Pausing a Fleet Manager import stops its local collection but does not revoke the upstream Tesla connection. Removing its read grant clears currently exposed readings on the next access check, normally within one minute. Separately recorded fleet assignments, vehicle photos and maintenance records remain operational records.
Review selected vehicles and application access in Rivell Connections. You can withhold or withdraw the Tesla vehicle-location permission, revoke Tesla authorization through your Tesla account, or remove the central connection. Contact [email protected] to request access, correction or removal of app-held Tesla records and any affected downstream copies. Withdrawal or deletion requests must be applied before retained copies can be restored. Tesla handles information sent to it under its own Customer Privacy Notice.
Continuous Tesla route history
When you enable continuous Tesla tracking for a selected vehicle, Rivell Connections receives timestamped precise GPS positions and related speed, heading, gear, odometer, battery and range readings directly from that vehicle. The authorized CoreHexa Fleet Manager workspace uses these reports to show live position, recorded route playback and inferred trips. GPS route reports and the latest streamed location are retained for up to 90 days. Metric samples may be retained for up to 365 days under the existing notice. Reports begin when collection starts; sleeping, disconnected or private intervals may leave gaps.
The Tesla relay carries encrypted traffic and does not terminate the vehicle’s TLS connection or store its GPS reports. Only the central Hub and explicitly granted Fleet Manager workspace receive decrypted vehicle data. Disabling collection, withdrawing location access, revoking the application’s Tesla access or requesting deletion remains available under this notice. Retained backups must respect deletion requests before restore.
Optional private Studio video exchange
Added October 27, 2026. When you enable this exchange, Rivell Connections receives a temporary encrypted copy of an approved Studio video, together with its title, description, file checksum, source identifiers, approval record, rights information and selected destination. Only the applications and client you authorize through specific media grants can use that copy.
Studio keeps the original video. Connections transfers the approved file privately to Middle Moose and the authorized publishing service. Middle Moose saves a separate copy in the selected client’s private asset library, subject to that library’s access and deletion controls. Expiry of the Connections staging copy does not delete the Studio original or the Middle Moose library copy. The exchange does not make Studio files or download links public. Publishing still requires current permissions and your chosen account, audience and publishing policy.
Each staging file is limited to 100 MiB. Staging bytes expire after seven days, become unavailable at expiry and are removed by scheduled maintenance. Transfer receipts may remain. The staging cache and its destination metadata are excluded from YouTube-free recovery archives. Removing the relevant YouTube connection data also removes its staging copies and destination metadata.
Revoking an application or media grant stops that application’s access. Studio checks current rights and content approval before confirming a source; reads require a source confirmation no older than five minutes. Changes to source rights or approval stop that confirmation. These freshness checks do not promise instant withdrawal across applications.
YouTube API records continue to follow the YouTube retention, removal and backup policy above. This optional exchange does not authorize another client’s files, expand platform grants, renew a paid allowance or create a new billing obligation. Contact [email protected] to request removal of app-held copies.
Optional automatic Studio content review
Added October 27, 2026. When you enable automatic editorial review, Middle Moose sends the video’s title, displayed text, narration script, captions and timing, branding and source-rights information, and measured technical checks to the separately authorized model provider, currently OpenAI. This review does not send the video or audio file to the model provider. Platform credentials stay in Rivell Connections.
The review compares the wording and claims with your saved business facts and approved template. It records the model response, decision and source bindings with the workflow. These are automated checks of text, provenance and timing; they do not mean a person watched or listened to the video or that every frame received visual inspection.
Current source, application and model grants, the saved review policy and existing spending authorization control this feature. Enabling review does not renew a paid allowance, authorize a paid remake or authorize publication. Contact [email protected] about access or removal of app-held review records.
Security and policy changes
Rivell Connections uses corporate authentication, explicit application and resource grants, and encrypted platform credentials. These controls reduce risk but do not guarantee security. New data uses require updated disclosures and any necessary authorization.
This notice will be updated when the service’s data practices change. Material changes that require renewed authorization will be presented before the affected features can be used.