Privacy Policy

1. Scope and operator

This Privacy Policy applies to Profitly websites, workflow automations, integrations, connected-account utilities, support, and related services operated by Michael Gulfan under the Profitly brand.

Project-specific instructions, contracts, or notices may provide additional detail. If they conflict with this policy, the more specific disclosure applies to that project. Profitly services are not directed to children.

2. Information we process

The information processed depends on the service requested and the systems a user authorizes. It may include:

• Contact and account information: name, email address, organization, authorized account identifier, and limited profile information.
• Workflow and business information: form submissions, lead or customer records, task details, status, ownership, reports, and other records intentionally connected to an automation.
• Connected-service content: messages, files, attachments, headers, dates, folders, or metadata that a user expressly authorizes Profitly to process for a requested migration, routing, reporting, or integration function.
• Operational information: workflow names, execution identifiers, timestamps, completion status, error details, audit records, recovery checkpoints, and technical logs.
• Website information: ordinary server and security logs such as browser type, requested page, approximate request time, and network information where collected by the hosting provider.

Profitly does not intentionally collect payment-card details, government identifiers, health records, or passwords through this website. Credentials and access tokens should never be sent through ordinary email.

3. How information is used

• Provide, configure, test, monitor, and maintain the requested automation or integration.
• Authenticate services selected and authorized by the user.
• Move, validate, route, transform, synchronize, or report information according to the approved workflow.
• Retry temporary failures, diagnose errors, recover missed work, and maintain execution integrity.
• Provide support, document the system, respond to requests, and communicate material service or security information.
• Protect users, connected services, and Profitly against misuse, fraud, or security threats.
• Meet legal, regulatory, contractual, and recordkeeping obligations.

4. Service providers and disclosure

Profitly does not sell or rent personal information, share it with data brokers, or transfer connected-account content for advertising. Information is disclosed only where needed to provide the requested service, protect users or systems, comply with law, complete a user-authorized transaction, or follow the user's instructions.

Depending on the project, processing may involve cloud hosting, automation platforms, communication services, project-management tools, customer systems, and other providers selected or approved for the workflow. Each provider handles information under its own terms and privacy practices.

5. Google API data and Limited Use

When a user authorizes a Profitly service to access Google account or Google Workspace API data, Profitly accesses only the permissions and information needed for the visible, user-requested function. This may include an authorized account identifier, limited profile information, messages, files, attachments, metadata, or records expressly selected for the connected workflow.

Profitly's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

• Google user data is used only to provide or improve the user-facing function that requested access.
• Google user data is not used for advertising, retargeting, credit decisions, lending, data brokerage, or training a general-purpose artificial intelligence or machine learning model.
• Human access is not permitted unless the user gives explicit consent for support, access is required for security or abuse investigation, the data is aggregated and anonymized for permitted internal operations, or access is required by law.

6. Storage, retention, and deletion

Information may be processed in the connected services and workflow infrastructure used for the project. Execution records can temporarily contain payloads, metadata, or error details needed for delivery, troubleshooting, audit, and recovery.

Information is retained only for as long as reasonably necessary to provide the requested service, recover failures, maintain security, resolve support requests, enforce agreements, or meet legal obligations. Access is restricted to authorized people responsible for the service. Information that is no longer required is deleted or anonymized.

A user may request deletion of retained Profitly execution or support data by emailing michael@profitly.tech. Identity or account authorization may be verified before completing a request to protect connected data.

7. Security

Profitly uses reasonable administrative and technical safeguards appropriate to the service, including access controls, encrypted connections, restricted credentials, monitoring, and failure logging. No system can guarantee absolute security.

If a security incident materially affects personal information, affected users and relevant authorities will be notified where required by applicable law.

8. Your controls and choices

• Ask Profitly to stop or disable an active workflow under your control.
• Revoke connected-account access through the relevant provider's security settings.
• Request access to, correction of, or deletion of retained Profitly data, subject to identity verification and applicable law.
• Manage information already delivered to a destination service using that service's own controls.

Revoking access stops future authorized API activity. It may not automatically remove information already delivered to a connected destination at the user's request.

9. Changes to this policy

This policy may be updated when Profitly services, data practices, or applicable requirements change. Material changes to how connected-account data is used will be disclosed and, where required, presented for renewed user consent before the new use begins.