Legal

Privacy

What we process, why we process it, who receives it, how long it is kept and your rights.

Last updated: 15 November 2026

At a glance

  • Checks run on the server.Relevant text and context are sent to the server. Saving to memory requires separate approval.
  • Primary hosting is in Türkiye.External email, analysis, payment and measurement services are considered separately.
  • Content is not used for ads.Checked content is separate from consented measurement on the public website.
  • Deletion and requests differ.The account-deletion button is not the only way to exercise your personal-data rights.

This summary is a guide. Read the full notice below for the details.

Operator: Ramazan Uzunkavak · Address: Soğanlık Yeni Mah. Muş Sok. No: 27/3 34880 Kartal / İstanbul · Privacy contact: support@proomise.com. Sytark Studio is the brand/promotional name and Proomise is the product name.

Information we process

We process your account email, display name and profile details, password hash and session information, workspace memberships and access permissions. New email/password registration asks for a full name; older accounts or other sign-in paths may lack a display name. Your password is not part of the text being compared.

If Google or Apple sign-in is enabled and you choose it, we process the provider-verified email address and provider-specific account identifier to create your account or recognize your linked account. This sign-in does not request permission to access your Google mail or contacts. Using the same email address does not automatically link a new sign-in method to an existing account.

For a completed Apple connection, the refresh credential needed to revoke that connection when deleting your account is stored encrypted on the server and used only for that revocation. Google and Apple access or ID tokens are not written to the browser's localStorage/sessionStorage stores.

When you check text, the relevant draft or document content, selected context and formatting preferences are sent to the Proomise server. Surrounding paragraphs or related message subjects and earlier correspondence may provide context in supported source workflows. Checking text and creating a permanent promise record are separate operations; you approve permanent recording.

Extension checks for the open mail page: When the toolbar attaches to a supported mail page, including before checking is enabled, the page’s full URL and structural information identifying its editor may be held in the extension’s working memory. Page information may also verify that internal extension messages come from an allowed mail source. These checks prevent an earlier check or send authorization from carrying over to the wrong draft. The full mail URL held for these purposes is not written to persistent/session storage or sent to the Proomise API. This memory record has no fixed retention period; references are released according to the page, editor and connection lifecycle. Immediate physical erasure of memory is not promised.

Saved promises, original source excerpts, revisions and workspace activity history form part of the service. Connected application/device names and connection status are associated with your account. Information you send to support is used to resolve your request.

Data categories, purposes and collection methods

Data categorySpecific processing purposeCollection method
Account email, password hash, display name and optional profile imageCreate/authenticate the account and display the selected profileRegistration, sign-in and profile forms; if selected, the verified email and provider account ID from enabled Google/Apple sign-in
Sessions, connected applications/devices and connection permissions; encrypted revocation credential for a completed Apple connectionMaintain account access, manage connections and perform sign-out, revocation and account deletionSign-in, pairing, session renewal and enabled external sign-in/connection operations
Workspace membership, roles and access informationRestrict private and shared records to authorized peopleWorkspace creation, invitation/membership and permission operations
Checked text, selected context/formatting, supplied source information and temporary analysis derivativesCompare current text with the correct authorized history and safely reuse an interpretation of the same sourceUser-enabled web/client checking and supported document/mail source reading; the bounded external analysis path below, if enabled
The full address (URL) of a supported open mail page and local structural information identifying its editorVerify the mail page/editor, recognize the same open draft and prevent earlier checking/send controls from carrying over to the wrong draftMay be processed only in extension memory when the toolbar attaches, including before checking is enabled
Approved promises, original sources, revisions, activity and read informationPreserve business history, select the correct source in later comparisons and show relevant activityExplicit recording/revision actions and associated activity and notification-read operations
An incorrect-warning report's checked text, previous-source/analysis evidence, reason and optional noteLet the user review a reported result with its comparison contextThe user's explicit recording of a report in a separate dialog; scope and retention are described below
Account email recipient, action message and verification/reset linksVerify the email address and recover account accessA user account action and its email delivery path
Language, formatting, currency, display and selected-workspace preferencesMaintain the selected interface and checking contextUser preferences and local/session storage on the device
Limited local error codes/timestamps and application-generated request/error metadataCorrelate technical failures without unnecessarily recording private source contentClient diagnostics and application request/error handling; exporting local diagnostics is the user's choice
Request IP address and limited service activityLimit abuse, enforce request budgets and protect service securityServer requests and verified connection information from a trusted proxy, if configured; no GPS permission or general location tracking is requested
Support subject, messages, replies, status and information supplied by the userAssociate the request with the correct account, answer it and track its resolutionIn-app support form, operator replies and the support-mailbox connection if enabled
Billing-account/subscription/transaction identifiers, selected plan and seat quantity, periods, amounts, currency, payment status and invoice information returned by the providerVerify entitlements for the correct personal/workspace account, perform renewal/cancellation and show payment historyPurchase flow, provider API reads and signature-verified payment notifications; Proomise does not store full card numbers or CVVs
Billing address lines, city, region/state, postal code and country; business name/tax identifier where applicable, and the existing business registration number and contact names/emails to be preservedApply an authorized billing-detail change to the correct subscription, preserve existing contact details and safely track duplicate or uncertain operationsBilling-details form and authorized provider reads; the operation-record and retention explanation below applies

