One1by AgenticShip
ONE1 BY AGENTICSHIP

Privacy

How One1 handles your account, project information and connected Google website data. This notice applies to the One1 application operated by AgenticShip.

Your account and project

One1 stores account and sign-in information, project memberships, and records added by authorized team members, such as customers, leads, tasks and conversation notes. We use them to provide sign-in, project access and the features you use. Session cookies and navigation preferences keep your sign-in, language and selected project working.

Google website connections

Google sign-in can provide your name, email and profile information for your One1 account. It does not authorize website reports. When a project owner or administrator connects a Growth source, One1 separately requests the relevant read-only permission:

  • Google Search Console: accessible property identifiers and permissions, then search clicks, impressions, click-through rate and average position for the linked website.
  • Google Analytics 4: property and web-stream metadata to check the domain, then aggregate sessions, active users and page views filtered to the linked website.

A customer or agency account needs existing Google permissions. Properties are checked on the server and assigned to a particular project and website. Measurements provide that project’s visible Growth reports. These connections do not edit your site, publish content or purchase advertising.

Use and sharing of Google data

Google reports are visible to authorized project members. Connect a source only if you may share its measurements with that project. Another project does not gain access merely because it uses the same Google account.

We do not sell Google API data or use it for advertising targeting or credit decisions. These integrations do not send retrieved Google data to AI providers or use it to train AI models. Additional uses need separate disclosure and authorization.

One1 limits use and transfer of Google API data according to the Google API Services User Data Policy, including its Limited Use requirements.

Facebook and Instagram connection status

Live Meta authorization and reading are not enabled in this release. Operators can register the Facebook Page or linked professional Instagram asset intended for a website, and review clearly labelled synthetic sample profiles. An asset ID, a saved intention or a sign-in does not verify access to a Meta account.

Authorized operators in the same project can see permitted saved profile fields, their source, expiry and request history. The fields are name, category or username, description and website when present. These features do not publish posts, send messages, buy advertising or transfer profile data to an AI model. Future live access requires a separate working authorization flow and applicable Meta permissions.

Meta disconnection and deletion

Disconnect asset stops future use of that local connection. It does not by itself erase all saved provider content, revoke an entire Meta account grant or complete a deletion request. Delete saved profile removes that profile payload while keeping its request identity and receipt hash so a repeated request cannot restore it.

A provider deletion request can be pending after it is saved. It is completed only after the covered provider content has been erased and the covered credentials and bindings revoked. Local and provider account/asset identifiers, authorization versions and scopes, session/request identifiers, timestamps, receipt hashes and audit/accounting records remain. These retained records are separate from erased profile text and encrypted credentials. Completion does not promise immediate erasure of backup copies or unrelated project records.

For additional data access or deletion requests, contact office@agenticship.ai. Do not send passwords, authorization codes or tokens.

Storage and service providers

One1 uses Vercel for application hosting and Neon PostgreSQL for stored application data. Google handles Google authorization and API requests. The configured email service delivers sign-in and account-recovery messages. Providers process information needed to deliver these services and may process it outside your country.

Growth connection tokens are encrypted before storage and used on the server, not returned in reports. Server-side membership checks and database isolation limit project access. Security and audit records support operations and investigations. Authorized personnel may access information for necessary support, security or legal purposes, with your authorization where required.

Disconnecting and retention

For Google connections in Settings → Connections, Disconnect clears the stored token, property binding and latest measurements for that website connection, stopping new reads through it. Connection metadata and audit records may remain. This does not revoke the whole Google grant, which may serve other projects.

You can separately remove account-wide access in your Google account’s connections. This can affect every One1 connection using that Google account and OAuth application.

Project records remain while needed for the service and applicable record-keeping obligations. There is no single promised automatic deletion period for all data. Deletion of additional project data, audit records or backup copies requires a support request and assessment of applicable requirements.

Your questions and requests

Contact office@agenticship.ai for access, correction, deletion or privacy questions. Identify the project; do not email passwords, tokens or sensitive records. We may verify your identity and authority before acting. Material changes to Google data use will be disclosed before requesting any necessary new consent.