Privacy at Simpho

Simpho is an early-access advertising reporting product. Sign-in creates or opens the workspace associated with your verified Google identity. Available advertising connections are shown inside the application. This policy explains how we handle contact requests and data from authorized users and their connected advertising accounts.

Operator: Naftaly Cohen, sole proprietor, trading as Simpho. Privacy contact: admin@simpho.ai.

Information and purposes

Contact requests. When you email us, we receive your email address, message and information you choose to include. We use them to answer your request, provide support and handle privacy requests. Do not send passwords, access tokens, keys or verification codes.

Identity and sign-in. Where sign-in is available to an authorized user, the identity provider's user identifier, email address and session information are needed to identify the user, restrict access and associate activity with the appropriate workspace. Sign-in uses server-managed sessions and cookies necessary to maintain that session.

Advertising connections. In authorized early access, connections use permission given on Google's or Meta's consent screen and the user's selection of an account they may access. Reporting data includes account identifiers, currency and time zone, names and identifiers of campaigns and advertising entities, status, budgets, spend and reported results. We access and store this data to display and refresh reports for the selected accounts. We also process connection authorization information, including access tokens and, where continued access is enabled, refresh tokens, to maintain the connection the user authorized.

LinkedIn advertising connections. We request read access to advertising accounts and reporting (r_ads and r_ads_reporting). LinkedIn receives its own authorization credentials, account identifiers and query parameters to provide the reports requested. LinkedIn data is stored on Render and restricted to the connected Simpho workspace, using the session, encryption and access controls described below. We do not send Google data to LinkedIn or use LinkedIn authorization to identify your Simpho workspace.

Initial reporting is not intended to retrieve contact details of people who submitted lead forms. Campaign names and support messages may contain personal information; avoid including unnecessary personal details. Aggregate metrics do not mean all information in the service is anonymous.

Technical information. Hosting services may process request information and technical logs needed to operate and secure the website and diagnose faults. Such information is used for those purposes, in accordance with the purposes described here.

Authorization and use limits

We use Google Ads data for reporting. The Google Ads permission can allow operations beyond reading, but the current Google integration reads account and reporting data and does not change Google campaigns or budgets. Entering a planning budget in Simpho is not an instruction to change a budget on an advertising platform.

Ask Simpho currently provides bounded summaries calculated by our server from reports in your selected client and period. It does not send campaign data to an external AI model. Any future external AI processing requires an updated explanation and relevant permissions before activation.

Simpho's use and transfer of information obtained through Google APIs comply with the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising targeting, or use it to train AI models.

Sharing, transfers and access to Google user data

We disclose Google user data only as described below, for the service and purposes explained in this policy:

• Render, our hosting and database provider: our application processes Google sign-in identifiers, connected-account metadata, advertising reports and authorization information on Render infrastructure. Stored authorization credentials are encrypted as described below. Render processes this information to host, store and operate the service.
• Google: authorization credentials and the account identifiers and query parameters needed for a request are sent to Google's authorization and Google Ads API services to authenticate the connection and retrieve the reports you request.
• Google Workspace, our email provider: if you include Google-related information in a support or privacy email, that information is processed in our support mailbox. We do not routinely send advertising reports or authorization tokens by email. Do not include passwords, tokens or unnecessary campaign data in a support request.
• Authorized users and support: reports are available through the authenticated Simpho workspace to which the connected account belongs. We do not disclose them to users of other workspaces. Our operator may access support correspondence to handle a request. Human access to specific Google user data for support requires your explicit agreement to that access; exceptions are limited to access necessary for security or compliance with applicable law.
• Legal requirements: we may disclose information when required by applicable law, limited to the information required for that purpose.

We do not share Google user data with Meta, advertising networks, data brokers or AI model providers. Meta supplies information for a separate Meta connection; it does not receive Google reporting data from Simpho. Infrastructure and email providers process information for their respective service roles, not for Simpho to sell or target advertising with that data.

Protection of sensitive data

The hosted service uses HTTPS to protect data in transit between your browser and Simpho and between Simpho and Google's APIs. OAuth access and refresh tokens that Simpho retains are encrypted with AES-256-GCM. Encryption keys and application secrets are held in server-side configuration, separately from encrypted credential records, and are not included in the browser application or public site.

Access to reports requires an authenticated server-managed session. Server and database access checks bind data to the authorized workspace and connected account. Session cookies use Secure and HttpOnly flags, and changes initiated through the application are checked for cross-site request forgery. The application avoids logging raw OAuth tokens and provider response payloads; diagnostic errors use bounded error codes. These controls reduce the risk of unauthorized access, but no service can guarantee absolute security.

Retention, disconnecting and deletion

Contact information is retained to address the request and necessary follow-up. Continued retention is assessed according to operational need, deletion requests and any applicable retention obligation. This policy does not promise permanent storage of correspondence or reports.

Data collected through time-limited early access is also subject to the access limits and deletion dates established for that access. This policy does not extend an earlier deletion commitment. The public service's retention policy will be published and aligned with its implementation before public data connections open.

Disconnecting, revoking access at Google or Meta, and deleting previously stored information are separate steps. Revoking provider access does not guarantee that information stored in Simpho has been deleted. Deletion requests are handled manually; automatic deletion from every system or backup is not currently promised. Limited records may need to remain for security, documenting a request or preventing deleted data from being restored. We will assess that need and explain relevant limitations for the request.

Requests and updates

For questions, correction, disconnection or deletion requests, contact admin@simpho.ai. Before acting on protected information, we will check that the requester is authorized. We will communicate the request's status, the scope of completed actions and any limitations or further steps. See the deletion-request instructions.

We will update this policy as the product and data handling change. Updating this page does not itself expand an authorization you granted on an advertising platform.