This table maps source-documented categories, purposes and collection methods. Matching each row to its applicable legal basis and completing actual external-recipient/transfer information remain open below. A user's checking, recording or reporting action is not presented as consent to every processing or international-transfer activity.

Purposes and sharing

We use this information to authenticate your account, enforce access boundaries, compare against the correct previous source, store approved records and manage connections. Shared workspace records are visible to users with access to that workspace. Consider that audience when adding a shared record.

We do not sell checked messages or documents, saved promises, or data derived from that content. We do not use that content to target advertising or provide it to advertising platforms. We do not use or transfer it to assess creditworthiness, determine lending eligibility, or make lending decisions. Authorized workspace sharing and the service-provider processing described in this notice support the Proomise service. Optional measurement on the public website is separate from checked content and is explained below.

The main application and primary database are hosted on the operator's own server in Türkiye, as stated by the user on 28 October and reaffirmed on 31 October. Türkiye is Proomise's primary data storage location. The external-service descriptions below do not mean that the primary database is hosted abroad; they concern only the information sent to each service.

If OpenAI or Claude analysis is enabled, checked content and selected context may be sent to the selected provider. General meaning comparison may also send a bounded set of previous source texts that you are authorized to access within the same party, project and work scope; the entire workspace memory is not sent. The code masks email addresses and recognizable phone details in both texts; this does not anonymize all personal data. Requesting that OpenAI not store its response does not mean every provider security record is deleted, and is not a retention guarantee for Claude.

The live-service check on 31 October 2026 reported rule-based analysis as active; external AI analysis and Google/Apple sign-in options were not offered as active paths. This is a dated operational observation, not a guarantee about future provider changes. Before enabling external AI, this notice must be updated with the actual provider and transfer conditions.

Google Workspace is used to send account emails, as confirmed by the user on 31 October. When an account verification or password reset email is sent, the recipient address and the corresponding account-action message are transmitted to that service. This is separate from optional Google or Apple sign-in and from checking content in Gmail or Outlook.

The Google Workspace edition observed in the Admin console on 31 October 2026 is Business Starter. Google's published list of editions supporting its data-region feature does not include Business Starter. Consequently, no US-only, Europe-only or Türkiye-only data-location commitment is made for this service; data may be processed where Google or its subprocessors have facilities. A selected region has not been verified. Supported editions and data regions, regional terms, covered data.

Google's Cloud Data Processing Addendum (CDPA), which sets out processing and deletion terms, was accepted for the Workspace account used by the service on 31 October 2026 with the operator's explicit authorization. Automatic deletion of email and chat messages is disabled in the Gmail administrator setting inspected; user- or organizational-unit-specific exceptions and Vault rules were not separately verified. No fixed automatic-deletion period is promised for the provider's mail copies. Application link expiry does not set the deletion time for those copies. Accepting the CDPA does not by itself complete the legal basis or any required notification for transfers outside Türkiye; these must be completed separately. CDPA, checking contract status, subprocessors.

