Keep your content safe while you get help.

A TestFlight installation invitation, a Daytuck account invitation code, and a shared journal invitation code serve different purposes. To create your first Daytuck account, choose “New here? I have an invitation” on the sign-in screen and enter the AT-I- account invitation code from the administrator.

After joining, keep your AT-R- personal recovery code somewhere safe. A shared journal invitation code only lets you join a particular shared journal. It cannot sign you in or recover your account.

Choose “Sign In with Recovery Code” and enter the AT-R- personal recovery code for your original account. An invitation code creates a new account; it cannot recover earlier content. Using the same display name will not recover it either.

If you lose your recovery code or are asked to check your identity, keep the content on your phone and contact test support. Creating another account will not recover it. Phone number, WeChat, and Sign in with Apple are not currently available as alternatives to the recovery code.

No. The ordinary test build uses its built-in service address. Check your network, try once more, and record the full error message. Please keep the existing address, invitation, and app in place; do not enter a new IP, repeatedly redeem an invitation code, or uninstall the app. If the problem continues, contact support below.

An entry is a saved piece of writing or a set of photos. You can write several entries on the same day, leave the title blank, or save photos alone. A journal organizes your entries; you do not need a new journal for each entry.

Start with “New Entry” and choose a journal in the editor. Choose “Save” for private content. Shared content becomes visible to members when you choose “Post”.

While editing, wait for “Draft saved on this device”, then continue from “Me → Drafts”. You can also look for “Drafts in This Journal” inside a journal. Your unsubmitted shared drafts are visible only to you. A submission awaiting verification may already be visible to members; check the original submission first. Reopening a draft does not post it automatically.

A draft saved on your phone is not necessarily backed up to iCloud. Check sync or manually save a backup before shutting down or uninstalling, and keep a backup in case the phone is damaged.

You can save on this device first. Until your private entries, originals, Live Photos, and your own drafts have uploaded fully, do not treat them as backed up in the cloud. Check “Me → Storage & Sync”, keep the content on this device, and create a full personal backup if needed.

Manage your own iCloud storage and restore the network, then sync again and check that sync is complete. Daytuck does not buy iCloud storage for you or silently move private content to the shared cloud.

No. Content stored only on the old phone, without an upload or backup, will not appear just by signing in. Retrieval from iCloud requires the same iCloud account, the same Daytuck account, and the same environment specified by the administrator. Before changing phones, confirm that sync is complete or keep a usable personal backup.

The new test build and earlier development builds use different content environments. Earlier content will not necessarily migrate automatically. Confirm the arrangements with the administrator first, and keep the original app and iCloud account in place instead of changing them to try to “refresh” the content.

Tap a photo to open it, then swipe left or right to switch. Tap once to show or hide information; double-tap or pinch to zoom. When zoomed in, drag to see details. Return to the original zoom level, then swipe up or down to close. Press and hold a photo marked LIVE to play it.

If a photo fails to load or gets stuck, keep the original entry. Note whether it happened in a private or shared journal, in the detail view or editor, and on the first photo or while switching, then report it. Please keep the entry rather than deleting it and uploading again to try to fix it.

A Live Photo needs both the photo and its complete paired motion resource. Each still original or complete Live Photo can be up to 20 MiB. JPEG, PNG, HEIC, and complete Live Photos are supported. Incomplete resources are not silently saved as still photos. If the original is still only in iCloud Photos, connect to the internet and wait until it is available before selecting it.

Motion cannot be restored automatically to older photos that were saved as still images. Use a sample without sensitive information when reporting a problem; do not send personal photo originals.

We do not recommend that during this test. An entry keeps its own file copy, and there is no promise of deduplication with your Photos library. “Saved on this device” does not mean cloud sync is complete. The test app should not hold your only photo copy; keep the original in Photos or another reliable copy.

Sharing an original photo may also share metadata such as when and where it was taken. Check before posting.

Sharing currently supports two people. Current members of a shared journal can see its posted entries, including entries posted before they joined. They cannot see your private journals or unposted drafts. Each person edits their own entries and can write another entry to add their perspective.

Viewing posted shared photos requires a network connection. A photo in a draft stored only on your device, which has not been successfully posted, is not visible to your partner through that draft.

Please do not create a duplicate post. “Check post status” means the original submission may already have succeeded, and your partner may already have seen it. When the network returns, check the original submission first. The app keeps the draft state that needs checking.

If you are temporarily unable to post, keep your draft on this device and try again later. Saving on the device or keeping a draft in iCloud does not mean it has been posted.

Check your current role in that journal’s “Members & Settings”. The current owner must transfer ownership before leaving. After you confirm leaving, you lose access to the journal, while posted entries remain in it. Your own unposted drafts remain, but keeping a draft does not give you permission to post to the journal again.

Copies that the other person has saved to Photos, Files, or an offline device cannot be recalled remotely. Test transfers and leaving only in fictional test journals specified by the administrator.

Not necessarily. The deletion or departure may already have taken effect, while an independent safety record still needs checking. View the original item or retry its confirmation in “Safety Confirmation”; do not start another deletion or departure. If the content or access does not match what the page says, contact support.

Go to “Me → Backup & Restore → Create Full Backup”. When it is ready, choose “Share or Save to Files” and actually save the file. Opening the share sheet alone does not save it. Keeping it only on the same phone does not protect against losing that phone.

A .daytuck file contains private journals, entries, private drafts, originals and Live Photo motion, plus your own shared drafts, including submissions awaiting verification. Those submissions may already be visible to members. Importing does not post drafts automatically. The file does not contain posted shared entries and is not a backup of a whole shared journal. The file is not password-encrypted. Keep it somewhere trusted and do not send it to support.

Review the preview before deciding to merge. Use the file only with its original Daytuck account and corresponding environment. Identical content is skipped. Different versions of the same item stop the entire import, leaving existing content in place.

Keep the backup and the content on your phone. Contact support about a conflict rather than clearing the phone to force an import. An older export only provides an inspection report; it cannot be restored as a new full backup. Ask the administrator to arrange validation before a first restore on a new phone or fresh installation.

You can restore entries from Recently Deleted within 30 days. For private entries, go to “Me → Private Recently Deleted”. For shared entries, use your own Recently Deleted area in that journal. Permanent deletion and completed account deletion cannot be undone. Keep any backup you need beforehand.

The test candidate reports completion only after private iCloud, shared cloud, and local cleanup checks. If a step fails, local data and retry credentials are kept. Continue the original request within 30 days; if you cannot finish, contact support and keep the app and original iCloud account. Live cloud and cross-device cleanup are still being verified. Independent backups follow their retention period; members and holders manage their own external copies. See leaving and deletion for details.