Who we are
AskFendy is a fencing season planning service for parents, guardians and adult users. This policy covers askfendy.io and the private beta at demo.askfendy.io. “AskFendy”, “we” and “us” refer to the operator of this service.
For privacy questions or requests, contact rudi@cxbunnies.com.
Information we handle
The information involved depends on the features you use:
- Sign-in details. Google sign-in provides identity information such as your email address and basic profile details. We use this to authenticate you and control access to the private beta. AskFendy does not receive your Google password.
- Planning information. Your workspace may contain fencer names, dates of birth, schools, calendars, travel plans, competition details, results, notes and opponent records that you enter or import.
- Documents and AI settings. If you use AI features, the app processes your chosen document or screenshot, your selected model, and the API key you provide.
- Technical information. Our hosting and authentication services process connection information, which can include IP addresses, request timestamps, browser information and security or error logs.
- Correspondence. If you request beta access or contact us, we receive the information you send by email.
Where your information lives
In the current beta, your planning workspace and saved AI settings are stored in your browser’s local storage. They are not automatically synchronised to an AskFendy account database. Local storage remains until you remove it, clear site data or your browser removes it. Different browsers, devices and site domains have separate storage.
Files you select for document import are read in your browser. Text extracted from a PDF or Markdown file can be sent for AI analysis as described below. We do not upload the original PDF or Markdown file to an AskFendy document library. Proposed changes and their evidence snippets can remain in your browser as part of your workspace.
Planning exports are files saved to your device and exclude the AI settings and keys saved through Settings. Keep exported files private and export before clearing browser data if you want to retain your plans.
When you choose AI
You choose OpenRouter or Ollama Cloud, enter your own key, and select a model in Settings. No document analysis runs simply because you save these settings. Loading the model list requests the provider’s catalogue; it does not submit a document or check that your key is valid.
When you import a PDF or Markdown document, AskFendy sends up to the first 60,000 extracted characters, the filename, and basic details from your competition catalogue to the selected provider. Basic catalogue details include event IDs, names, locations and dates so the model can identify new events and updates.
If you import a results screenshot, the image and roster names are sent to your selected provider to match results. Choose only material you have permission to share and avoid unnecessary information about children or other people.
OpenRouter requests go from your browser to OpenRouter, which routes them to the model provider. Ollama Cloud requests pass through AskFendy’s authenticated server to Ollama. The server forwards your key for that request; the forwarding configuration does not store keys or request bodies. Your saved key remains in your browser and is readable by someone with access to your browser profile.
AI providers process submissions under their own terms and privacy practices, including retention, model routing and any training preferences. Review OpenRouter’s Privacy Policy and Ollama’s Privacy Policy before use. Ollama Cloud runs remotely. A JSON proposal import does not require an AI request.
How we use and share information
We handle information to provide the workspace, authenticate authorised users, process the AI requests you initiate, respond to support enquiries, and protect the service from misuse. We do not sell your personal information or use your planning data for targeted advertising.
Service providers may process the information needed to provide hosting, authentication, email and optional AI features. The current beta uses Hostinger for hosting and Google for sign-in. These providers may operate in countries other than yours. We may also disclose information where required by law or necessary to address a security issue or protect legal rights.
Google sign-in is used for authentication. We do not request access to your Gmail messages, Google Drive files or Google Calendar. We do not send Google access tokens to AI providers. Our use of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements.
Information about young fencers
The service is intended to be used by adults managing fencing plans, including parents and guardians. It is not intended for children to create and manage their own accounts.
Only enter information about a child when you are authorised to do so. Keep details proportionate to planning needs, and review documents before submitting them to AI providers. If you believe a child has supplied personal information to us without appropriate authorisation, please contact us.
Your choices and requests
You can edit your planning information in the app and use Settings to export a copy. To erase the stored workspace and saved keys from a device, clear site data for demo.askfendy.io (and any other AskFendy domain you have used) in that browser. “Reset data” restores the demo’s starting data; it is not the same as deleting all site data.
To remove an AI key only, open Settings, select the provider, choose “Clear key”, then save. Repeat for each provider you configured. To revoke a key completely, use that provider’s account settings. You can also remove AskFendy’s Google access through your Google Account’s third-party connections settings.
Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability or to object to certain processing, and to raise a concern with a data protection authority. Contact rudi@cxbunnies.com for help or to request removal of beta access. We may need to verify your identity. We cannot remotely erase files or local storage on your device.
Retention and security
Browser data remains under your device’s storage controls. We retain support correspondence and operational records only as needed for their purpose, security and legal obligations. Provider retention practices apply to information submitted to external services; clearing your browser does not erase a provider’s records.
We use HTTPS and authenticated access to the beta. No service or device is completely secure. Use a trusted device, keep software updated and protect both your Google account and provider keys.
Changes to this policy
We may update this policy as the service develops. The updated date will appear here. If a change materially affects how we handle personal information, we will provide an appropriate notice. For questions about the current policy, email rudi@cxbunnies.com.
A question about your privacy?
Reach out to AskFendy. We’re here to help.
rudi@cxbunnies.com