Support requests are not shared workspace content; they are processed by the requester and separately authorized operator administrators. Ordinary workspace ownership does not grant access to other users' support requests. When incoming/outgoing support email is enabled, addresses, subjects and message content are also processed through Google Workspace. Mail-provider retention is separate from the in-app request record.

The Safari extension does not request access to macOS Contacts. Permissions for supported writing and related source workflows do not authorize collection of an entire mailbox or general browsing history. The current extension contains no advertising tracking.

Paddle's Merchant of Record model has been selected for paid plans; the actual Proomise payment integration remains unverified. This selection does not establish that payment or billing data is currently sent to Paddle. The data involved, processing countries and retention terms must be verified for the actual integration and publication before this notice describes that data flow.

Optional measurement on the public website

Google Analytics 4 visitor measurement and Google Ads conversion measurement can be enabled separately on the public website. A service that has not been configured is not loaded. A configured service does not load its Google tag or send measurement requests to Google until you allow the relevant purpose. Visiting the site or accepting the terms of use does not provide that permission. Analytics and advertising measurement are separate choices; permission for personalized advertising is not enabled.

Measurement covers the public page address without its query string or fragment and the defined link clicks. Clicking the contact email link does not mean an email was sent, and clicking a sign-up link does not mean an account was created. The application's events do not include form contents, email addresses, account or workspace identifiers, or checked message and document content. When a Google tag runs, it may receive technical connection and measurement information from your browser. Optional measurement is therefore not described as processing no personal data.

Your choices, their version and the time of the choice are stored in your browser as “proomise-site-consent-v1” and remain valid for up to 180 days. Use the fixed “Cookie preferences” button at the bottom of the screen to change or withdraw them. Withdrawal stops new application measurement events, clears the relevant provider cookies that the site can access and, under normal storage conditions, reloads the page with measurement denied. It does not recall data already sent. If browser storage becomes blocked after a tag has loaded, you may be asked to close the tab to remove the running tag. The cookie notice provides further details.

Google is a separate recipient for this measurement. The actual account settings, provider processing and retention terms, cookie inventory and applicable international-transfer arrangements must be verified before enabling it. Allowing visitor measurement does not change our commitment not to provide checked business content for advertising.

Information on your device

Sessions, connections and interface preferences may be stored on your device to operate the service. The storage used varies by client; the descriptions below reflect the implementation in source code, not a fresh verification of every production client. Expiry of a permission or reuse period does not mean that data in a closed application is physically deleted at that instant.

Web application: The working draft is held in page memory; its body is not written to localStorage/sessionStorage. Language, number/date format, currency, price basis, help/information-icon and memory grouping preferences may remain in localStorage without an application-defined time limit. The selected workspace ID, the name and operation key of a pending workspace/group creation, the help panel's location and the open support ticket's number may use sessionStorage. An invitation code, support-ticket link or payment link for an existing purchase waiting to open after sign-in may also be held in the same tab; these can be reused for at most 15 minutes and are cleared when consumed. The payment link stores only an application path containing the existing purchase-operation ID, any workspace/setup IDs and provider transaction ID, with its original received time; it stores no name, address, message body, sign-in credential or instruction to change a payment method. The link alone grants no payment or account access; operation ownership and scope are separately validated by the server. Retaining it again does not extend the original time; physical deletion at exactly 15 minutes is not promised while the application is closed. These records are not draft/message bodies or sign-in tokens. Source applications such as Gmail, Outlook and Word retain their own mail or documents under their separate service behavior. When you move from the public-site form to registration on the same origin, the email you entered, a data-format version and its creation time may be placed in sessionStorage under “pw-website-signup”. The registration form reads and removes the entry once, using a valid entry less than five minutes old to prefill an editable email field. The address is not added to the URL. This does not create an account, sign you in or accept any terms. If storage is blocked or the destination has a different origin, the normal registration page opens without transferring the address. Five minutes is a reuse limit, not a promise to physically erase an unread entry in a closed browser at that moment.

