Privacidad

GetMyData is operated by Ana Ramos, an individual developer based in Manila, Philippines. Support, billing, privacy and legal enquiries: support@getmydata.io. Submit data requests through your AI Agent using our API, MCP or Skill; email is not an ordering channel.

This policy describes information processed when you visit our website or use the Agent-based data service. The data controller is Ana Ramos, based in Manila, Philippines.

1. Information processed

• Requests and results: sources, requested fields, filters, row counts, descriptions, language, samples, results and associated service records. Results may contain personal data about individuals (for example public profile or contact details) when you request it.
• Email verification: the email supplied for a request and verification metadata. A one-time code is sent to that address. Stored verification records use a keyed digest of the code; the code is not included in application audit logs. Email delivery providers necessarily process the message being sent.
• Order information: agreed scope and quote, explicit discount codes, order and payment status, and checkout information reported by the payment provider. We do not receive your full payment-card number.
• Access and security: session and request authorization records, timestamps, request identifiers, errors, operational metrics and abuse-prevention records. Network addresses may be processed by our hosting provider and represented by a derived identifier for rate limiting.
• Support and preferences: correspondence you send to support, your language preference and any optional analytics consent. Historical signup, consent and service records may remain; new email-based registration and ordering have been removed.

2. Purposes

We use this information to process authorized requests, verify the current order’s email, deliver results, handle payment and support, prevent abuse, troubleshoot failures and meet applicable legal obligations. Where required, processing is based on steps requested before a contract, performance of a contract, legitimate interests in operating and securing the service, consent for optional analytics, or legal obligations. We do not use your requests to train our own AI models.

3. Providers and access

Hosting, storage, security, email delivery, AI processing and data collection providers process the information necessary for their role. An authorized operator may review a request or incident. Payment information is processed by the payment provider identified at checkout under its own terms and privacy policy. We do not sell customer personal information. Providers may process data outside your country; contact support for information about the providers and applicable transfer safeguards.

4. Cookies and optional analytics

The lang cookie remembers your language. Security services may process connection information needed to protect restricted resources. When enabled and only after you agree, Google Analytics measures public-page visits and scroll depth, language selections, and clicks on Agent, Skill, API and pricing links and on copy buttons (only which fixed button was used, never the copied text). The consent choice is retained for up to 180 days and can be changed through Privacy choices.

Analytics does not run on confirmation, payment-return, verification, download, API or administration pages. We do not send email addresses, request contents, OTPs, coupon codes, order identifiers, private credentials, full referring URLs or URL query parameters to analytics. The only exception is campaign tags in the link you followed (utm_source, utm_medium, utm_campaign, utm_content and gclid), which are kept so we can tell which campaign brought a visit; values that look like email addresses or are unusually long are discarded. Advertising features are disabled. Google may process pseudonymous browser and device information; see Google’s Privacy Policy. Declining analytics does not prevent use of the service.

Separately from optional analytics, and without cookies, our server records limited traffic statistics for public pages only (never for confirmation, payment, verification, download, API, MCP or administration pages): the referring website’s domain name (never the full referring address), the campaign tags utm_source, utm_medium and utm_campaign when they are short codes (values containing an @, spaces or control characters are discarded, and utm_term is never recorded), the country derived from the connection, a browser, crawler or AI-agent category with a mobile flag (not the full browser identification), and a daily visitor key. The visitor key is a keyed one-way hash of the network address and browser identification. Its key changes every day and is not stored, so it counts unique visitors per day, cannot be linked across days and does not contain or reveal the network address. These records are kept for the same limited period as ordinary diagnostic logs. The legal basis is our legitimate interest in understanding which channels bring visitors.

5. Security and retention

Access credentials and signed links must be kept private. They are not placed in application logs. Ordinary diagnostic logs use limited metadata and do not contain request or response bodies. Restricted API/MCP audit snapshots retain redacted request and response content for up to 7 days, with access recorded; credentials, verification codes, email addresses and signed links are removed. Large delivery responses reference the retained delivery object and cannot be reconstructed after it expires. Call metadata and snapshot-access records are retained for 30 days. Restricted sample data, field dictionaries and result snapshots are available for 7 days; sample metadata and confirmation references are retained for 30 days. Restricted execution inputs and schema snapshots are retained for up to 30 days. Completed execution event history is retained for 30 days; provider run facts and unresolved expense records remain available as needed for reconciliation and dispute handling. A paid order’s frozen confirmation remains subject to the order-record retention rules below. Expired audit content is blocked from reading immediately and deleted by bounded maintenance passes. Diagnostic records use limited fields; payment-return records do not store arbitrary URL parameters or full referring URLs. Access is restricted and the website uses HTTPS. No method of transmission or storage provides an absolute security guarantee.

Delivered files are retained for 30 days. Renewing an access token does not extend file retention. Request, payment, verification, security and audit records are retained as needed for service operation, dispute handling and applicable legal obligations. Historical payment and audit records are not erased as part of a code rollback. Contact support to request deletion or obtain retention information; legal and security exceptions may apply.

6. Your rights and contact

Depending on applicable law, you may request access, correction, deletion, restriction or a copy of your personal information, object to processing, or withdraw consent. Contact support@getmydata.io. We may need proportionate verification before releasing or changing personal records; an email address alone does not recover an order credential. You may also contact the competent data-protection authority.

7. Personal data in collected results

When you request data that includes individuals (for example public social or professional profiles), you decide the purpose and use of that data and act as its controller; GetMyData collects it on your instructions. You are responsible for having a lawful basis (such as legitimate interests or consent), for any notice owed to the people concerned, and for honouring their rights after delivery. Delivered files are deleted after the retention period above. People whose data appears in results we still hold can send access, correction, deletion or objection requests to support@getmydata.io; we act on records we hold and refer the request to the customer where appropriate.

The service is intended for adults. We publish policy updates here and provide any further notice required by applicable law.

Nothing in this policy excludes rights or remedies that cannot be excluded under applicable law. Contact support@getmydata.io about a dispute or a request to exercise those rights.