Privacy Policy

Privacy Policy

Updated 7 October 2026. This policy covers DigitalHarvest at digitalharvestdaily.blogspot.com, an independent publication operated by NSST. For privacy questions, contact noyoung0329@gmail.com.

Browsing and site statistics

You do not need to create an account with us to read the blog. The site is hosted by Google's Blogger service. Blogger and Google may process technical information such as IP addresses, browser and device information, visited pages, cookies and other identifiers when providing their services. We use available aggregate Blogger statistics to understand readership.

Google Analytics 4

We use Google Analytics 4 to understand which pages readers visit and how they reach them. Analytics may process page URLs and titles, referring sources and campaign information, visit timing, browser and device information, and cookies or other identifiers. The Google tag sends technical information to Google. DigitalHarvest and SmartAI Reviewer use our existing Analytics property, with reports separated by website domain.

We do not add names, email addresses, phone numbers or private message contents to Analytics events or campaign links. Please avoid including personal information in search terms or page URLs. Read how Google processes information from sites using its services. You can manage cookies in your browser and use Google's Analytics opt-out browser add-on.

Advertising and cookies

Google AdSense is configured for this site. Configuration does not mean the site has been approved or that ads are currently being served. When advertising operates, Google and other advertising providers may place and read cookies, use web beacons, and process IP addresses or other identifiers for ad delivery, measurement and, where applicable, personalisation. Advertising cookies may relate to visits to this and other websites.

Read how Google uses information from sites that use its services. You can manage personalised Google advertising through Google Ads Settings and manage or delete cookies in your browser. Disabling cookies can affect some third-party features.

Contact and comments

If you email us, we receive the message, your email address and any information you choose to include. We use it to reply and to handle your request, not for unrelated marketing. Blogger comments and any associated Google sign-in are handled through Google's services. Please do not send passwords, API keys or payment-card information. To request access, correction or deletion of information you sent directly to us, contact the email above.

On-page tools

The duplicate file checker reads the two files you choose and compares them in your browser. Its code does not upload those files to our server or save them. Visiting the page can still involve the hosting, statistics and advertising technologies described above.

Other websites and purchases

If an article contains an affiliate link or a link to something we sell, it is disclosed there. Following them takes you to another service, which applies its own privacy and payment practices. Purchases are handled by the destination platform; this blog does not provide a payment-card entry form. Do not assume that another site's privacy practices are the same as ours.

Children and updates

This publication is intended for adult creators, not children under 13. Please contact us if a child has sent us personal information. We update the date on this page when its description changes.

About · Contact · Start here · Disclaimer

Comments

Post a Comment

Popular posts from this blog

FFmpeg Shows −1.5 dBTP. Did You Actually Fix the Audio?

An output_tp of −1.50 in an FFmpeg log does not mean your original audio has been fixed. A command can show that number without saving any corrected audio. Before uploading, measure the file you actually exported. This follow-up to our AI song quality checklist tackles one practical mistake: confusing filter output statistics with a saved deliverable. You need FFmpeg installed and a local audio file. These commands process files on your computer; they do not upload your recording. One recording, two different stages On September 18, 2026, we measured one newly generated, roughly 2-minute-20-second MP3. Its integrated loudness was −11.41 LUFS and its true peak was +0.84 dBTP . The same analysis log showed output_tp: -1.50 . input_i and input_tp describe the file supplied to that command. output_i and output_tp describe the signal after the filter in that execution. They do not establish the measured properties of a separately encoded final file. We then reduced gain by...
Read more

VoxCPM2 vs ElevenLabs for a 30-Second Science Short: We Timed Both on the Same Script

Image
Disclosure: DigitalHarvest (NSST) is an independent affiliate of ElevenLabs. We may earn a commission if you subscribe through the referral link in this article. ElevenLabs has not sponsored, reviewed, or approved this article. This relationship does not change the numbers below, and the free local option wins on cost in our own test. We make 30-second science Shorts from public-domain NOAA ocean footage, and every one needs about six lines of narration. On October 4, 2026 we took one finished script and voiced the same six lines twice: once with VoxCPM2, an open-source model running on our own Apple Silicon Mac, and once with ElevenLabs on the paid Creator plan we already use. Then we ran both outputs through the same Whisper check our pipeline uses before anything is published. Here is what came out. The script we used The episode is "Why doesn't hot water on the seafloor boil?" (a small black smoker vent filmed at 2,947 m by NOAA Ocean Exploration). Six lines, 428...
Read more

Before You Upload an AI Song or Video: The Checks We Run (Free Commands)

The FFmpeg and file-hash commands below run locally. No purchase is needed to follow them. In September 2026 we published a 140-second "music video" for one of our AI songs. It was one still picture with a small moving waveform along the bottom. Our pre-upload checks had measured the length, the resolution and the loudness. Nobody had checked whether the picture actually moved. We deleted it from our channel the next morning. This post shows the checks we run now. Every command below runs on your own computer with ffmpeg , and every number comes from files we measured ourselves. 1. Loudness and true peak (free, one command) ffmpeg -hide_banner -nostats -i song.mp4 -af ebur128=peak=true -f null - Read the Summary block at the end: I: is the integrated loudness in LUFS. Peak: under "True peak" is the true peak. ffmpeg prints the unit as dBFS. A test file we deliberately pushed too loud read I: -8.4 LUFS and Peak: 3.5 . Our own working baseline is ...
Read more