Oreniss privacy, terms, and customer delivery policies
Oreniss runs managed delivery for global SMB customers: service requests and delivery setup, reusable customer workspaces, agentic execution tracking, assisted setup, billing, invoicing, maintenance, and support communications.
This compatibility route opens the requested section inside the merged legal center while keeping the rest of the Oreniss privacy, delivery, billing, and consent policy content available below.
Privacy policy
Oreniss processes contact, organization, request, workspace, file, billing, consent, and support data to scope, quote, contract, execute, invoice, and maintain customer work.
Customer portal access requires a verified Google identity that matches an approved membership, verified customer contact, or verified customer identity. Company-name-only matching never grants access.
Oreniss managed workspace records remain the source of truth for rooms, files, agent runs, messages, tree views, grid views, and execution evidence. Oreniss exposes only customer-safe workspace folders through portal APIs.
Delivery terms
Oreniss managed delivery starts with a non-binding request review, then moves into a scoped offer, firm bid, contract state, execution path, acceptance gates, and maintenance where applicable.
Self-service setup is available when a customer can install approved access tooling. Human-assisted setup is used when onboarding, access, review, or fulfillment needs operator support.
Agentic execution is bounded by approved case scope, workspace folders, manual secret-safe infrastructure tasks, and customer or operator approval gates for sensitive actions.
Billing, invoices, and tax
Oreniss supports quotes, contracts, assisted-delivery lines, Oreniss Token ledger entries, Stripe checkout sessions, Stripe invoices, invoice events, and tax-ready invoice sync.
Oreniss Token pricing starts from the published token catalog and tier discounts. Customer-facing balances, purchases, and usage are shown as Oreniss Tokens while implementation costs remain internal.
Stripe live-mode mutations require explicit target confirmation. Downstream execution starts in Stripe test mode with automatic tax enabled on invoice and checkout payloads when configured.