Privacy

Who processes the data

The controller of the personal data processed by OKF Index is WRP Consultoria e Informática Ltda (Brazilian company registry CNPJ 66.300.125/0001-45), at R. Copaíba, Lote 01, Bloco B, Sala 408, Águas Claras, Brasília/DF, CEP 71919-540, Brazil, which also runs the other products listed in the footer. The channel for personal data matters is eu@wendelmaques.com; requests are answered by e-mail.

What this product keeps

• We store submitted domain names, bundle URLs and key-file locations to check publication rights and queue collection. Listed bundle metadata and source links are public.
• PDF, DOCX and DOC conversion sends your file to our shared document service. PDF uses Mistral OCR and automated OpenAI review. DOC and DOCX use native extraction without visual review. Conversion stores the original, extracted text, images, quote and authorization.
• Files uploaded to your own bases start private. We store the original text, search index, filename, hash, upload date and account ownership. Publication exposes the selected base's current files, declared author, source and terms. It does not expose your account email.
• Favorites store bundle IDs and the date saved in your personal account. Your collection is private. Remove a saved item with its heart button.
• Connected sources store their public URL, content hash and check times. Source URLs stay with imported files after disconnection and appear in their OKF export. Source checks do not use your account credentials.
• Collections store a name and base references in your personal account. They start private. Publishing a collection exposes only selected references to public bases. It does not copy their files or expose private references.
• Team sharing stores the organization ID on the base or collection. Current members can read, search and download shared files. Account manages membership. The owner remains the only editor.
• Following stores base IDs and follow dates in your personal account. It uses current public versions without copying files. Unfollow removes the reference and its notices.
• Base activity stores daily totals for searches, searches with no results and document reads. It stores no query text or visitor identity. Only the base owner can read the 30-day report.
• Ask with sources sends your question and up to five excerpts from your base to Anthropic through our AI service. We store the question, source versions, excerpts, answer and purchase for retrieval and billing. Answers are private to the owner and are not published with the base.
• Dataset descriptions store fields, coverage, format, declared update frequency, license and source URL. They follow the base's draft and publication controls. We do not import the source data or verify its license.
• Account: e-mail, password, passkeys, sign-in codes and sessions are kept by the account system shared by our products, in its own database — this product keeps only the account id next to what is yours. Without an account, a signed guest token stored in your browser owns what you create; signing in moves it to your account.
• Pay-per-call payments (x402) settle on the Base network, which is public by design; here we keep the transaction reference and the amount for reconciliation and accounting.
• Prepaid credit: the token is stored only as a SHA-256 hash with its balance and movements; whoever holds the token holds the credit, and it cannot be recovered by e-mail.
• Contact: the name, email, message, WhatsApp number and audio you choose to send go through our own mail server to the controller's mailbox. The message includes the source page, language and network (IP) address. We use this data to answer your request.
• Audio recording is optional and requires your microphone permission. You can listen and delete it before sending. Audio stays in your browser until submission, then goes as an attachment without transcription. Contact does not subscribe you to marketing lists.

Sign in with Google

• When you choose Sign in with Google, you allow access to your Google account identifier, verified email and basic profile. The profile can include your name, given name, family name, photo, language and Google Workspace organisation domain.
• We use this data to identify your account, give you access and display your profile. We store the link and profile fields in the account system. Google confirms your identity. We do not receive your Google password.
• Sign-in requests only openid, email and profile. It does not give access to Gmail, Drive, Calendar, contacts or Search Console. Additional integrations request their own permission when you choose to connect them.
• Sign-in tokens are used on the server to check your identity. We do not keep access or refresh tokens from this sign-in to query other Google services.
• We do not sell data received from Google. We do not use it for personalised advertising or to train general artificial intelligence models. Internal access is limited to service operation, authorised support, security and legal obligations.
• We keep the link and profile while needed for your account. Unlinking Google prevents new access through that link. It does not delete your account, the imported profile, product data or required security and billing records.
• You can remove the connection in your Google Account settings at https://myaccount.google.com/connections. To request access, correction or deletion of data we keep, write to eu@wendelmaques.com. Include the product and account email. Do not send a password or token.
• Our use and transfer of information received from Google APIs follow the Google API Services User Data Policy, including its Limited Use requirements where applicable: https://developers.google.com/terms/api-services-user-data-policy.

Sharing Google user data