Marketing-site language preference: The new TR/EN site version stores the language code chosen from its menu in localStorage under “proomise-site-language”. This choice takes precedence over browser language on later visits; automatically detected browser language is not written as a saved preference. There is no application-defined expiry; it changes when you choose another language and is removed when the browser’s site data is cleared. If storage is blocked, an explicit choice can be carried in the page URL’s lang parameter.

Customer sign-in: The “PromiseWall.Session” and “PromiseWall.Refresh” cookies cannot be read by JavaScript. Server access lasts eight hours and may be renewed within an absolute limit of 30 days from sign-in. If you select Remember me, both cookies may persist until that limit; otherwise, nonpersistent session cookies are used. Renewing access extends neither that deadline nor the chosen persistence. Signing out or security revocation can end access sooner; a cookie remaining on the device does not by itself mean that access is valid. Enabled Google/Apple sign-in may also use short-lived external-sign-in and verification cookies that JavaScript cannot read.

Operator administration: Separate administrator sign-in uses “Proomise.Administration.Session”, independently of customer-account cookies. JavaScript cannot read it, and it is sent only to the administration API path. An administrator session lasts eight hours; use does not extend it. The administrator's Remember me choice only enables persistence within those eight hours, not the customer's 30-day renewal. The administration language preference is separately stored in localStorage.

Browser extensions: Chrome/Edge access and refresh credentials are in session storage restricted to trusted extension contexts; they are not exposed to content scripts. Language/format and similar preferences and limited diagnostics use separate local extension storage. Safari's remembered connection credentials are in macOS Keychain, while the running connection uses extension session storage. These client connections start with eight-hour server access and an absolute renewal limit of 30 days from pairing; revocation may end access sooner. Expiry does not mean a closed client's local record is deleted at the same instant.

Word/Outlook add-ins: Access and refresh credentials are held in the open pane's memory. Separate Word and Outlook device-identifier cookies, unreadable by JavaScript, help locate a connection when reopening over HTTPS; these last 30 days. Such a cookie alone does not authorize opening or renewing a connection; the server separately verifies the connection and its current authority. Language preference and the session/operation IDs of an unfinished explicit sign-out may remain in localStorage; the latter is cleared when sign-out resolves and contains no access token. A language selected during startup can be carried once through sessionStorage when the pane reloads. Outlook's item-bound SessionData may also contain a send-check marker, source digest, short-lived restricted send permission and a used-attempt marker; no body copy is written to those markers. Expiry of send permission does not physically delete SessionData at that instant.

Thunderbird: An optional remembered connection is held in a file protected with the current Windows user's DPAPI or in Mac Keychain. Ordinary extension storage holds a nonsecret storage locator/enabled flag for that connection. A separate reload handoff uses a temporary envelope that writes the access token and any refresh token to ordinary local extension storage without additional application-layer encryption. The envelope can be reused for at most 120 seconds; it carries only the connection and permitted tab preferences, not draft text, source-reading consent or an old analysis decision. A running background timer performs cleanup; when reopening, consumption removes the stored envelope before validating it. Physical deletion at exactly 120 seconds is not guaranteed while the process is closed. This temporary handoff is a different storage method from the protected connection in the operating-system vault.

Local extension diagnostics contain limited error codes and timestamps, without text, email addresses or request bodies. The last-50-events/seven-day limit is applied on reads and writes; users can clear these diagnostics. Exporting diagnostics for support is your choice.

Retention and requests

The following statements describe the documented application retention and deletion policy. The stated default periods do not mean that every production setting was reverified when preparing this notice. Expiry of access, removal from a view, archiving and physical deletion are separate operations.

Support content: We retain support messages, images and technical attachments for 12 calendar months after the last message from you or support. Reading a request does not extend this period. Deleting a request also removes its linked messages and reply email queue from the application. Copies in the support mailbox or other services are covered separately below.

Security and support access logs: We retain routine application security access logs and records of staff access to support content for 90 days. A support access record identifies the staff member, request and version, time, view type and reason; it does not copy the content. Financial records, membership acceptance records, saved business promises and backups are outside this 90-day rule.

