Terms of service
& data use
How company work records are used, who can access them, and what connecting your tools means.
Draft version · October 4, 2026
Log work accurately. Company work records may be accessed and shared with authorized people. Keep client and team information internal, connect only approved tools, and protect your keys. Reporting is read-only; your legal rights remain intact.
01Scope and purpose
These terms describe how OuterScope Studios (the company) operates its internal timekeeping workspace and how authorized team members may use it. They cover the website, time entries, reports, exports, API keys, MCP connections and related administrative features. The workspace supports company operations and is intended for authorized business use, not personal storage or public publication.
This version is a proposed policy for owner and legal review. It has not been deployed as a new agreement or recorded as accepted by any user. Before adoption, the company must confirm its legal entity, applicable jurisdictions, existing employment and contractor agreements, and any required notice or consultation. This page alone does not change an employment relationship, compensation arrangement or client contract.
02Accounts and authorized use
Use your own account and keep sign-in credentials private. Access depends on your current role, account status and assignments. The owner may grant, narrow, suspend or remove workspace or integration access for legitimate operational or security reasons. Access to another person's records is permission to use those records for an authorized business purpose, not permission to publish them or bypass access controls.
Do not impersonate another person, borrow another person's account, attempt to obtain hidden records, defeat rate limits, run unauthorized automated collection, or interfere with the service. An administrator's ability to manage access does not authorize arbitrary changes to the underlying facts of a time entry.
03What the workspace records
Records can include first and last names, account identifiers, roles, work assignments, clients, scopes, work types, start and end dates and times, elapsed duration, the time an entry was submitted or updated, its saved timezone and local time, approval status, descriptions, accomplishments and notes. Other parts of the workspace may hold authorized financial or administrative information under their separate access controls; that information is not part of the read-only reporting API.
A time entry describes reported work. Its timestamps and saved timezone do not establish that someone was online, physically present at a location, or signed into a particular application. Timezone settings and manually entered records may require correction. People should describe work clearly and avoid entering unrelated personal information.
04Company records and work product
Time entries, business descriptions, work notes, accomplishments and related reports submitted for company work form part of the company's operational records. Subject to applicable law and existing agreements, the company may retain, access, organize, copy, review, correct through authorized processes, combine and use these records to manage work, coordinate teams, verify delivery, prepare reports and maintain an audit history.
Company work product is owned or licensed as provided by the relevant employment, contractor and client agreements. To the extent you have the necessary rights, you authorize the company to use submitted work information for those business purposes and share it with authorized recipients. These terms do not transfer ownership of your personal identity, unrelated personal material, pre-existing intellectual property or third-party material that you do not own, and do not override a client's rights.
05Internal access and sharing
The owner can access organization-wide reporting. Members can only access their own hours; leads default to themselves and their assigned team, excluding owner hours. An owner-configured reporting list replaces a lead’s default team set while self remains. It may remove overseen people or add people, including the owner’s own hours after confirming elevated sharing. Member access cannot expand beyond self. Keys retain the people selected at creation and intersect current permissions; new grants do not expand existing keys. Removing access applies to subsequent integration requests. Authorized company personnel may review records relevant to their responsibilities.
The company may distribute permitted records internally for staffing, supervision, project coordination, quality checks, reporting and other legitimate operational needs. The company aims to keep records confidential and internal. Any external disclosure must have an authorized business or legal basis and respect applicable privacy law, employment rights and client commitments. This policy does not authorize public posting of a team's hours or client work.
06Names and reporting privacy
Full names may appear in the authenticated workspace, including the people picker used to select whose hours a key can read. The reporting API and MCP data responses expose first names rather than structured last-name fields. Internal identifiers distinguish people who share a first name. Known team surnames are redacted from returned work text.
Descriptions, notes and accomplishments are included in reporting. Automated redaction has limits: it cannot guarantee identifying an unknown surname, every personal detail, every financial reference or every secret embedded in free text. First-name-only reports are not anonymous. A client, project, timestamp or work description may still identify a person. Review content before submission and before sharing an export or generated answer.
07Read-only API and MCP
Reporting integrations return permitted time data only. They cannot edit or approve entries, manage payments, change permissions, run arbitrary database queries or use a reporting key to manage other keys. The public response schema excludes structured pay rates, labor costs, revenue, profit, margin, billing amounts, invoices, receipts, banking information, password hashes and authentication tables.
The ten available reads are access context, time-entry search, one entry by ID, daily and weekly hours, work history, people summaries, clients, scopes and work types. Access context lists permitted people and key date limits without requiring a date range. People summaries include zero-log people and describe only the requested work window. Requests may filter by person, client, scope, work type, status, timezone and date range. The documentation and OpenAPI schema describe the current endpoints, fields and limits. Features that require unconfigured infrastructure or sign-in remain unavailable until activated.
08Keys, limits and responsibility
You may create keys only for yourself. Each non-owner account may have up to three active keys. The owner is exempt from this personal cap, while service-wide storage and abuse controls still apply. Choose a useful name, select only the people the key needs, and choose all time or a narrower date window. A key can never grant more access than its owner's current permissions. Newly granted people are not automatically added to an existing key.
A key is a bearer credential: anyone possessing it can make requests within its permissions. The secret is shown once and stored only as a hash. Keep it in an appropriate secret store or local environment variable, not source control, public messages, screenshots or shared documents. Keys expire after 90 days. Rotation replaces the old secret; revocation stops future authentication. Removing API access also revokes that account's keys and API access.
Revocation does not recall information already retrieved, cached, copied or shared by a connected tool. Revoke immediately if a key may have leaked and notify the owner through an established internal channel. Do not use another person's key or share an owner key as a substitute for correctly assigned personal access.
09Connected tools and AI services
Connecting ChatGPT, Claude, Claude Code, Codex or another tool can send the permitted records to that service or device. A third-party service may process prompts, tool results and generated answers under its own contract, privacy settings and retention rules. An integration does not imply that the company controls the vendor's storage, employees, subprocessors or model behavior. Product names and marks belong to their respective owners and do not imply endorsement.
Use company-approved tools, accounts and data settings. Do not connect a personal or shared organization-wide connector if it would expose company data to unauthorized people. Review the intended audience of chats, shared projects and generated documents. Do not assume that a connector's read-only status prevents someone from copying its results or that all plans provide identical privacy protections.
AI summaries can omit context, miscalculate totals or make unsupported claims. Verify material conclusions against the underlying entries. Generated output is not an independent record of attendance, legal compliance, approved compensation, an invoice or an employment decision.
10Accuracy and corrections
Log hours honestly and promptly, using the appropriate client, scope, dates and timezone. Do not fabricate entries, misattribute work, conceal time actually worked or enter misleading descriptions. Follow the company's approved correction process when a record is incomplete or inaccurate. Reporting queries do not themselves change source records.
Approval status reflects the workflow recorded in the system; it is not a legal determination that time is or is not payable. Nothing here permits withholding legally required pay because an entry is late, unapproved, disputed or unavailable. Report discrepancies through the appropriate internal channel, without limiting any right to contact a regulator or obtain advice.
11Confidentiality and appropriate content
Limit entries to relevant work information. Do not include passwords, API secrets, bank details, private medical information, unrelated personal communications or confidential third-party material that you lack authority to disclose. Avoid adding client pricing or sensitive payment details to work descriptions, because those descriptions may be included in time reports even when structured financial fields are excluded.
Recipients should use the minimum information necessary for the authorized purpose, secure downloaded files and avoid onward sharing beyond the permitted audience. Confidentiality obligations remain subject to applicable law and the protected-rights section below; they are not a ban on lawful discussion of wages, hours or working conditions.
12Security and service providers
The company uses access controls and other reasonable safeguards intended to protect records. Reporting controls include scoped permissions, hashed bearer secrets, bounded queries, rate limits and encrypted private key metadata when durable storage is configured. Access checks are repeated on requests. Security measures reduce risk; they do not make any system or third-party integration immune to compromise, misuse or error.
Authorized hosting, storage, identity and other service providers may process information needed to operate the workspace under applicable arrangements. Reporting request logs are designed to record operational metadata such as request identifiers, routes, status and duration rather than response bodies or raw keys. Other workspace audit and security records may identify authorized actions. The company should not promise a security or retention configuration that has not actually been implemented.
13Retention, exports and deletion
The company may retain work records for operational, contractual, payroll, audit, dispute-resolution and legal-recordkeeping purposes. Retention must follow applicable law and the company's adopted schedule; this draft does not establish a universal deletion deadline. Account closure or integration revocation does not automatically delete historical time records, audit records, required backups or copies already lawfully distributed.
Ask the owner about access, correction, export or deletion through the company's established internal channel. Requests are subject to identity checks, applicable rights, confidentiality obligations and legally required retention. Do not delete or alter records subject to a preservation obligation. Copies in an external AI tool or downloaded file may require separate action in that service.
14Availability and technical limits
The company may maintain, change or suspend features for security, reliability or operational reasons. No uninterrupted availability, fixed response time or permanent feature set is promised. Each reporting request covers at most 93 days and returns a bounded page; other documented volume and rate limits apply. All-time key access does not mean an unlimited single query.
Reports reflect data and permissions when queried and are not guaranteed frozen snapshots. Timezone changes, daylight saving transitions, corrections and concurrent updates can affect comparisons. Follow the documented pagination and retry behavior. Maintain any separate records required by your role or applicable law rather than relying exclusively on an AI conversation.
15Incident response and suspension
Report suspected unauthorized access, a lost key, accidental disclosure or a material data error promptly through a trusted internal channel. Revoke affected keys where possible, preserve relevant evidence, and avoid redistributing sensitive material while seeking help. The company may temporarily limit access while investigating and take reasonable steps to contain an incident.
The company remains responsible for any incident assessment, notification, preservation or cooperation duties that apply by law or contract. This policy does not promise that revocation will erase prior disclosures or that every incident can be prevented. It does not require permission to make a protected report to a government body or legal adviser.
16Disclaimers and limits of liability
To the extent permitted by applicable law, the workspace and reporting integrations are provided as available, without a promise that they will be error-free, continuously available or suitable for every external workflow. The company does not warrant the accuracy or availability of third-party AI answers, external services or user-entered descriptions. Users must exercise reasonable care when selecting tools and sharing results.
To the extent permitted by applicable law and consistent with controlling written agreements, the company excludes liability for indirect, consequential, special or incidental losses arising from service interruption, unauthorized onward sharing or reliance on third-party output. This is not a blanket release from liability. It does not exclude obligations or remedies that cannot lawfully be excluded, responsibility for fraud or willful misconduct, or liability for gross negligence where a limitation is prohibited.
Nothing here limits rights to earned compensation, statutory employment protections, mandatory privacy or data-security remedies, legally required recordkeeping, or any non-waivable right. No arbitrary monetary liability cap, employee indemnity, forced arbitration or waiver of class or collective rights is introduced by this draft. The enforceability of any limitation depends on the applicable jurisdiction and facts.
17Protected rights and controlling obligations
Nothing in these terms prohibits lawful discussion of wages, hours or working conditions; protected concerted activity; communicating with a union; reporting suspected violations; cooperating with a regulator; whistleblowing; obtaining legal advice; or exercising applicable access, correction, deletion or other statutory rights. Where such rights apply, no prior company authorization is required and retaliation is prohibited by applicable law.
Mandatory law and controlling employment, contractor, client, collective bargaining and data-protection agreements take precedence over conflicting language here. These terms do not determine worker classification, waive minimum-wage or overtime rights, or expand company ownership beyond what the law and applicable agreements allow. If a provision cannot be enforced, it should be applied only to the lawful extent without cancelling other valid provisions.
18Changes and questions
Material policy changes should be communicated before they are relied upon, with additional acknowledgment or consultation where required. Publishing a link does not by itself prove that a person accepted a contract. Any future acceptance workflow must identify the version presented and use a suitable record of notice or acknowledgment; none is implemented by this draft page.
Contact the workspace owner through your established company channel for questions about reporting visibility, corrections, approved tools or this policy. Do not send secrets or unnecessary personal information with a support request. The policy's legal entity, governing law, formal privacy contact and retention schedule must be confirmed before this draft is adopted.