Privacy

StoriKix.com is a wholly owned operating unit of DYNAKAT LLC. This notice covers the StoriKix website and its reading, saved-find, and interactive features. Other websites you reach through a story or company link have their own privacy practices.

You do not need a reader account to browse stories, save a find, or make choices inside a card. These features do not create a public profile or publish your answers to other readers.

StoriKix uses browser storage to keep the experience useful between visits. The feed's preference features store the following information on the browser and site address you are using:

• Likes and saved finds: which stories you have liked or bookmarked.
• Your place: the current story, category, Feed or Saved view, submitted search or filter, feed position, story page, and reading offset.
• Reading progress: a story's unread, in-progress, or read state, the portions viewed, a progress total, and the time that record was updated.
• Interactive choices: selections in pickers, quizzes, and polls; personal rankings or favorites; reveal states; and choices such as Save, Maybe, or Pass.

The feed does not upload these preference records or personal votes to a StoriKix account. They do not automatically synchronize across devices. Tabs using the same site in the same browser can share stored preferences.

Search operates against the stories loaded into the feed. A search you submit can be remembered as part of your return position, so avoid entering information you would not want another person using the same browser to see.

Persistent browser storage keeps likes, saved finds, progress, and interactive choices until you change or clear them, or your browser removes that storage. These records do not have an automatic expiry set by the feed.

Return-position information is also kept in session storage and browser history state to support refresh and Back/Forward navigation. Session storage is associated with a browsing session; browser restoration behavior can vary. Your browser may separately retain a history of the page addresses you visited.

Private browsing, storage restrictions, clearing site data, or changing browsers can prevent preferences from being retained. Reading remains available when the browser does not allow the feed to save these records.

• Tap a selected heart or bookmark again to remove that like or saved find.
• Use the controls in an interactive card to change a choice or restart a picker where that option is offered.
• Tap a story's reading-status control to mark it read, or tap a Read status to reset it to unread.
• To remove the site's stored preferences together, close StoriKix tabs, clear StoriKix site data in your browser settings, and reopen the site.

Clearing site data removes the preferences held by that browser; it can also remove login cookies. Browser history is managed separately. Clearing browser preferences does not erase an email you have sent us or records held by an external website.

Because saved finds and interactive choices are not linked to a reader account, we cannot look them up on a central account dashboard or recover them for you after the browser deletes them.

Delivering a website involves requests to a server. Depending on the hosting and security configuration, technical request records may include an IP address, request time, requested address, browser information, and error details. Such records are separate from the feed's locally stored bookmarks and choices and may be used to operate, troubleshoot, and protect the website.

The feed's preference features use local and session storage rather than setting their own cookies. WordPress can use cookies for administrative login, session verification, and interface preferences. You can read WordPress's explanation of its cookies for more detail.

The aggregate analytics counter does not use cookies or browser storage.

Public reading does not require an administrative login. If you use a WordPress administrative account, its account and authentication information are separate from the reader preferences described above.

If you email us, we receive the information in that correspondence, such as your email address, your message, and any attachments or name you provide. We use it to handle the inquiry, investigate an issue, communicate with you, and maintain relevant business records.

Include only what is useful for the request. Do not send passwords, payment-card details, or other sensitive information that is not needed to explain the issue. If a screenshot contains private information, remove that information before sending it.

Correspondence can be handled through the company's email and business-service providers. It is retained as needed for the inquiry, related follow-up, recordkeeping, and applicable obligations. You can contact us with questions about information you have provided.

The Share control opens your device or browser's sharing interface with the story's title, short description, and address. If that feature is unavailable, the site offers to copy the address or displays it for you to copy. The destination you choose handles the information you share under its own practices.

Source links, recommendations, and company links may take you to other websites. Those websites can receive ordinary connection information when you visit them and may use their own cookies or tracking technologies. StoriKix's browser-preference controls do not control those websites.

The current reading interface serves its fonts and story imagery from site assets and uploads. It does not add social-platform widgets that automatically publish your activity.

StoriKix uses a first-party counter to understand aggregate website traffic. It automatically counts page views and story openings, the page or published story, a broad source group inferred from the referring site or recognized campaign-source tags, a broad device category, an approximate country, region, and city estimated on the server from the connection address using a local location database or trusted hosting integration, approximate city-center coordinates rounded to two decimal places when available, and the date and time bucket. These are network-based estimates, not GPS positions or street addresses. The connection address is used transiently for the location lookup and is not stored by this counter. Unavailable locations remain unknown. Aggregate totals are retained without an automatic expiry so we can compare traffic over time, including across years. The counter does not store raw IP addresses, full browser user-agent strings, or visitor identifiers, and does not build individual browsing histories. Full referring URLs, query strings, and arbitrary campaign values are not stored. Missing source information is grouped as Direct / unknown; source labels are not a guaranteed account of how every reader arrived.

The counter does not use analytics cookies or browser storage and does not display an analytics permission popup. It does not use consent preferences or browser privacy signals to enable or disable these aggregate counts. Signed-in editors and identifiable automated traffic are excluded. Counts describe events, not unique people. Saved finds, reading progress, and interactive choices remain separate browser features and are not sent with analytics events.

The feed does not currently include an advertising-network integration, third-party analytics beacons, or social tracking pixels. Its personal polls and rankings are not a server-collected audience survey. We will update this notice and provide applicable choices before enabling services that change these practices. Commercial disclosure standards are explained in How We Create.

You can contact us about access to, correction of, or deletion of information you have provided to the company. Describe the request and how you interacted with StoriKix. We may need enough information to confirm that the request concerns you and to understand which records are involved.

For information held only in your browser, the controls in Manage your saved information are the direct way to make a change. For correspondence or other information held by the company, contact us using the details below. Requests are considered in light of the information involved and applicable requirements.

This notice may change as StoriKix's features and data practices change. The updated date identifies the current published version. We will describe material changes here and provide an additional notice or choice where appropriate for the affected feature.

StoriKix is operated by DYNAKAT LLC. Send privacy questions to hello@dynakat.co with StoriKix privacy in the subject line. Identify the feature or story involved and explain the question without including unnecessary sensitive information.

You can also find the company's published contact information on the DynaKat contact page.