Specific retention exceptions: We may retain specific records longer where needed for a particular security incident, legal obligation or dispute, with a documented reason, case reference and end date. Normal cleanup applies again when the exception ends or is released. The exception record itself, which contains no support content, is retained for 90 days after the end or release date. Cleanup runs periodically while the application is running. Temporary errors, a backlog or a stopped application can delay deletion. We do not promise physical deletion of every copy at the exact moment a period expires.

Account and private workspace: Approved business records have no general automatic age-based deletion while your account remains open. When deletion is completed through Account → Security → Delete account using your current password and explicit confirmation, the private workspace's records, sources, revisions, activity history and feedback are removed. If you are the sole owner of a shared workspace, ownership must first be transferred. Account deletion also removes the associated session and connection permissions. For an eligible ongoing personal paid subscription, the request first stops renewal; the account remains through the paid period and is deleted after the provider cancellation and period are verified. The request can be withdrawn without automatically resuming renewal. Unresolved payment operations or shared ownership must first be resolved. Request time, related subscription and operation status are retained to execute this flow.

Payment history: Account deletion removes the account-access link to closed financial records; payment receipts, invoice information and provider references are not automatically erased. Registering again with the same email does not provide access to old invoices. The actual personal data retained, applicable retention obligation/period and Paddle's separate retention must be completed in the final publication review; simultaneous deletion of all data is not promised.

Billing-detail changes: Your submitted address and, where applicable, business name/tax identifier, the previous address/business details and the existing business registration number and contact names/emails to be preserved are held encrypted in a separate server-side operation record until the change is resolved. Completion, a confirmed rejection or safe closure removes this full content; an encrypted request digest remains to prevent the same operation ID from claiming an earlier result for different content. Completed account deletion removes this content, the encrypted digest and the requesting-account link. The identifiers and stage of an uncertain subscription-binding operation may remain; erasing data does not authorize repeating the provider write. This does not promise simultaneous deletion of Paddle records or a fixed retention period.

Shared workspace: Deleting a member's account does not delete the team's business records. Original business sources, conditions, meaning and revisions remain; the deleted person’s account link and personal attribution in activity are removed or replaced with a non-identifying system identity. This does not mean that every personal expression within source text has been erased or anonymized. Archiving also does not physically delete records.

Activity and Notifications: Shared workspace activity and user-specific read information form part of the business history. Other people's unread activity appears in Notifications within a seven-day window; reading it removes it from that inbox while it remains in Activity. The same seven-day window does not apply to automatic system notifications. Removal from the notification inbox is not a data deletion period; account/private-workspace deletion and removal of shared account attribution apply separately.

Feedback: When you choose a reason in the separate report dialog and select “Record report”, the report stores the full checked text, the compared previous source's identity/version and text, previous/proposed meaning evidence, your reason and any note in a protected (encrypted) payload. New reports also include the relevant analysis-request context: source title, language/number/date formatting, reference date, supplied reply sources and user selections. You can expand “Comparison included” to read the checked text and previous source; this view is not presented as a field-by-field preview of the entire technical request. A report does not change your promises. Withdrawing feedback removes the protected content; a transaction receipt and request digest may remain to prevent the same old request from recreating it. Account deletion removes the person's feedback content in shared workspaces as well as private-workspace feedback.

Temporary analysis and source interpretations: A check does not by itself create a permanent business record. The server's in-memory extraction cache has a default lifetime of 120 seconds, configurable between 1 and 300 seconds. The shared client analysis cache is not written to persistent storage and can be reused for at most 60 seconds; source and access evidence is revalidated by the server before reuse. Interpretations of saved sources may also be held in capacity-limited memory and encrypted database caches, which have no time-based deletion period. A changed source or interpretation version invalidates the old interpretation, and account deletion clears the associated caches. These periods are not deletion deadlines for an open card, all page memory or approved permanent records.

