Contents
1. Application and availability
These V1 terms supplement the applicable Tessen agreement for Connect and connected-tool actions across Web, Mobile, Code, Browser Extension, Orbit and developer services where available. They are not confirmation that every integration is available or that provider approval has been obtained.
A connection links a particular account, service or resource within specified permissions. It does not transfer ownership of that account to Tessen and does not grant access beyond the authority of the person approving it. The Privacy Notice and any executed DPA govern the corresponding personal-data processing.
2. Authority and consent
Before connecting an account, confirm that you may grant the requested scopes and use the data for the intended purpose. Organization policies or a third party’s rights may limit that authority. Authentication proves access to an account; it does not necessarily prove permission to disclose all its data.
Review the connected identity, read/write scopes and action destinations. A read permission is not a send permission. An organization administrator must not silently expand another user’s authority beyond the applicable agreement and notices.
3. Tokens, credentials and scope
Use the supported authorization flow and protect tokens, keys and sessions. Do not paste credentials into conversations or expose them in repositories. Tessen should process connection credentials only for authorized access and protect them according to verified security practices.
Connect actions require the implemented authorization and relevant provider scopes. The reviewed Web integration exposes connection/scopes and routes credential-dependent operations to its Connect service; provider credentials are not treated as general authorization for unrelated actions. These terms do not promise a particular encryption scheme or universal per-action approval. Technical checks must match the service’s real risk and authority model.
4. Reading, importing and context
A connection may retrieve content, metadata, files, contacts or other information within the enabled scope. Retrieved context may be used to answer questions, generate material or support authorized work. Imported material can persist separately from the source service if the feature stores it; the user must be informed of this behavior.
Instructions embedded in retrieved content are untrusted material, not authorization to change permissions or disclose unrelated information. The final service should distinguish source content, user instructions and system controls. Source deletion does not necessarily delete every previously imported copy or generated result.
5. Writing, sending and consequential actions
An action may modify a record, send a message, publish content, create a file or affect another person. Review recipients, account identity, scope and important consequences before granting authority. A prior authorization can cover a bounded workflow but should not be interpreted as unlimited permission for unrelated actions.
Users should understand whether work continues unattended and how to cancel it. External effects may be irreversible and a repeated request may create duplicates unless the relevant system prevents them. Tessen should communicate failed or partial actions accurately rather than imply success from a planned action.
6. Third-party conditions and interruptions
Connected services retain their own terms, limits, privacy practices and availability. A provider can change its API, revoke access or restrict a feature. Tessen’s obligations for an engaged processor differ from obligations concerning a user-selected independent recipient.
Do not use Connect to circumvent provider restrictions, abuse rate limits, scrape prohibited data or evade opt-outs. Connection availability does not imply legal permission for bulk outreach, surveillance or redistribution. The Subprocessor Register should distinguish the relevant roles.
7. Revocation and removal
You may revoke a connection using the controls actually available in Tessen or the provider’s account settings. Revocation should prevent future access according to the actual token lifecycle, but may not undo completed actions or erase previously imported content. Scheduled work depending on the connection may fail or stop.
The reviewed disconnect route first disconnects the subject-scoped Connect record and then the Web ledger; if the service step fails it does not claim a successful disconnect. Neither step revokes the external provider grant. Provider-side revocation, deletion of imported content, cancellation of active work and retention of lawful logs are separate operations. The final UI and notice must explain these differences. Uninstalling an application is not always equivalent to revoking an external authorization.
8. Organizations, developers and responsibility
Business customers must manage authorized users, service accounts and administrator permissions. Developers must provide their own users with clear notices and control flows. They may not treat Tessen’s connector permission as end-user consent to every downstream disclosure.
The parties remain responsible for the processing and security obligations each actually controls. Tessen’s tools do not replace a customer’s access policy or necessary processing agreements. Sensitive or regulated integrations require suitability assessment before use.
9. Incidents, suspension and related terms
Report unexpected access or actions promptly through support, identifying the connected account and request context without exposing credentials. Revoke access if necessary and investigate completed effects. Tessen may suspend a connection to address security, abuse or legal requirements within the underlying agreement.
Read the Privacy Notice, Service Terms, Acceptable Use and Developer Terms. Governing law, liability and other open legal choices remain in the underlying agreement; this supplement creates no separate jurisdiction or unverified guarantees.