Seoki Apps

Privacy policy

Effective date:

Seoki Apps, an independent software studio in the Republic of Korea, operates seokiapps.com. Contact [email protected] for privacy questions and rights requests. This policy covers the website and support messages or app error reports submitted to it; also consult each app’s own privacy information for processing inside that app.

1. Tables and on-device translation

Pasted table text, numbers and source HTML are processed in browser memory, not sent to our server, analytics or advertising servers. The current version does not save or restore table contents automatically; reloading or closing the page may lose your work. Clipboard access occurs through actions such as pasting or copying.

Table translation in supported browsers uses on-device models. Required model downloads need confirmation first and their connections are managed by the browser. Table contents are not sent to an external AI translation API.

2. Visitor statistics and exclusion

Ordinary pages store a random browser identifier and last counted date in localStorage to avoid duplicate counts. The server stores a SHA-256 hash of that identifier and dates for daily, weekly and monthly statistics. This statistics API does not store names, emails, raw IP addresses or page paths. Hashed identifiers are not treated as fully anonymous.

Identifier hashes and counts currently have no automatic expiry. Browser identifiers are removed by clearing site data or enabling exclusion below. Contact us about server records. Exclusion, GPC or Do Not Track prevents subsequent visit-count requests.

3. Support messages and email

Support requires the app name, subject, message, language and submission time; email and a post password are optional. Without a password, messages and replies are public. Subjects and app names remain public even with a password. Email is not shown on the board. Passwords are stored as verification hashes and encrypted copies recoverable by the administrator; do not reuse passwords from other services.

New messages and supplied email addresses pass through Brevo for operator notifications. If you provide an email, reply notifications may include the inquiry and reply. Messages and replies older than 180 days become eligible for cleanup when a new inquiry is submitted, rather than deletion at an exact scheduled time. Contact us for earlier deletion. Direct emails and mail-provider records may remain separately.

4. App error reports and abuse prevention

We accept app error reports only when users consent to sending them. App and OS versions, platform, device description, symptoms, logs, report ID and submission time help resolve errors. Known email and credential patterns are redacted, but detection is not complete; check the report before sending.

Logs older than 30 days are cleaned up during submissions or administrator listings, with a limit of 1,000 reports. Report ID, app, content hash and time used for duplicate prevention and weekly counts are stored separately without automatic expiry. Some APIs use temporary hashes combining IP, a secret and a time window to prevent abuse, without storing raw IPs in those records.

5. Browser storage and cookies

localStorage holds language choice (seoki-language), table UI settings (seoki-table-ui), panel state (seoki-table-panels), and statistics ID, date and exclusion preferences. These have no fixed expiry and can be removed through browser site-data settings. Blocking storage limits saved preferences. The site does not create its own login cookie for ordinary visitors.

Only administrators receive a secure session cookie (__Host-seoki-admin, up to one hour). Hosting and security providers may process cookies and connection records under their own policies. Clearing browser data does not delete server-side inquiries or existing statistics.

6. Hosting, email providers and external links

Cloudflare provides page delivery, security, APIs and the database, and may process technical connection data such as IP, request time and browser information. Brevo handles inquiry and reply emails. Hosting and email data may be processed outside the Republic of Korea depending on provider infrastructure and settings; their policies below explain provider retention and transfers.

We do not sell document contents or share them for advertising. Sharing outside the stated purposes is limited to necessary service/security processing or legal requirements. App stores, social media and other external destinations have their own policies.

7. Advertising and personalization choices

Live advertising is currently disabled on this website. The AdSense verification meta tag and ads.txt provide site verification information and do not load ads by themselves. This notice and required consent arrangements will be applied before advertising is enabled.

If Google advertising is introduced, third-party vendors including Google may use advertising cookies to serve ads based on earlier visits to this or other sites. Google and its partners may use those cookies for personalized ads. Manage personalization through Google’s advertising settings or the industry choice page linked below. Table contents are not supplied for advertising.

8. Your rights, safeguards and policy changes

Contact us below to request access, correction, deletion, restriction or withdrawal of consent. We may ask for minimal verification such as a post or report ID. Do not post identity documents or sensitive information publicly. Withholding required fields may prevent support submission or email notifications but does not prevent table conversion.

We use administrator access controls, HTTPS, and password hashing/encryption. Records marked for deletion are removed from the database; provider backups and mail copies may follow separate retention procedures. This page and its effective date will be updated when data categories, purposes, advertising or provider processing change.

Privacy contact: [email protected]