Sessions, account email and diagnostics: Expiry of a session or connection permission does not physically delete its database row at the same moment. Password reset links are valid for 30 minutes and email verification links for 24 hours. Protected email content for sent, consumed or expired account actions is cleared. When active, the mail delivery worker also clears action metadata whose expiry was more than seven days ago. A fixed physical-deletion time is not promised while that background worker is disabled. Local extension diagnostics are pruned when read or written to a limit of the last 50 events/seven days; users can clear these diagnostics.

If the Claude API is used: Anthropic's commercial API policy provides standard input/output deletion within 30 days, with exceptions for special agreements, features requiring longer storage, safety investigations and legal obligations. A zero-retention agreement for Proomise has not been verified. Anthropic retention policy.

The provider also has retention and safety-review rules for designated “Covered Models”; a zero-data-retention arrangement must not be assumed to apply unchanged to every model. The selected model, account and contract must be checked against these exceptions before external analysis is enabled. This note does not mean Proomise uses those models. Model-specific retention and review rules.

Processing location and storage location are separate settings. Anthropic documents global default inference routing and a currently available US workspace storage region. Proomise's source does not select a request region; its actual provider workspace settings have not been verified. Hosting the main server in Türkiye does not keep Claude processing in Türkiye. Region settings.

Other services and copies: The application periods above do not govern the separate records of Google, Apple, OpenAI/Claude, source mail applications, external security logging/collection or existing server backups. The general Claude policy above does not verify Proomise's actual account settings or transfer basis. Other services' processing and retention conditions require separate verification. Deletion from the application database is not presented as simultaneous deletion from every provider copy.

Disconnecting an application ends its access to your account; it does not delete your account or saved promises. Contact support@proomise.com to request information, correction, deletion or other rights available under applicable law. Do not send your password or connection code. We may verify your identity securely.

Valid requests under Türkiye's personal data protection law are resolved as soon as possible, within 30 days at the latest. Shared workspace records, statutory retention obligations and provider backups are assessed according to the request's scope.

Security, access and your rights

The service uses account authentication, workspace and role checks, and connection revocation. Certain sensitive records are encrypted by the application; this does not mean every database field is encrypted or that the service uses end-to-end encryption. Account/source identifiers, timestamps and pseudonymous information in security records are not anonymous merely because they omit source content.

Authorized support staff can read the messages, technical information and optional images in support requests made available to them so they can respond. Owning a shared workspace does not grant this access. We do not routinely have people review your content. Human access is limited to your specific support request, a necessary investigation of a specific security incident or a legal obligation. Access is restricted to the minimum needed, and we record who accessed the information, when, the relevant request or incident and the reason. General maintenance does not grant unrestricted access to content.

The support panel records access before displaying a summary or conversation. If that record cannot be written, the content is not provided. This application log does not automatically record a database or operating-system administrator's actions outside the application. For necessary access of that kind, the operator defines the reason and scope beforehand, records the work in the incident record and removes temporary access afterward.

Where Türkiye’s Personal Data Protection Law (KVKK) applies, you have rights to learn whether your data is processed, request information, learn the purpose and whether use matches it, learn the recipients in Türkiye and abroad, correct incomplete or inaccurate data, request deletion or destruction when the legal conditions are met and notification of relevant recipients, object to an adverse result based solely on automated analysis, and seek compensation for unlawful processing. Send requests to support@proomise.com or the postal address above. Explain your request and how we can contact you securely; do not send passwords or connection codes. Any necessary identity check is limited to matching the request to the correct person.

Reading the privacy notice, accepting membership terms and consenting to optional measurement are separate actions. You can withdraw measurement consent; this does not undo processing that took place before withdrawal. Where the GDPR applies, rights of access, rectification, erasure, restriction, objection, portability and complaint to the competent supervisory authority are considered under their applicable conditions. The interface language alone does not determine which laws apply. The account-deletion button is not the only way to make a personal-data request.

Additional information

Reading this privacy notice alone is not consent. Before an external analysis service is enabled, we provide its account, data-transfer and retention details.

Questions?

Contact support@proomise.com. Do not send passwords or connection codes.

Contact

A promise
is a promise.

Proomise keeps confirmed commitments with their sources, so you can refer to them when writing a new message.

Promises are saved only with your approval