Your reading. Your choices.

Browsing and accounts

Swaylit is operated by Kreshnik Mati. You can browse public posts in the native app without an account. The website requires beta approval; posting and private account actions require sign-in. Apple, Google and email/password sign-in use Amazon Cognito, which manages account identifiers, email and authentication credentials. For email access, Swaylit passes your password to Cognito over HTTPS and does not persist or log it. You choose the public name shown with your posts.

Apple, Google and email/password access use separate Swaylit identities. Using the same email address does not combine those accounts.

Beta requests and browser sessions

If you request access, we store your email, request date and approval status so the owner can manage invitations. Requests are not automatically approved. An approved email must be verified by the sign-in provider. Separate accounts remain separate even when their verified email matches.

The website uses a necessary, secure sign-in cookie. The server stores the corresponding session and provider tokens in its private database for up to seven days. Signing out removes that browser session; revoking beta access blocks protected website and account actions, but does not make public posts private. Beta request records remain until the owner removes them or ends the beta; contact us to request removal.

What stays on your phone

Unfinished posts and copies used to recover posting progress stay on your phone. They may contain selected media, book details and your thought. Sign-in sessions use your device’s secure storage. A local recovery copy is not an online backup.

Camera, microphone and photo-library permissions support the capture and import actions you choose. You can change those permissions in your device settings. Posting-stage timings stay on the phone for recovery and diagnosis.

When you post or share

Saving your reader profile makes your chosen display name, username, photo and bio visible on a shareable page. You can change them in Profile → Edit profile. A display name change also updates the byline on existing posts in the feed.

Deliberately posting sends the selected content to private storage for processing before publication. An uploaded or queued item is not a confirmed public post.

Published posts, their public bylines, playable media and branded sharing files are publicly readable, including through the native app without signing in. The website entrance remains limited to approved beta accounts. Recipients and other platforms may keep copies they receive. Removing a Swaylit post cannot recall those copies.

Services that help Swaylit work

The app, database and private storage run in AWS Canada Central. CloudFront delivers the website and published content. AWS, Apple, Google and any sharing destination you choose process connection or account information while providing their services.

Book searches send your query through Swaylit to Open Library. Swaylit does not attach your account identity or unfinished post to that request. Server failure logs use limited error codes rather than your post text or sign-in tokens.

No additional remote reader-study analytics collection is active. Any reader study will explain its observations and ask for consent separately.

How long information stays

The private beta uses the following storage and cleanup rules. They describe different copies of information, rather than a single deadline for deleting an account.

New uploads and processed media

These have no automatic age-based expiration. The earlier 30-day original-upload rule does not apply to them. Post removal and cleanup are separate actions.

Earlier uploaded originals

Originals stored through the earlier upload system become eligible for expiration after 30 days. Older versions have a separate 30-day period after they are replaced.

Private submission records

Backup maintenance removes private submission records and their upload receipts older than 30 days. Removing those records is not the same as deleting every stored media copy.

Database backups

Backups become eligible for expiration after 14 days. Older backup versions become eligible one day after they are replaced. A backup may retain information already removed from the live database.

Reports

Reports are kept for 30 days from their original acceptance, including resolved reports, then removed during successful intake or maintenance.

Rejected posts

Processed media and the stored references used to preview it become eligible for cleanup seven days after rejection. This does not remove the review decision itself. Original uploads and backups follow their separate rules.

Storage expiration and cleanup do not happen instantly. Service or database outages can delay them. These schedules do not remove copies on your phone or files that other people have already received.

Removal and privacy requests

You can remove a public post through Your posts. Full account deletion is not yet active in this owner-only release, and no whole-account deletion timeframe is promised here.

For a privacy question or data request, contact haknick@gmail.com. Please describe what you need without sending passwords, sign-in codes or private media. See the community rules for concerns about a post.