AIPrompter Privacy and Personal Data Notice

Version: 2026-10-11.1-web · Effective: 2026-10-11

Controller and contact

AIPrompter is a free prompt-sharing community operated by an individual under the BKTR Apps brand. BKTR Apps is a brand name; the data controller is the individual operating the service. This temporary version does not publish the operator’s actual identity; the controller identification remains incomplete. Contact email: destek@aiprompter.site. Request channels: Use the email registered to your account or in-app support to contact destek@aiprompter.site. Formal KVKK procedure/particulars are assessed separately. No physical request address is represented in this version; the applicable genuine address/request arrangement remains a launch prerequisite. This notice explains how the app uses data. Accepting the terms is not blanket consent to optional processing.

Information collected

Registration involves your email, username, display name and authentication information. Supabase Auth stores a one-way password hash; the operator has no screen for viewing passwords. The authentication provider manages the infrastructure, so the app not storing passwords does not mean no authorized infrastructure access exists. Google sign-in is optional: account identifiers and permitted basic profile information supplied through Google and Supabase are processed. The app does not receive your Google password. Only openid, email and profile identity/basic-profile scopes are requested, without Gmail messages, Drive files or contacts. You do not need to share a Google identity for this sign-in if you do not choose Google login.

We store prompts, descriptions, categories, reviews, ratings, follow/block relationships, favorites, accepted terms versions and timestamps. Biography, avatar and social links are optional. Support requests and reports contain information you submit. The app does not ask for national identity numbers, contacts, precise location, payment cards or health data. Do not include unnecessary personal information, other people's private data, passwords or API keys in content or support messages.

Even without signing in, infrastructure providers may process technical information such as IP addresses, request times, browser/device details and errors. Authentication emails are delivered through İsimtescil / Mailmatik custom SMTP service. The providers and services actually used in production are: Supabase: database, Auth, avatar storage and server functions; Google OAuth: optional basic identity; Firebase Cloud Messaging: optional Android delivery; server setup is complete, physical device receipt remains separately tested; GitHub Pages: public website and technical visit data; Isimtescil/Mailmatik: support and service email; Google Analytics 4: consent-based website analytics only. Mobile analytics, advertising and CAPTCHA are disabled.

Data use by activity

The table does not mean that every basis applies simultaneously to every record. Legitimate interests are not permission for unlimited collection: purpose, necessity and effects on rights are assessed for the activity. A new consent-based activity requires separate information and a withdrawal route.

Purposes and legal grounds

Account/session management, publishing, favorites, following, profile changes, data export and deletion support the service you request. Necessary processing is based on establishing or performing the service relationship. Records needed to investigate reports, prevent abuse and secure the service may be processed for legitimate interests after assessing their effect on your rights. Valid authority requests and applicable legal duties are assessed separately. Records may be restricted where necessary to establish, exercise or defend a legal claim. Where a new optional purpose needs consent, it will be requested separately and can be refused; this notice does not request marketing permission.

The current implementation has no advertising/tracking analytics or feature that transfers prompts for model training. Sharing a prompt does not automatically call an AI provider. Using a copied prompt in another service is subject to that service's practices. Such functionality changes require updated notices and applicable preference controls before activation.

Public information

Username, display name, biography, uploaded avatar/social links, prompts, reviews, ratings and follow relationships are public. Internet users and search engines may view or copy them. Email, password hashes, sessions, favorites, your personal block list, support/report text and terms acceptance records are not public profile information. App access to them is restricted by authorization rules. Removal of copies made by others or search engine caches at the same time cannot be guaranteed.

“anonymous” identifies original starter examples and license-labelled community imports curated by the app. It is an editorial profile that cannot sign in, not a claimed real user. Its content has no fabricated reviews, ratings or followers. You may use a pseudonym, but that does not anonymize infrastructure records.

Recipients and international transfers

Supabase provides database, authentication and avatar storage services. Providers may process data as necessary for their technical functions. When selected, Google sign-in also involves Google's processing. Public content is delivered to visitors. Disclosures to authorities are limited to appropriate requests and applicable duties. Personal information is not sold.

Project region and processing countries: The current Supabase primary database region is Frankfurt, Germany. Provider staff and subprocessors may access data from other countries; Google and GitHub also operate globally. The email provider’s complete subprocessor and location inventory has not yet been verified. The applicable transfer mechanism and how to access its safeguards: This version is a pilot. Supabase’s DPA and transfer FAQ are available at https://supabase.com/legal/customer-resources/data-processing-addendum and https://supabase.com/legal/privacy-resources/data-residency-and-transfers-faq Completion of a mutually signed/notified Turkish standard transfer contract or another applicable KVKK mechanism has not been verified. EU standard clauses are not automatically Turkish transfer contracts. This notice and terms acceptance do not complete missing transfer safeguards; this remains a separate public-launch prerequisite. Selecting a European region does not mean information stays in Türkiye or that all support and subprocessor access occurs in that region. International transfers are not legitimized by a blanket consent clause in the terms. Provider changes require the transfer assessment and this notice to be updated.

