With the options you have specified, the permissions are applied to every file in the NTFS file system.
To take advantage of ntfs-3g's feature for permissions per file, you need to add the
permissions option. If you also want to support more than one user, you can use the
man 8 mount.ntfs:
Access Handling and Security
By default, files and directories are owned by the effective user and group of the mounting process, and everybody has full read, write, execution and directory browsing permissions. You can also assign permissions to a single user by using the uid and/or the gid options together with the umask, or fmask and dmask options.
Doing so, Windows users have full access to the files created by ntfs-3g.
But, by setting the permissions option, you can benefit from the full ownership and permissions features as defined by POSIX. Moreover, by defining a Windows-to-Linux user mapping, the ownerships and permissions are even applied to Windows users and conversely.
Here is the documentation on the pertinent options:
Use file file-name as the user mapping file instead of the default .NTFS-3G/UserMapping. If file-name defines a full path, the file must be located on a partition previously mounted. If it defines a relative path, it is interpreted relative to the root of NTFS partition being mounted.
When a user mapping file is defined, the options uid=, gid=, umask=, fmask=, dmask= and silent are ignored.
Set standard permissions on created files and use standard access control. This option is set by default when a user mapping file is present.