• These disclosures cover the Google account data and any Google integration data described in this policy. They also cover raw responses, summaries and aggregated or derived data.
• WRP processes this data to provide the features you request. Our hosting and storage providers supply the servers we operate. They process stored data to provide that infrastructure. Authorised operators can access data when needed for service operation, security or support you request.
• Google receives the requests and credentials needed to confirm your identity or read a service you connect. Amazon Web Services Simple Email Service (SES) receives your email address and message contents to deliver account messages and enabled alerts. The integration sections describe any Google metrics included in alerts.
• For a purchase you request, the payment providers identified in this policy can receive the name and email used for billing, including those imported at sign-in. They do not receive your Google access tokens, refresh tokens or imported performance reports.
• We do not sell Google user data or disclose it to data brokers or advertisers. We do not use it for advertising, credit decisions or AI model training. We do not send Google API responses, imported performance reports or tokens to AI providers.
• We disclose data to authorities only when required by applicable law. We limit such disclosure to what is required. Hosting and email providers can process data outside your country. Their role is to supply the services described here.

Protecting Google user data

• HTTPS encrypts data between your browser and our service, and between our service and Google's APIs. This includes Google sign-in, permission requests and imported reports.
• The server checks your session and permission before it returns private data. Account and product identifiers restrict access to the records you are allowed to use. Private responses are not stored in shared public caches.
• For optional Google integrations, access and refresh tokens are encrypted before storage with AES-256-GCM. The encryption binds each token to its product, account and Google service. Server configuration holds the encryption keys separately from the encrypted records.
• Google tokens stay on the server. They are not included in browser storage, public reports or AI requests. Sign-in sessions use Secure and HttpOnly cookies. State validation, short expiry and single-use callbacks protect the Google authorization flow.
• Stored profile fields and report metrics are protected by server access controls and account checks. You can revoke Google access and request deletion as described in this policy.

For how long

• Published metadata remains while listed. Removal and correction requests are handled by email.
• Remove file deletes the document from your base, search, downloads and public access. Replacement keeps the current and last published versions until you publish again.
• Make private stops new public reads and removes the base from discovery. It cannot recall copies that visitors already downloaded.
• Deleting a collection removes its references and public page. The original bases and files remain with their owners.
• Stopping team sharing or revoking membership blocks new team reads. It cannot recall files already downloaded. Sharing a collection includes current and future files in its owner's referenced bases.
• Sign-in codes expire within minutes; the account session ends when you sign out or when it expires.
• Per-network rate-limit counters (guest, contact, sign-in code) expire on their own within minutes or hours.
• Payment and credit records stay as long as accounting requires.
• Visit steps stay 7 days on the product server; the copy kept for analysis, without IP or account, stays on our data server.
• Web server records, with the IP address, are deleted within 15 days.

Infrastructure and third parties

• Servers we operate run the service and store your data. Cloudflare provides DNS only.
• Amazon Web Services (SES) sends the account e-mails, such as the sign-in code, the invitation and the alerts you turned on.
• Interface libraries (Bootstrap) are served from the product's own domain, not from a third-party CDN.
• When configured, our server forwards pages and actions to Google Analytics 4. Your browser does not load the Google library. We do not send typed text, e-mail or account data. Advertising features stay off.
• Coinbase Developer Platform (CDP) verifies and settles x402 payments on the Base network. It receives the wallet address, amount, signed authorization and paid resource URL. The private key is not sent. The wallet address and transaction are public on the network.
• Asaas Gestão Financeira Instituição de Pagamentos S.A. processes payments in Brazilian reais (Pix, boleto and card) and receives the payer's name, CPF or CNPJ and e-mail to issue and check the charge.
• In the product's card forms, card and billing details pass through our API to Asaas. This includes the postal code, address number, phone and buyer's IP address. We do not store the card number or security code.

Cookies and browser storage

• When you sign in, the account session lives in an HttpOnly cookie on this domain; without an account, the guest token stays in your browser and identifies what you created.
• Screen preferences (theme, filters) stay in the browser's local storage and never leave it.
• To improve the path through the product, we measure page views, clicks on controls and purchase steps. We keep a random identifier and the session in your browser. These events contain no typed text, page content, IP, e-mail or account data. Global Privacy Control or "Do Not Track" disables this collection.
• Our Google Analytics integration does not set Google cookies in your browser.
• There is no advertising cookie and no cross-site tracking.

IP address

To limit abuse, the IP address goes into a hash with a secret salt. The approximate country and city come from a geolocation database (MaxMind GeoLite2) on our server. This lookup does not send the address to third parties. Card payments send the IP address to Asaas to validate the payment. The raw IP is not kept in the product's databases: it appears only in the contact e-mail and in the web server records, deleted within 15 days.

Your rights

You can request access, correction or deletion of what exists about you by writing to eu@wendelmaques.com. We answer within the terms of the Brazilian data protection law (LGPD) and, where it applies, the GDPR. Data from public sources (official registries) stays at the source; only the copy here is removed.