Content review and administration

New or edited prompts enter a review queue. New authors and word-filter matches require human approval before publication. Authors with accounts at least seven days old, three distinct manually approved prompts and no rejected or removed prompt in the last thirty days may publish content that passes the filter while review remains pending. Account age, content text and previous moderation records are used for this decision. Titles, descriptions and bodies are checked against a word filter, which may produce false matches or miss violations. Appeals and reports receive human review. Reviews remain absent from the public feed until approved. You can view and edit your own pending or rejected prompts. Authorized operators use multi-factor authentication and access controls to handle reports, content and account restrictions; minimum operation logs are retained. Account deletion does not create an unlimited copy of all account data. A separate restricted evidence hold requires an actual, documented legal reason for a specific record and an expiry date. A 30-day operational waiting period for removed prompts is not presented as a statutory requirement. Retaining destruction-operation records for at least three years does not mean retaining all user data for three years. Provider and backup lifecycles require separate explanation below.

Retention, deletion and device storage

Profiles and content are retained as needed for the account and relevant functions. You can manage your content, download account data and delete your account. After reauthentication, deletion removes avatars, then the account and linked profile, prompts, reviews, favorites, follow/block relationships and support/report/acceptance records from the primary system. Review and retention schedules for individual records and reports: Active accounts and associated content are retained while needed for the service. Deletion restricts access; failed Storage/Auth erasure is queued for retry. Removed content has a 30-day operational cleanup period, not a claimed statutory requirement. Specific evidence requires a real reason and expiry; the one-year code ceiling is not a general retention entitlement. Minimal destruction records excluding content and passwords are retained for at least three years. Provider log periods are not yet confirmed. Support retention must be limited to the request purpose and required legal period. Daily cleanup of abuse-rate records must be configured and monitored.

Provider logs and backups may have different lifecycles from the primary database. Backup retention and deletion arrangements: A single encrypted d1 database-and-avatar snapshot is scheduled at 06:10 daily on the operator’s Mac. An unavailable Mac cannot guarantee an on-time backup; the operating system may coalesce missed runs on wake. The previous d1 snapshot is replaced only after a successful backup; failure preserves the last completed snapshot. A separate-location recovery copy is not configured. Accepted deletion requests must be reapplied before restored data is served. Provider log and backup lifecycles are separate from this local copy. If a record must legally be retained, its grounds, scope and duration are determined separately; the app does not create an unlimited archive merely for possible future needs. Previously accepted deletion requests must be reapplied after a backup restore.

The app caches public startup copy and catalog information on your device. Mobile sessions use secure device storage; web sessions use tab session storage. These stores are not used for advertising tracking. Signing out clears the local session; it should not be assumed to terminate all sessions on every device. Sign out on shared devices. Clearing local device/browser information does not delete your server account.

The administration website is separate from ordinary mobile sessions. Authorised operators use Google sign-in and an authenticator check. Access/refresh sessions remain in page memory; a PKCE verifier survives the redirect in tab storage for at most ten minutes and is removed on return. This is not advertising tracking.

Security and rights

Controls include HTTPS, per-user database policies, server-side authorization, write limits and separated keys. Server administration keys are not embedded in the app. These controls reduce risk; no absolute security promise is made. Report suspected unauthorized access or data incidents to the contact email.

Under Türkiye's personal data law, you can request information on processing, purposes and recipients, correction of inaccurate data, deletion/destruction where conditions apply, communication of relevant changes to recipients, objection to adverse outcomes from automated evaluation, and compensation where applicable. Requests are assessed after proportionate identity verification. KVKK requests are answered within 30 days, subject to statutory fee and complaint rules.

Where GDPR applies to the activity, rights of access, correction, erasure, restriction, objection, applicable portability and complaint to a supervisory authority are also assessed. Requests are generally answered within one month; any permitted extension is explained. The app is not designed to make solely automated decisions producing legal or similarly significant effects. Rights are not unlimited; any refusal is explained with its grounds.

Handling requests, correction and objections

Requests are narrowed to the relevant account/record, requested action and reply channel. Proportionate checks, such as control of the account email or an existing session, are used; an identity-card photograph is not requested routinely. Clarification may be requested if the scope is unclear. Reasons and applicable complaint routes are explained for a refusal or partial response. Mandatory procedures and deadlines remain applicable. Withdrawal of consent does not automatically invalidate lawful processing that preceded withdrawal; refusing marketing permission does not remove access to the service.

Content ranking uses catalogue criteria such as category, date, approved ratings and review counts. It is not used to decide eligibility for employment, lending or similar matters with legal or significant effects. Where an incident meets applicable legal conditions, the competent authority and affected individuals are notified under the required procedures.

Changes

