Snapshot 41649
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Privacy and data Privacy Policy How GenderAPI collects, uses, protects, shares and retains information connected with our website, products and services. Effective date September 6, 2026 Last updated September 27, 2026 On this page 01Personal Information 02Technical Information 03Browser Cookies 04How We Use Information 05Information Security 06Information Sharing 07Google API Limited Use 08Retention and Deletion 09Analytics 10Policy Changes 11Acceptance 12Contact Related documentsGDPR Privacy InformationCalifornia PrivacyData Processing AgreementSubprocessorsTerms & ConditionsEULADelivery & Returns Policy overview Information practices for GenderAPI users This Privacy Policy governs the manner in which GenderAPI collects, uses, maintains and discloses information collected from users (each, a "User") of the www.genderapi.io website (the "Site"). This Privacy Policy applies to the Site and all products and services offered by GenderAPI. 01 Personal Identification Information We may collect personal identification information from Users in a variety of ways, including when Users visit our Site, place an order, fill out a form, or use activities, services, features or resources available on our Site. Users may be asked for, as appropriate, a name, email address, mailing address, phone number and limited billing information. Complete payment-card credentials are collected and processed by the payment provider rather than stored by GenderAPI. Users may visit our Site anonymously. We collect personal identification information only if Users voluntarily submit it. Users may refuse to supply personal identification information, although this may prevent them from engaging in certain Site-related activities. GenderAPI is intended for business and professional use and is not directed to children. We do not knowingly collect personal information directly from children. If you believe a child has provided personal information to us, contact us so we can review and delete it where required. 02 Non-Personal Identification Information We may collect non-personal identification information whenever Users interact with our Site. This may include browser name, computer type, operating system, Internet service provider and similar technical information about a User’s means of connection to our Site. 03 Web Browser Cookies The following inventory covers first-party cookies, provider cookies and related browser storage used by the GenderAPI website and signed-in application. Strictly necessary items support login, security and privacy choices. Optional measurement items are used only after the applicable consent choice. Name Provider Purpose Duration Category token GenderAPI Stores the signed-in authentication token used to authorize account requests. Up to 60 days, or until logout Strictly necessary genderapi_cookie_consent GenderAPI local storage Remembers whether the User accepted optional measurement or selected necessary storage only. Until deleted or the consent version changes Strictly necessary genderapi_demo_api_key GenderAPI session storage Temporarily remembers an API key entered by the User for an interactive documentation demo. Browser-tab session Strictly necessary when the demo is used _ga Google Analytics Distinguishes browsers for aggregate measurement. Up to 2 years Optional analytics _ga_* Google Analytics Maintains Analytics session state. Up to 2 years Optional analytics _gcl_* and other Google measurement cookies Google Ads / Google Tag Attributes advertising interactions and measures conversions where the relevant feature and consent are enabled. According to the enabled Google measurement configuration Optional measurement __cf_bm Cloudflare Bot detection and protection, when enabled. 30 minutes after inactivity Strictly necessary cf_clearance Cloudflare Remembers successful security-challenge completion, when a challenge is issued. Configured challenge-passage period Strictly necessary _cfuvid and other conditional Cloudflare security cookies Cloudflare Rate limiting, traffic routing or service availability when the corresponding Cloudflare feature is enabled. Session or feature-configured period Strictly necessary Chatra support storage Chatra Maintains the live-support widget session and conversation continuity when Chatra is used. According to Chatra’s active configuration Support functionality Browser limits or provider settings may shorten these maximum periods. Cloudflare and Chatra items are conditional and appear only when the relevant security or support feature is used. SendGrid, Gmail, iyzico, Binance and DigitalOcean do not require GenderAPI to place a provider-specific browser cookie merely because their backend services are used. Users may change optional measurement consent through “Cookie preferences” in the footer. They may also delete cookies or browser storage through browser settings. Blocking strictly necessary storage can prevent login, security checks, saved privacy choices or other requested functionality from working. 04 How We Use Collected Information GenderAPI may collect and use Users’ personal information for the following purposes: Customer service: to respond to support requests and needs. Transactional and support emails: to send registration, verification, password-recovery, order and service messages, and to respond to inquiries. GenderAPI does not use SendGrid or Gmail for email marketing. Personalization: to understand in aggregate how Users use Site services and resources. Site improvement: to use feedback to improve products and services. 05 How We Protect Your Information We adopt appropriate data collection, storage and processing practices and security measures to protect against unauthorized access, alteration, disclosure or destruction of personal information, usernames, passwords, transaction information and data stored on our Site. Sensitive and private data exchanged between the Site and its Users uses an SSL-secured communication channel and is encrypted and protected with digital signatures. 06 Information Disclosures and Service Providers GenderAPI does not sell or rent personal information. Query inputs, uploaded-file contents and connected spreadsheet data are not disclosed for advertising or for another company’s independent use. They may be processed within the contracted hosting and network infrastructure needed to transmit, secure and operate the Service. Automated inference, including AI-assisted processing where offered, runs on a private GenderAPI-operated AI server; query inputs are not sent to a third-party AI provider, used to train the model or retained in AI logs. We use the following providers for the stated purposes: Cloudflare: network delivery and security; IP addresses, request headers and security or network telemetry. DigitalOcean: primary application, database and file-processing infrastructure in the United States; account data, queries, technical logs and Excel, CSV, Google Sheets or Microsoft Excel data while a requested operation is performed. iyzico: card-payment processing; customer, order, transaction, device and payment information. GenderAPI does not store complete payment-card credentials. Binance: cryptocurrency payment and transaction verification; relevant transaction identifiers, amount, currency and wallet or account information. Twilio SendGrid: transactional account emails such as registration, verification and password recovery. It is not used by GenderAPI for email marketing. Google Workspace/Gmail and Chatra: manual customer support; contact details, message content, attachments and technical metadata supplied through the relevant channel. Google Analytics, Google Tag Manager and Google Ads: consent-based site measurement, tag delivery and conversion measurement. These providers receive only the information needed for the relevant function and act under their applicable contractual and data-protection terms. They may use subprocessors where permitted by those terms. Customers that submit personal data for processing can review our Data Processing Agreement and current Subprocessors register. We may also disclose information when required by applicable law, a valid legal process, or when reasonably necessary to protect the rights, security and integrity of Users, GenderAPI or the public. These limited disclosures do not change the query and uploaded-data rules above. 07 Google API Limited Use Policy GenderAPI.io’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. 08 Data Retention and Deletion The periods below are maximum standard retention periods. Information is deleted or irreversibly anonymized sooner when it is no longer needed. A longer period applies only where required by law, needed to establish or defend legal claims, or necessary to investigate fraud or a security incident. GenderAPI queries Successful name, username, email and other GenderAPI query inputs are processed to return the requested result and are not retained as reusable query records. Automated inference runs on computing infrastructure controlled by GenderAPI and query inputs are not sent to a third-party AI provider. Separate server, authentication and security-event logs follow the retention period stated below. Non-email queries for which no gender result is found may be retained for up to 12 months for the limited purpose of improving GenderAPI, subject to access controls, followed by deletion or irreversible anonymization. Email queries are excluded from this improvement dataset. Applicable access, objection and deletion rights are described in our GDPR privacy information. Excel and CSV uploads The published policy schedules uploaded Excel and CSV files for removal from active systems within five days. After exporting results, the User may request earlier removal from the active workspace. Data removed from active systems may remain in access-restricted rolling backups for up to 15 additional days, as described below. Account information Account information is retained while an account is active. Following account closure or an approved deletion request, information that is not subject to a legal exception is deleted or irreversibly anonymized within 30 days. Billing and transaction records Invoices, transaction records and the limited billing information needed for accounting, tax, chargeback and fraud-prevention obligations may be retained for up to seven years from the transaction date. GenderAPI does not use this period to retain query inputs or uploaded-file contents. Support communications Support requests and related correspondence may be retained for up to 24 months after the request is closed so that we can follow up, maintain service quality and resolve disputes. Security and technical logs Server, authentication and security-event logs may be retained for up to 90 days, unless a specific event requires longer preservation for investigation, legal compliance or the protection of the Service and its Users. Backups Data deleted from active systems may remain in access-restricted rolling backups for up to 15 additional days before automatic overwrite. Backup copies are not restored for ordinary business use and remain subject to the original deletion request if restoration is required for disaster recovery. Google Sheets data We do not store or retain data from Google Sheets. Spreadsheet data is processed in real time solely to generate the requested result; input and output data are discarded after the operation and are not saved or logged on our servers. 09 Analytics and Consent Necessary storage may be used to operate the Site and remember privacy choices. Google Analytics, Google Tag Manager and Google Ads conversion measurement are used for site measurement and campaign performance. Optional measurement tags are loaded only after the User has selected “Accept cookies.” Choosing “Necessary only” prevents optional measurement tags from being loaded by this Site. When enabled, these Google services may process limited technical, campaign and Site-use information on GenderAPI’s behalf, such as page interactions, device or browser information, an IP-derived approximate location and purchase-conversion identifiers or values. Advertising storage, advertising user data, ad personalization signals and Google signals are disabled in the Site configuration. GenderAPI query inputs, Excel or CSV file contents, and Google Sheets data are not supplied to these services. For selected English pages, consented first-party measurement connects a visit and registration-link click with a successfully created account and its first successful V2 API request. We keep a category for the referring service, an approved landing-page path, event dates, and pseudonymous identifiers. We do not include API keys, names or email addresses submitted for prediction, account email addresses, full referring URLs, or URL query strings in these records. This is a separate measurement store from API credit accounting. The shared analytics preference and attribution cookie last up to 30 days across www.genderapi.io, app.genderapi.io and api.genderapi.io. Account matching is limited to that attribution window; stored measurement records are removed after at most 90 days. Withdrawing consent removes the matching first-party attribution and its linked events. Cookie loss or blocked measurement may prevent a visit from being matched. This measurement does not establish the identity or gender of a person. Users may change their choice at any time through “Cookie preferences” in the footer. Selecting “Necessary only” disables further analytics collection and removes analytics cookies accessible to the Site. Further information is available in the Google Analytics terms and Google Privacy Policy. 10 Changes to This Privacy Policy GenderAPI may update this Privacy Policy. The “Last updated” date identifies the current version. For a material change, we will provide reasonable notice through the Site, the signed-in service or the account email address, as appropriate to the change. We encourage Users to review this page periodically. 11 Your Acceptance of This Policy By using this Site, you signify your acceptance of this policy. If you do not agree, please do not use our Site. Continued use following the posting of changes will be deemed acceptance of those changes. 12 Contacting Us If you have questions about this Privacy Policy, the practices of this Site, or your dealings with the Site, contact Onur Öztürk, trading as Ozan Soft, at [email protected] or +90 850 305 0427. Data controller · Tax identification number: 7140188422 · Etimesgut Tax Office · Ankara Chamber of Tradesmen registration: 4522 · Tradesmen Registry number: 354342 Şehit Osman Avcı Mah. Kaplan Cad. No:11B/4, Etimesgut, Ankara, Türkiye · ozansoft.com