Privacy policy
Last updated: 13 November 2026. Effective: 6 October 2026.
The short version: Studio keeps your work on your computer. The web and phone apps store what they need to schedule and publish your posts, and to make videos in the cloud when you ask. We encrypt your social account tokens, don't sell data or run ad trackers, and delete everything when you delete your account. AI features send the text you choose to DeepSeek, a China-based provider. They are optional.
Who we are
TallyReel is made by Soonbuilt, a registered business in Pakistan ("Soonbuilt", "we", "us"). We are the controller of the personal data described here.
This policy covers every part of TallyReel:
- TallyReel Studio, the desktop app for Mac and Windows that makes videos on your own computer.
- The web app at app.tallyreel.com: scheduling, AI writing help, and videos and pictures made in the cloud.
- The phone apps for Android and iPhone, which use the same account as the web app.
- The social networks you connect, and this website, tallyreel.com.
Questions, requests or complaints: support@tallyreel.com. We aim to reply within 30 days.
TallyReel Studio: what stays on your computer
Studio is built to run on your computer. You don't need an account to use it. These stay on your computer unless you choose to send them somewhere:
- Your ideas, scripts, videos, library, settings and licence details.
- Script writing, voices, captions, music and rendering, once the AI models are downloaded.
What Studio sends over the internet, and why
A few Studio features reach the internet on purpose. This is all of them:
- Stock footage: short search words for each scene (for example "falcon diving") and your own Pexels API key are sent to Pexels to find and download clips.
- Content check, before a video or AI image is made: the idea, scene description, custom look or host description you typed is sent to our server and then to Creem, which screens it against our content policy. See Content check.
- AI images (only if you use them, and only after the content check allows it): the image description is sent to Pollinations to make the picture, with your Pollinations key if you added one. If the image model is installed on your computer, the picture is made there instead.
- Research: the topic of your video is looked up on Wikipedia so scripts get their facts right.
- Script writing before the local model is downloaded: your idea (or, if you paste your own script, that script) is sent to Pollinations, a free online AI service, so it can plan the video. This stops once the local model is installed or you connect your own AI service.
- Your own AI service (only if you add a key in Settings): your idea, the research notes and the script are sent to the service you chose: Anthropic, OpenAI, DeepSeek, OpenRouter, or any address you enter, including one on your own machine. Their privacy policy applies to what you send. Your key is stored on your computer and sent only to that service. Voices, recordings, footage and videos are never sent.
- Licence activation: your licence key and your computer's name are sent to our server, which checks them with Creem, to activate your licence and to confirm it is still valid. Nothing about your work goes with it.
- Model downloads: AI models are downloaded from Hugging Face and GitHub. These requests include normal technical details such as your IP address.
- Update checks: once a day Studio asks our website whether a newer version exists. The request carries the app version and your operating system, like any download does. It tells us nothing about your videos. You can see the current state under Settings, Updates.
- Sending a video to your TallyReel account (only if you link Studio to your account and press send): the finished video file, its title, description and hashtags are uploaded to your workspace in the web app. The name of your computer is shown there so you can tell your linked apps apart.
- Usage counts and error reports: see Usage analytics and error reports. You can turn them off in Settings.
Pexels, Pollinations, Wikipedia, Hugging Face, GitHub and the AI service you connect are independent services with their own privacy policies.
What the web and phone apps collect
The web app and the phone apps need an account. We only collect what they need to work:
| Data | Examples | Why |
|---|---|---|
| Account details | Name, email address, timezone, whether you verified your email. Your password and sign-in methods are held by Clerk, our sign-in provider; we never see your password | To create and secure your account and show times in your timezone |
| Brand voice | The optional description of your tone that you write in settings | To guide the AI features |
| Connected social accounts | Account id, handle, display name and avatar URL; access and refresh tokens, Bluesky app passwords, Telegram bot tokens and Discord webhook URLs | To publish on your behalf. All tokens and secrets are encrypted at rest with AES-256-GCM. |
| Posts | Post text, per-network versions, scheduled time, status, the networks and options you chose (for example subreddit, board or page), and the link and id of each published post, plus error messages if publishing fails | To schedule, publish and show your posts and their history |
| Post statistics | For posts published through TallyReel, the numbers a network reports, such as views, likes, replies and reposts, and your follower count where the network provides it | To show how your posts did and suggest better times to post |
| Replies and comments | Replies to posts you published through TallyReel on networks where we read them (Bluesky and Mastodon), with the name and handle of the person who replied, and the most-liked public comments under your published videos on YouTube, Bluesky and Mastodon | To show replies in Replies, draft answers for you to check and send, and let a series suggest its next episode from what viewers asked for. Drafts are written by DeepSeek. See AI features. |
| Media | Images and videos you upload, their size, type, dimensions and alt text | To attach them to posts and send them to the networks |
| Cloud videos and pictures | The plan for each video you make in the cloud (idea, script or your own text, and the choices you made), its status, and the finished video and thumbnail; descriptions of AI pictures you ask for, and the pictures | To make the video or picture and let you download or post it. See Videos and pictures made in the cloud. |
| Workspaces and teams | Workspace names, who belongs to each and their role, pending invites (the invited email address, role and who sent it), comments on posts, and each post's activity (who created, edited, sent for approval, approved or published it, and when) | To let teams share channels and posts, review posts before they go out, and show who did what |
| Linked apps | For each desktop app you link (such as TallyReel Studio), the name it gave itself, its platform, when it was linked and last used, and a hashed copy of its token | To let an app you approved upload a finished video and leave a post, and to let you see and unlink your apps. A linked app can only upload media and create posts. It cannot publish, read your existing posts or change your account. |
| Talking to Tally | The messages you send Tally in the app, and short voice clips when you speak to it instead of typing | To answer you and do what you ask. Messages go to DeepSeek. Voice clips go to Deepgram, which turns them into words, and Deepgram also speaks Tally's answers. |
| Your cloned voice | If you clone your voice: the short recordings you make, the name you sign with when you confirm it is your own voice, and the voice built from them | Only to read your scripts in your voice. It is never used to identify you, and only you can use it. Delete it any time on the Voices page, which removes the recordings too. |
| Message Tally on Telegram | If you link it: your Telegram chat id, the workspace it posts to, and the messages and photos you send the bot | To turn what you send into draft posts. Text you send may go to DeepSeek to write the draft. |
| Notification tokens | A device token issued by Apple or Google, or a browser notification subscription, and the device platform | To notify you when a post publishes, fails or needs approval. You can turn this off at any time. |
| Product usage | Which pages of the app you open and a few actions, such as signing up or in, connecting a channel (which network), scheduling a post (how many networks, whether it has media) and choosing a plan. Tied to your internal account id and workspace id, plus browser and device type. Never the text of your posts, your handles, your name or your email. | To see which features people use and where they get stuck, so we can improve the product |
| Security and technical data | IP address, browser or app version, request logs, hashed session tokens, error reports | To keep the service secure, limit abuse and fix bugs |
We do not read your direct messages, your followers' data or your feeds. We only ask each network for the permissions needed to publish, list the pages, boards, blogs or locations you can post to, read the statistics of your own posts, and read the public replies and comments under posts you published through TallyReel.
We do not sell your personal data, share it for cross-context behavioral advertising, or use it to build advertising profiles.
AI features and DeepSeek
The web app's AI features are powered by DeepSeek, an AI provider based in the People's Republic of China. They are: tailoring a post for each network, suggesting hooks, drafting from an idea, the content planner, chatting with Tally, drafting answers to replies, suggesting a series' next episode, and drafts made from what you send Tally on Telegram. DeepSeek also writes the scripts for videos made in the cloud.
When you use an AI feature, we send DeepSeek only what that feature needs:
- the post text, idea, goal or video idea you entered,
- the networks you selected,
- the messages you send Tally,
- when it drafts an answer, the reply you are answering, the name of the person who wrote it, and your post,
- your brand voice description, if you wrote one, and
- when the planner looks at a website, the address you gave and the page text we fetched from it (title, description and visible text).
We do not send your name, email address, social account tokens or media. Most AI features only run when you ask for them. A few run on their own once you use the feature: new replies to your posts get a draft answer, and Autopilot and the weekly plan write posts and scripts if you turn them on. You can use scheduling without ever using them.
Data sent to DeepSeek is processed and may be stored on servers in China, under DeepSeek's own privacy policy. Chinese law may allow authorities there to access it. If you are not comfortable with this, don't use the AI features, and don't put personal or confidential information in text you send to them.
Studio does not use DeepSeek unless you connect it yourself as your own AI service. See What Studio sends.
Videos and pictures made in the cloud
On the web and in the phone apps you can have a video or an AI picture made for you on our servers, instead of on your own computer. When you do:
- The text that describes it is screened first. See Content check.
- DeepSeek writes the script from your idea, unless you gave your own script.
- The plan (idea, script, and your choices of voice, look and length) or the picture description is sent to Modal, a cloud computing service that runs the video and picture models on graphics cards for us.
- If the video uses stock footage, short search words for each scene are sent to Pexels, Pixabay and Coverr.
- The script may be read aloud by Deepgram or Microsoft Azure, which turn text into speech for us. They receive the lines to read, not your account details.
- The finished video and its thumbnail are stored in our media storage on Cloudflare R2.
Some features use files of your own:
- Videos from your photos: the photos and clips you pick are sent from our storage to Modal to put the video together.
- Your cloned voice: your recordings are kept in our storage and sent to Modal to build your voice and to read lines in it. Only you can use it.
- Drawn characters and hosts: when you upload a drawing, Amazon Rekognition checks the picture: that it is drawn rather than a photo of a real person, that it isn’t a famous face, and where the face is so the lips can move. We keep only the result (how many faces, a rough age range and a few labels), not a face template. TallyReel doesn’t make hosts from photos of real people.
Content check
Before any video or AI picture is made, in Studio or in the cloud, the text that describes it is sent to our server and then to Creem. Creem screens it against our acceptable use policy. That text can be the idea, a scene description, a custom look, a host description or a picture description.
This happens before any image or video model runs. If the check fails or can't be reached, nothing is made. Your finished video, voice and footage are not sent for this check.
Connected networks
When you connect a social account, you allow TallyReel to act on that network for you. What we publish there, and when, is exactly what you schedule. Once content is published, the network's own terms and privacy policy apply to it, and deleting it from TallyReel does not delete it from the network.
YouTube and other Google services
TallyReel uses YouTube API Services to upload videos you schedule. By connecting YouTube you agree to be bound by the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy. You can revoke TallyReel's access at any time from your Google security settings, as well as by disconnecting the channel in TallyReel.
TallyReel's use and transfer of information received from Google APIs (YouTube and Google Business Profile) adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- we use Google user data only to provide the publishing features you see in the app;
- we don't transfer it except as needed to provide those features, for security, or to comply with law;
- we don't use it for advertising;
- we don't let humans read it unless you ask us to (for support), it's needed for security, or the law requires it; and
- we never use it to train AI models, and it reaches an AI provider only when you choose to use it in a feature: if you pick a viewer’s comment as a series’ next episode, that comment’s text goes to DeepSeek to write the script.
What Google data we access. When you connect YouTube, TallyReel asks for two permissions. With youtube.upload we upload the videos you choose to your channel, with the title, description and visibility you set. With youtube.readonly we read your channel's id, name and picture (to show which channel you are posting to), your subscriber count and the view, like and comment counts of the videos you published through TallyReel (to show on your Results page), and the most-liked public comments under those videos (so Shows can let viewers suggest the next episode). When you ask Tally to read your channel, we also read your channel's description and keywords and the titles, view counts and lengths of your latest 50 public uploads, once, to suggest video ideas that fit it. That read is turned into a short summary you check and can change before it is saved as your ideas profile; the titles and numbers themselves are not stored. We don't edit or delete any videos, playlists or account data, and we don't read anything else. If you connect Google Business Profile, we use it only to publish the posts you schedule to the locations you pick. We also store the access and refresh tokens Google gives us. If you sign in to TallyReel with Google, we receive your name, email address and profile picture through Clerk, our sign-in provider.
How we use it. Only to upload the videos you schedule, show which channel is connected, show you how your own videos are doing, and offer viewers’ top comments as ideas for a series’ next episode. We never use Google user data for advertising. Separately, to suggest channel ideas we read public information about other channels, which is not Google user data; see Public YouTube data below.
Who we share it with. No one, except the service providers that host TallyReel for us (Amazon Web Services, Supabase and Cloudflare, listed under Sub-processors below), which store it only to run the service, and DeepSeek for a viewer’s comment you pick as an episode idea, as above. We never sell Google user data or give it to data brokers or advertisers.
How we protect it. Google tokens are encrypted with AES-256-GCM before they are stored, all traffic uses HTTPS, and only the systems that publish your videos can decrypt them.
How long we keep it and how to delete it. We keep your Google tokens only while YouTube is connected. Disconnecting YouTube in TallyReel (Settings, Your accounts) deletes the tokens and revokes our access with Google. Video statistics are kept with your posts until you delete the post or your account. Deleting your TallyReel account deletes all of it within 30 days (see Delete your data). You can also revoke access at any time in your Google account permissions.
Public YouTube data
To suggest channel ideas, TallyReel also reads public information about videos and channels on YouTube through YouTube API Services: titles, view counts, lengths, publish dates and subscriber counts. We read it for a small fixed set of topics, and for a public channel whose link you paste when you ask Tally to learn from a creator you like. This is not your Google user data, it is not linked to you, and it does not need you to connect anything. We turn it into our own estimates, which we label as TallyReel estimates and show apart from numbers reported by YouTube. We keep view counts and other statistics, and the estimates built from them, for up to 36 months, and we delete titles, creator names, descriptions and other non-statistics data within 30 days. We use it only to suggest channel ideas, we never copy another creator’s titles, scripts or videos, and we read YouTube only through YouTube API Services. YouTube’s Terms of Service and Google’s Privacy Policy apply to it.
Meta, TikTok, X and others
The same principle applies to every network: we use the data it gives us only to connect your account, publish your posts and show how they did. You can disconnect at any time. Disconnecting deletes the stored tokens and, where the network supports it, revokes TallyReel's access.
TikTok: we store your TikTok open_id, display name and avatar, your access and refresh tokens (encrypted), the publish id of each video we post for you, the statistics of your own posts (views, likes, comments and shares), and your follower count. Disconnecting TikTok revokes our access with TikTok and deletes the tokens.
See also our data deletion instructions.
Your email, when you download an app or join a list
To download Studio we ask for your email address. We use it to send you the download link and setup help, and later to tell you about launches and product updates. If you ask for the Android app, we email you the download link and how to install it. If you ask for the iPhone app, we email you once when it is out. We store the address with the kind of request (a download or a phone app), the system you picked, and the page you came from. We don't sell it or share it with advertisers. The emails are sent through Resend, which handles the address only to deliver them. To stop hearing from us, reply to any of our emails and ask to be removed, or write to support@tallyreel.com, and we will delete it.
Purchases and licences
On the web, payments are handled by Creem, our merchant of record. This covers Studio licences, scheduling plans and cloud video plans. Creem processes your payment details, billing address and email under its own privacy policy, charges any sales tax or VAT that applies, and emails your receipt and, for Studio, your licence key. We receive your name, email and order details so we can provide your licence or plan and support. We never see card numbers.
In the phone apps, purchases go through Apple's App Store or Google Play, and RevenueCat tells us which plan or video pack you bought.
If you arrive through a friend's referral link, the website tells our server the link was visited, and keeps the code in your browser for 30 days if you agree, so the discount can be applied at checkout.
Usage analytics and error reports
This website, the web app and Studio count how they are used with PostHog. It is not used for advertising.
- This website counts which pages are visited and a few steps, such as starting a download, asking for the phone app or playing a sample video. It is cookieless: nothing is kept in your browser for it, so a visit can't be followed from one day to the next.
- The web app records the product usage described in What the web and phone apps collect, without cookies or local storage. Browsers that send Do Not Track aren't counted.
- Studio sends anonymous counts tied to a random id made on your computer, not to you, your licence or your email: the app version, operating system, chip, rough memory, and a few choices and timings per event (such as which template or voice, or how long a render took). When something breaks, it sends the error's type, where in our code it happened, and its message with file paths and quoted text removed. You can turn this off in Settings.
- Problem reports: if you send a report from Studio yourself, it carries your note and the end of the app's log, and Studio shows you what goes with it before you press Send.
We never send PostHog the content of your ideas, scripts, posts or videos, and never your email address. Like any web request, PostHog receives your IP address and browser or device details when an event is sent.
Errors on our server and in the web app are sent to Sentry, an error monitoring service, so we can fix them. Passwords, tokens, cookies and your email address are removed first.
Who processes your data
We use a small number of service providers (sub-processors) that handle data for us:
| Provider | What for | What it receives |
|---|---|---|
| Amazon Web Services (United States) | Hosting the web app and our server (EC2), and checking pictures uploaded for drawn characters and hosts (Rekognition) | All account and post data passes through it; Rekognition receives the uploaded picture |
| Supabase (United States) | Our database and job queue | All account and post data |
| Clerk (United States) | Sign-in and account security: creating your account, passwords, sign-in with Google or Apple, and sessions | Name, email address, profile picture, hashed password, sign-in history, and the IP address and browser of each sign-in |
| Cloudflare | Serving this website, network protection, and storage for media, cloud videos and database backups (R2) | Uploaded media, finished cloud videos, backups, request metadata |
| Modal | Making videos, AI pictures and cloned voices in the cloud, only when you ask for one | The video plan or picture description, the photos and clips you pick for a photo video, and your voice recordings for a cloned voice |
| Deepgram (United States) | Tally's voice chat (turning your voice into words, and speaking its answers), and reading scripts aloud for cloud videos | Your voice clips when you speak to Tally, Tally's answers, and the lines of a script |
| Microsoft Azure | Reading scripts aloud for cloud videos, mainly in Urdu and Hindi | The lines of a script |
| DeepSeek (China) | AI features and cloud video scripts, only when you use them | Text you submit to an AI feature, messages to Tally, replies you get a draft answer for (with the replier's name), your brand voice, the idea for a cloud video |
| Creem | Content check before a video or picture is made | The text that describes the video or picture |
| Creem | Payments on the web and Studio licence keys, as merchant of record (it is an independent controller for the purchase) | Name, email, account id, billing details, licence key and computer name at activation |
| RevenueCat | Managing App Store and Google Play purchases made in our apps | Account id, purchase receipts and status |
| Apple and Google | In-app purchases and push notifications | Purchase receipts, device push tokens |
| Expo | Delivering push notifications to the phone apps | Device push token and the notification text |
| Resend | Sending emails (account emails, notifications, download links) | Name, email address, the email's content |
| Sentry | Error monitoring for our server and the web app | Error details and technical data, which may include your account id |
| Featurebase | The support chat on this website and in the web app: messages to us, feature requests, feedback and help articles | What you write to us, and your name, email address and account id when you are signed in (or the email you give when you are not), browser details, IP address |
| PostHog (United States) | Product analytics, without cookies (no session recording, no ad tracking) | Pages opened and product events, account and workspace id (web app) or a random id (Studio), browser and device type, IP address. Never the content of your posts or videos. |
| Pexels | Stock footage for cloud videos | Short search words for each scene |
| Pixabay | Stock footage for cloud videos | Short search words for each scene |
| Coverr | Stock footage for cloud videos | Short search words for each scene |
The social networks you connect receive the content you publish to them. They are independent controllers, not our processors. So are the services Studio uses directly (see What Studio sends).
Why we're allowed to use it
If you are in the EU, UK or a similar jurisdiction, we rely on these legal bases:
- Contract, to provide what you signed up for or bought: your account, scheduling, publishing, media storage, cloud videos, notifications and your Studio licence.
- Consent, for AI features (you choose to use them), voice cloning (you record your voice and confirm it is yours), push notifications (you can withdraw consent in settings or on your device), and launch and product emails.
- Legitimate interests, to keep the service secure, prevent abuse, screen content before it is made, diagnose errors, and understand how the product is used (cookieless analytics).
- Legal obligation, to keep payment records and to respond to lawful requests.
International transfers
We are based in Pakistan. Our servers and database are in the United States, and our providers process data in several countries, including the United States, the European Union and, for AI features only, China. Where the law requires it, we rely on the providers' standard contractual clauses or equivalent safeguards. DeepSeek does not offer such safeguards in the same way, which is why AI features are optional.
Cookies and local storage
The web app at app.tallyreel.com uses only the cookies it needs to keep you signed in:
- Session cookies (
__session,__client_uatand, on our sign-in domain,__client), set by Clerk, the service that handles signing in, to keep you signed in. - Active workspace (
tallyreel_ws), the id of the workspace you last opened, so the app reopens it. Cleared when you log out.
The web app and this website save your light or dark theme choice in your browser's local storage. For the length of a visit, this tab's session storage holds the site and page you came from (a site name and a page path, never your name or email), so a new account can be tied to that visit. It is gone when you close the tab.
If you arrive through a link someone shared, its code counts for that visit. We keep it longer only if you say yes when we ask: a partner's code in a cookie (tr_aff) for 180 days, so they can be credited, and a friend's code for 30 days (in local storage on this website, or a tr_friend cookie in the web app), so their discount still applies. Say no and nothing is kept.
There are no advertising cookies, no ad trackers and no analytics cookies, so there is no cookie banner. The only question you may see is the one above, about a shared link. In the phone apps, your sign-in tokens are kept in the device's secure storage.
How long we keep it
- Account, posts and connected accounts, for as long as your account exists. Deleting a post or disconnecting a channel removes it immediately.
- Uploaded media, as long as a post uses it. Uploads that are never attached to a post are deleted automatically after 24 hours.
- Videos made in the cloud: on Free, 7 days after each is made (we email you 3 days before); on a paid plan, while the plan lasts. The parts kept for scene editing are deleted sooner, when the edit window ends (2 days on Free, longer on paid plans). Deleting a video removes its files immediately.
- Your cloned voice and its recordings, until you delete it on the Voices page or delete your account.
- Sign-in sessions: held by Clerk, they expire automatically and end when you log out.
- Server logs and error reports, up to 30 days.
- Database backups: deleted data can remain in encrypted backups for up to 30 days before being overwritten.
- Download and waitlist emails, until you ask us to remove them.
- Payment records, kept by us and our payment providers as long as tax law requires.
- Studio data stays on your computer until you delete it there. We don't hold a copy.
Deleting your account
You can delete your account at any time in Settings, Delete account on the web or in the phone app. Deletion is immediate and permanent: your profile, posts, media, connected channels and their tokens, push tokens and sessions are erased, pending scheduled posts are cancelled, and we ask each network to revoke TallyReel's access where it supports that.
Posts that were already published stay on the networks. Delete them there if you want them gone. Full instructions are on the data deletion page.
Team workspaces. Content in a workspace belongs to that workspace and is controlled by its owner. Deleting your account deletes the workspaces you own, with everything in them. Posts, media, channels and comments you created in workspaces owned by someone else stay with those workspaces, shown without your name, because they are the team's data. Your membership, profile and sessions are erased. If you own a workspace that has other members, you need to transfer ownership (or remove the members) before you can delete your account.
Studio. Studio keeps your work on your computer. Delete any video, voice or recording inside the app, or remove the app and its data folder. To delete the order details or email address we hold, write to support@tallyreel.com.
Your rights
Wherever you live, you can ask us to:
- Access your data or get a copy. You can download everything as a JSON file from Settings, or email us. The export contains everything in the workspaces you own, and only what you created (posts, media, comments) in workspaces owned by others. Their owners can export the rest.
- Correct it. Most details can be edited directly in Settings.
- Delete it. See above.
- Restrict or object to processing based on legitimate interests.
- Port it to another service. The export is machine-readable.
- Withdraw consent: stop using AI features, turn off notifications, or unsubscribe from emails.
California residents have the right to know, delete and correct personal information, and to not be discriminated against for using these rights. We do not sell or share personal information as those terms are defined in the CCPA and CPRA.
Write to support@tallyreel.com to use any of these rights. We may need to confirm your identity first. If you are in the EU or UK and are unhappy with our response, you can complain to your local data protection authority.
Security
Passwords are handled by Clerk, our sign-in provider, and never reach our servers. Social account tokens and secrets are encrypted with AES-256-GCM before they are stored. Sign-in sessions are kept in cookies on the web and in the device's secure storage in the phone apps, and all traffic uses HTTPS. No system is perfectly secure. If we learn of a breach that affects you, we will tell you and the relevant authorities as the law requires.
Children
TallyReel is not for children. You must be at least 13 years old to use it, or 16 if you are in the European Economic Area or UK (or older where local law requires). We don't knowingly collect data from children. If you believe a child has created an account, contact us and we'll delete it.
Changes to this policy
If we change this policy, we'll update the date at the top. If the change is significant, for example a new sub-processor that receives your content, we'll tell you by email or in the app before it takes effect.
Contact
Soonbuilt, Pakistan. Write to support@tallyreel.com, or reply to any email we sent you.
See also: Privacy · Terms · Acceptable use · Refunds · Delete your data