Material changes are published with a new version and date. Changing this text alone does not authorize a new purpose or a processing activity requiring consent. The published notice must reflect the providers and functionality actually in use.

Age and children

The service is a general-audience prompt-sharing community and does not specifically target children. We do not collect age, date of birth or identity documents at registration and do not impose an 18+ rule. Where local law requires a parent/legal representative’s permission for the service contract or a particular processing activity, that permission must be obtained. A reported child account lacking required permission is restricted while proportionate representative verification and assessment take place. Child-data or safety concerns can be reported to destek@aiprompter.site. A completed verifiable parental-consent system is not claimed

Current notice and version history

The current notice is available at https://aiprompter.site/en/privacy/ The app links to this page and records the accepted terms version on the server. Previous versions remain available in the dated archive. Material changes are brought to users’ attention in the app and require renewed acceptance where appropriate. The privacy notice does not constitute marketing or international-transfer consent.

Account restrictions and prevention of ban evasion

Restricted accounts may sign in and use features such as following and favorites, but cannot submit or edit prompts, comments or ratings. Banned accounts cannot sign in. One account is permitted for each email address after case and surrounding whitespace normalization. An ordinarily deleted account may register again using the same email; a valid ban cannot be bypassed by re-registration.

When a ban is imposed, a server-keyed HMAC-SHA256 digest of the email and its creation date are retained in a restricted security table. This table does not contain the plaintext email or a complete copy of the account. The digest remains personal data, is not treated as anonymous information, and is not used for advertising, profiling or unrelated purposes. Following account deletion, this identifier may remain only for as long as necessary to prevent evasion of a valid ban. It is removed when the ban is lifted. Necessity and effects on fundamental rights must be assessed for the security and protection-of-rights purposes. Appeals concerning the ban or the necessity of this record, and privacy-rights requests, may be sent to destek@aiprompter.site.

Optional measurement on the official website

Google Analytics is not enabled in the mobile app. On aiprompter.site, Google Analytics 4 loads only after analytics consent in the cookie panel; it does not start before consent, after refusal, or on administration, verification or security pages. Consent can be withdrawn. URL query/hash portions, referrer, form contents, email and app user identifiers are not sent for measurement. Google Signals, user-provided data, detailed location/device collection and enhanced measurement are disabled. Event/user data retention is set to two months, with reset on user activity disabled. Provider reporting and aggregated data may have separate lifecycles. Technical connection data processed by Google and possible overseas processing must be considered alongside the provider/transfer disclosures in this notice and the website cookie explanation.

Service notifications and device choices

Replies to support requests, content decisions and account-related service events appear in the notification inbox; service emails may be sent to your verified address. We do not send advertising or bulk marketing. The email provider processes the recipient address, send time and a generic service message. These emails do not include your full private support conversation or moderation evidence.

When Android remote notifications are activated, Firebase Cloud Messaging (Google) processes device tokens and technical delivery information only after you enable notifications and grant device permission. iOS remote notifications are not enabled in the current pilot; the Apple APNs scope will be disclosed before activation. Notification permission is optional. You can disable it in device settings or the app. Firebase Analytics is not enabled in the mobile app. Device bindings are deleted with the account; bindings not renewed for 90 days are removed by daily maintenance. Completed or exhausted push delivery records are cleaned after a 30-day operational period; active deliveries are evaluated separately. Payloads contain only generic service titles and event identifiers.

Initial follow of the official account

As disclosed at registration, a new account initially follows the official operator account. The relationship appears in public follow lists and can be removed at any time from the profile. It does not grant marketing-email or device-notification permission.

Written responses and delivery

You can submit a privacy-rights request from the email registered to your account or through in-app support. We verify ownership proportionately and never ask for passwords or verification codes. Formal KVKK requests are assessed against the required procedure and particulars; identity documents are not collected during ordinary registration. Requests are answered as soon as reasonably possible and, under KVKK, within thirty days, in writing or electronically. The response identifies accepted requests, actions taken and reasons for rejected portions. A telephone explanation does not replace the final written/electronic response. Request and response dates are recorded only as needed to document handling and delivery. Other applicable data-protection deadlines and complaint rights remain available.

Device permissions and account choices

Adding a profile photo is optional. Refusing camera or photo access does not prevent account use; it only prevents selecting a photo through that source. Device access can be withdrawn in system settings. Notification permission is not marketing permission or consent to all processing. Language preferences are stored on the device; synchronization across devices is not promised.

Limits on retention

The purpose, scope and expiry/review date of evidence retained for security or a legal dispute are determined for that case. Deleting an account does not automatically place its complete content in a legal archive. Necessity is also reviewed for limited ban-evasion identifiers; hashing/HMAC does not itself make them anonymous. Accepted deletions must be reapplied during recovery before restored records become visible. D1 retains only the most recent completed snapshot; a failed replacement can leave that snapshot older than one day.

Permanent link to this version